Package: gcc-3.3
Version: 1:3.3.4-7
Severity: serious
This bug report is the result of a conversation on #debian-release, as
IRC is volatile I capture it now.
If gcc-3.3 is built on a machine with binutils 2.15 gcc's ./configure
test
| checking linker --as-needed support... yes
will succeed and the resulting gcc will use --as-needed when linking,
although it does not depend on binutils (>=2.15). James Troup noticed
this on sparc "because it's broken the buildds".
Checking the buildlogs yielded that s390, ia64, arm are built with
older binutils, mips, mipsel, alpha and sparc are built with 2.15.
Heuristically I also tested with
dpkg --fsys-tarfile gcc-3.3.deb | grep -- --as-needed
which showed matches only in i386, mipsel and sparc
This breaks the compiler completely, minimal testcase:
$ echo 'int main () { return(0) ; }' > foo.c
$ gcc -Wall -o foo foo.c
/usr/bin/ld: unrecognized option '--as-needed'
/usr/bin/ld: use the --help option for usage information
collect2: ld returned 1 exit status
Possible "solutions":
1) Delay gcc-3.3's entry into sarge by making it Depend on binutils
2.15.
2) Make binary NMUs of the broken binaries. (Too late for today's
dinstall, mipsel takes more than 8 hours)
3) Ignore this bug and temporarily live with a non-working gcc in
sarge.
Personally I think 3 is not acceptable for gcc-3.3 but might be for
gcc-3.4 .(#263019).
cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"
