Bug#384923: Dangling slave link to cc.1.gz

2006-08-27 Thread Matt Kraai
Package: gcc Version: 4:4.1.1-6 The daily man-db cron job produces the following error: > /etc/cron.daily/man-db: > mandb: warning: /usr/share/man/man1/cc.1.gz is a dangling symlink cc.1.gz is a slave link to gcc.1.gz, which no longer exists. The attached patch removes the slave link. -- Mat

Bug#384927: Dangling slave link to c++.1.gz

2006-08-27 Thread Matt Kraai
Package: g++ Version: 4:4.1.1-6 The daily man-db cron job produces the following error: > /etc/cron.daily/man-db: ... > mandb: warning: /usr/share/man/man1/c++.1.gz is a dangling symlink c++.1.gz is a slave link to g++.1.gz, which no longer exists. The attached patch removes the slave link. --

Bug#323325: ICE compiling gnustep-base's mframe.m

2005-08-15 Thread Matt Kraai
Package: gobjc-4.0 Version: 4.0.1-4 Severity: important gnustep-base fails to build on i386 because there is an ICE compiling mframe.m in i386: > gcc mframe.m -c \ > -MMD -MP -DGNUSTEP_INSTALL_PREFIX=/usr/lib/GNUstep/System > -DGNUSTEP_LOCAL_ROOT=/usr/local/lib/GNUstep/Local > -DGNUSTEP_N

Bug#323313: ICE compiling gnubik on i386 in size_binop

2005-08-15 Thread Matt Kraai
Package: gcc-4.0 Version: 4.0.1-4 Severity: important gnubik fails to build because there is an ICE: > if i486-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -DWIDGET_SET_gtk=1 > -DSCRIPTDIR=\"/usr/share/gnubik/scripts\" > -DGUILEDIR=\"/usr/share/gnubik/guile\" -DICONDIR=\"/usr/share/gnubik/icons\"

Bug#323512: FTBFS: Unable to find libstdc++.a.2.10.0

2005-08-16 Thread Matt Kraai
Package: gcc-2.95 Version: 2.95.4.ds15-22 Severity: serious gcc-2.95 fails to build on i386 because it cannot find libstdc++.a.2.10.0: > dh_movefiles -plibstdc++2.10-dev usr/lib/libstdc++.a.2.10.0 > usr/include/g++-3/ usr/share/info/iostream* > usr/lib/gcc-lib/i486-linux-gnu/2.95.4/libstdc++.{

Re: Your bug reports for various ICE's

2005-08-17 Thread Matt Kraai
On Wed, Aug 17, 2005 at 10:19:15AM +0200, Matthias Klose wrote: > apparently you're running a local buildd, please improve the reports: > > - add the preprocessed source. this should be easy, if you keep the > build tree in case of an error (you could even parse the build log > for the "See ht

Bug#323512: FTBFS: Unable to find libstdc++.a.2.10.0

2005-10-11 Thread Matt Kraai
tag 323512 patch thanks On Tue, Oct 11, 2005 at 08:48:10PM +0200, Lennert Buytenhek wrote: [that this bug is caused by the new dpkg-dev] Thanks for investigating this. In that case, the following, untested patch should fix this problem. -- Matt diff -ru gcc-2.95-2.95.4.ds15.orig/debian/rules2

Bug#323512: Tested patch

2005-10-13 Thread Matt Kraai
Howdy, I incorporated Lennert's suggestion and created a patch that fixes the problem on at least i386. -- Matt diff -ru gcc-2.95-2.95.4.ds15-old/debian/rules2 gcc-2.95-2.95.4.ds15/debian/rules2 --- gcc-2.95-2.95.4.ds15-old/debian/rules2 2005-10-13 06:58:48.0 -0700 +++ gcc-2.95-2.

Bug report for -m64 failure

2005-10-18 Thread Matt Kraai
Howdy, ncurses fails to build on i386 because it cannot compile with -m64: > gcc -m64 -O2 -g conftest.c >&5 > /usr/bin/ld: warning: ld-linux-x86-64.so.2, needed by /lib64/libc.so.6, not > found (try using -rpath or -rpath-link) > /lib64/libc.so.6: undefined reference to [EMAIL PROTECTED]' > /

Bug#334627: FTBFS: Link tests are not allowed after GCC_NO_EXECUTABLES

2005-10-18 Thread Matt Kraai
Package: gcc-3.4 Version: 3.4.4-9 Severity: serious gcc-3.4 fails to build: > checking for library containing gettext... configure: error: Link tests are > not allowed after GCC_NO_EXECUTABLES. > make[3]: *** [configure-target-libstdc++-v3] Error 1 > make[3]: Leaving directory `/tmp/buildd/gcc-3

Bug#334626: FTBFS: Link tests are not allowed after GCC_NO_EXECUTABLES

2005-10-18 Thread Matt Kraai
Package: gcc-4.0 Version: 4.0.2-2 Severity: serious gcc-4.0 fails to build: > checking for library containing gettext... configure: error: Link tests are > not allowed after GCC_NO_EXECUTABLES. > make[3]: *** [configure-target-libstdc++-v3] Error 1 > make[3]: Leaving directory `/tmp/buildd/gcc-4

Re: Bug report for -m64 failure

2005-10-19 Thread Matt Kraai
On Wed, Oct 19, 2005 at 09:59:24AM +0200, Matthias Klose wrote: > Matt Kraai writes: > > Howdy, > > > > ncurses fails to build on i386 because it cannot compile with -m64: > > > > > gcc -m64 -O2 -g conftest.c >&5 > > > /usr/bin/ld: warni

Bug#350688: Patch

2006-02-24 Thread Matt Kraai
tag 350688 patch thanks The attached patch integrates Daniel's patch into the build system. It fixes the problem on PowerPC. -- Matt diff -Nru gcc-2.95-2.95.4.ds15-orig/debian/patches/p-make-lang.dpatch gcc-2.95-2.95.4.ds15/debian/patches/p-make-lang.dpatch --- gcc-2.95-2.95.4.ds15-orig/debian/

Bug#314405: gcc-4.0: acats-killer.sh does not terminate

2005-06-15 Thread Matt Kraai
Package: gcc-4.0 Severity: normal acats-killer.sh does not terminate after the build finishes. As a result, it fills up the log file once the build chroot is removed: export testdir; cd testsuite/ada/acats; ${testdir}/run_acats === acats configuration === target gcc is /tmp/bu

Bug#316578: FTBFS: No rule to make target current_symbols.txt

2005-07-01 Thread Matt Kraai
Package: gcc-4.0 Version: 4.0.0ds1-11 Severity: serious When I tried to rebuild gcc-4.0, it failed as follows: baseline_name=`basename /tmp/buildd/gcc-4.0-4.0.0ds1/src/libstdc++-v3/config/abi/i486-linux-gnu`; \ baseline_parentdir=`dirname /tmp/buildd/gcc-4.0-4.0.0ds1/src/libstdc++-v3/config/a

Bug#316578: FTBFS: No rule to make target current_symbols.txt

2005-07-02 Thread Matt Kraai
On Sat, Jul 02, 2005 at 10:35:49AM +0200, Matthias Klose wrote: > severity 316578 important > tags 316578 + unreproducible > thanks > > works for the buildd's and me. I won't have a chance to retest this until Tuesday. If it still fails, I'll close this. -- Matt signature.asc Description: Di