Mailinglist Archive: opensuse-packaging (249 mails)

[Richard Guenther <rguenther@xxxxxxx>]

On Mon, 22 Nov 2010, Dave Plater wrote:

> On 11/21/2010 03:25 PM, Cristian Rodríguez wrote:
> > El 21/11/10 10:22, Dave Plater escribió:
> >
> >   
> > > Thanks, now it's fallen into the wrong hands :-)
> > >     
> > :-)
> >
> >   
> > > I had a package that failed (gcc froze) on one lib when anything more
> > > than -o0 was used, that would have been easier than patching SConscript.
> > > Dave P
> > >     
> > FORTIFY_SOURCE has nothing to do with optimization...if GCC freezes then
> > there is a bug in the compiler..
> >   
> I blinked and saw the -D in -D_FORTIFY_SOURCE pity it won't work with
> -o0 :-! .
> COLLADASaxFrameworkLoader which won't build with > -o0 won't build on my
> local system with -j 2 either, it goes "out of memory".
> I've initialized a build in home:plater:blender > openCOLLADA with -o2
> and after hanging for 1/2 hour it's on :
>
> g++ -o
> COLLADASaxFrameworkLoader/obj/posix/x86_64/debuglibxml/src/generated14/COLLADASaxFWLColladaParserAutoGen14PrivateNameMap.os
> -c -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector
> -funwind-tables -fasynchronous-unwind-tables -g -ggdb
> -DGENERATEDSAXPARSER_XMLPARSER_LIBXML -DGENERATEDSAXPARSER_VALIDATION
> -fPIC -ICOLLADASaxFrameworkLoader/include
> -ICOLLADASaxFrameworkLoader/include/generated14
> -ICOLLADASaxFrameworkLoader/include/generated15
> -ICOLLADABaseUtils/include -IGeneratedSaxParser/include
> -ICOLLADAFramework/include -IExternals/MathMLSolver/include
> -IExternals/MathMLSolver/include/AST -I/usr/include/libxml2
> COLLADASaxFrameworkLoader/src/generated14/COLLADASaxFWLColladaParserAutoGen14PrivateNameMap.cpp
> COLLADASaxFrameworkLoader/src/generated14/COLLADASaxFWLColladaParserAutoGen14PrivateFunctionMap.cpp:
> In member function 'void
> COLLADASaxFWL14::ColladaParserAutoGen14Private::initFunctionMap()':
> COLLADASaxFrameworkLoader/src/generated14/COLLADASaxFWLColladaParserAutoGen14PrivateFunctionMap.cpp:20:6:
> note: variable tracking size limit exceeded with
> -fvar-tracking-assignments, retrying without
>
> If this happens is it a bug or does it justify -o0?

*sigh*

Can you open a bug and attach preprocessed source?  -fno-var-tracking
should fix it as well (hopefully).

Richard.

-- 
Richard Guenther <rguenther@xxxxxxx>
Novell / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex