[Bf-committers] Core dump mysterium

Hans Lambermont bf-committers@blender.org
Sun, 30 Mar 2003 13:00:05 +0200


Meino Christian Cramer wrote:

>   configure --disable-openal
...
>   So, all optimization that is active while compiling is coming "from
>   inside" the source tree (as prefereces or such).

Please don't confuse the newly proposed build system with code from
'inside the source tree' ;-)

>   (rhymes wins!;) into the output of make: There are some -O2's and
>   some -fxxxyyyzzz...but all those are not set by me.

It must be possible to add an argument to configure such that it removes
all optimization. I don't know how, as I'm not familiar with the auto*
tools.

>   If the glibc would be b0rken, other programs would have also
>   problems (I think).

Not necessarily, but most probably yes.

>   Would it be possible, that the blender sources are not
>   gcc-3.2.2-ready?

hehe :) nice way of putting it. Turn it around: gcc-3.2.2 is not fully
matured yet to compile gcc-2.9x (or various other non-gcc compilers)
code.

>   The same compilation algo is used on the system, where the compiled
>   blender runs fine.

Ehhm, now you've got me confused. What system is this ?

Did you try a build using the traditional makefiles ? You can set the
optimization flags in source/nan_compile.mk for the whole system per
platform.

regards,
   Hans
-- 
http://lambermont.webhop.org/   () ascii ribbon campaign - against HTML mail,
                                /\ vCards and proprietary formats