On Sun, Jan 25, 2009 at 2:50 PM, Kurt Roeckx <[email protected]> wrote: > On Sun, Jan 25, 2009 at 01:39:59PM +0100, Bastien ROUCARIES wrote: >> retitle 468555 -nostdlib linking provoque FTBS >> severity 468555 serious >> block 468555 512252 >> thanks >> >> Automatic linking with -nostdlib do not link with libgcc and therefore >> provoque a serious mess. Lib pthread is another exemple. >> >> For an exemple see bug 512252 that is under investigation, and will hurt us >> for next version of djvulibre, therefore serious because it could hurt poor >> soul >> programmer and lead to hard to debug bug :-/ > > It might be an annoying bug, but that does not mean it's a serious > error for this package.
Every c++ lib is linking by default with -nostdlib :( Depending of buildin used by gcc, gcc version and phase of moon, it could work or not work. Morevoer it could lead to hisenbug. Moreover it break at link time or even at run time of the program depending of the arch used. I think it is serious because we do not know the number of program affected at run time, and this the next compiler build ins are more important and therefore this bug could be generic. Do not really know if it is a goal for lenny or should be fixed after. An esay work arround is to add a -lgcc on the lib list but it is ugly and should die. For lenny it will be sufficient but we should fix this bug before this kind of workarround be generalized. Linking with nostdlib is evil and poor soul love band aid like -lgcc :( Regards Bastien -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
