On Mon, Jan 19, 2009 at 1:11 AM, Matthias Klose <d...@cs.tu-berlin.de> wrote: > Bastien ROUCARIES writes: >> On Mon, Jan 19, 2009 at 12:47 AM, Matthias Klose <d...@cs.tu-berlin.de> >> wrote: >> > hmm, I don't have the log of the failed build anymore. looks like >> > linking with -lgcc is sufficient. >> >> Ok seems like a gcc bug :( >> Libgcc is automagically added by gcc to every build :( > > No. > > [ generating libdjvulibre.la ... ] > /bin/bash ../libtool --mode=link g++ -DHAVE_CONFIG_H -I.. -I. -DNDEBUG -Wall > -O3 -Wno-non-virtual-dtor -pthread -DTHREADMODEL=POSIXTHREADS > -no-undefined \ [...] > ranlib .libs/libdjvulibre.a > > please note this is libtool-2.2, which adds -nostdlib, but not -lgcc.
Seems a libtool bug :( http://gcc.gnu.org/ml/gcc/2001-09/msg00262.html http://www.archivum.info/libt...@gnu.org/2005-03/msg00272.html gcc say it is not a gcc bug http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25460 Seems related to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468555 Do you prefer I open a bug to libtool or do you prefer to open it? Regards -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
