severity 156662 wishlist thanks these are requirements for future versions. I don't see anything which would make the current libgcc_s.so.1 from gcc-3.0 worser than it is. Please correct me if I am wrong.
Jack Howarth writes: > Package: gcc-3.2 > Version: 3.2_3.2-0pre4 > Severity: grave > > On ppc, there will be version requirements, for properly building > and installing gcc-3.2, on the glibc and binutils installed. See > bug report 155606 for a description of this issue. The needed binutils > will likely be version 2.13.90.0.4-1 and, with luck and > cooperation, the correct libgcc-compat.S patches will be in > glibc 2.2.5-14. Without the Build-Depends on both these versions > of binutils and glibc, a libgcc_s.so.1 will be created with > missing versioning on the __divdi3 symbol on ppc. Also without > the Depends on these versions of glibc and binutils, there > can be problems building programs with gcc 3.2 on ppc due to > bugs in binutils fixed in current binutils-cvs (and the next > release, 2.13.90.0.4). Specifically, binutils will incorrectly > report a symbol conflict on __divdi3 which doesn't exist when > libc.so.6 is really only providing __divdi3 for run-time > resolution and NOT for linking. This has been fixed in binutils-cvs. > If we don't add the Build-Depends on binutils (>= 2.13.90.0.4) > and glibc (>= 2.2.5-14) for gcc-3.2 , we won't be able to properly > build gcc-3.2 against glibc 2.2.5-14 with the corrected > libgcc-compat.S code. If we don't add the Depends on the above > binutils and glibc versions, when gcc-3.2 becomes the default > compiler for builds in debian sid on ppc, we risk the build > machine getting out of sync and not building able to link programs. > Thanks in advance for slating this for the final gcc-3.2 release > (after Chris releases the new 2.13.90.0.4 binutils when it arrives > and glibc adopts the needed libgcc-compat patch from bug report > 155606 or resamples glibc upstream once Franz Sirl has that > added there). > Jack > ps Franz Sirl should be submitting his patch to libc-alpha today. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
