Re: Coexistence of gcc 3.2 and gcc 2.95
Jack Howarth <howarth@bromo.msbb.uc.edu> writes:
> I think the primary problem debian will have with gcc 3.2 (or
> 3.1.1 for that matter) is dealing with rebuilding glibc under it.
> Because the gcc 3.1 fixed a bug relating to incorrectly linking in
> libgcc symbols into binaries, glibc trunk and glibc-2-2-branch have
> fixes to address this through a new libgcc-compat file on ppc.
Jack,
To comment on this issue, I feel I would need more details, like:
- what symbols are you talking about? (probably ashldi3, etc,
as mentioned in the patches you refer to),
- what was the bug that was fixed in gcc 3.1?
- why has fixing this bug in gcc 3.1 caused you to add fixes to glibc?
If this is really about a few libgcc symbols only, I doubt there is
any serious problem hidden in there.
Regards,
Martin
--
To UNSUBSCRIBE, email to debian-gcc-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: