[Bf-committers] Core dump mysterium

[Hans Lambermont]

Meino Christian Cramer wrote:

> From: hans@lambermont.dyndns.org (Hans Lambermont)
> > 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' ;-)
> 
>   Hrrrmm....I am confused....
>   What should not confuse with what ?

The 'configure' system is not part of the original blender. It is a new
system, proposed to replace the original blender makefiles used at NaN.

There are 2 make systems, completely independent of eachother.
One is the old NaN system, not for the failt-hearted I'm told ;-) and
the other is the new autotools system, which is not completely finished
yet.

> > >   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.
> 
>   In other words: If you got a bold and a nut, which do not fit
>   together: What is the wrong part ???  ;)

I think you don't get the point I'm trying to make. gcc3.x still
contains lots of bugs.
NaN for one didn't compile blender with gcc3.x while it was readily
available for a while.

> > >   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 ?
> 
>   The one with the following config is the "blender-runs-system":
>   CXX=gcc-2.95.3
>   CC=gcc-3.2.2
>   glibc2.2.5

I'm amazed ! This is very wrong. Don't try to mix gcc2.x and gcc3.x
unless you're an expert in compilers.

Auto* ppl: why doesn't configure check its findings ?

> > 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.
> 
>   I check source/nan_definitions.mk and found nothing special -- or
>   dont understand it at all.

Read again, I wrote 'nan_compile.mk' not 'nan_definitions.mk'.

I'll spell it out :
Change in the 'ifeq ($(OS),linux)' section:
    REL_CFLAGS  += -O2
    REL_CCFLAGS += -O2
to
#    REL_CFLAGS  += -O2
#    REL_CCFLAGS += -O2

And use 'make' in blender/

This problem:

>   ====> make all in blender/extern
>   mkdir: cannot create directory `/home/mccramer/data/static/home/mccramer/ZZZ/newdir/../lib/linux-glibc2.2.5-i386': No such file or directory

is because a topdir doesn't exist yet. I don't know which one, but try a
'mkdir -p' by hand if you don't know how to fix issues like this.

You will most probably stumble into other things the old NaN makefiles
expect to be in place 'a' where they are in 'b' on your system.

All in all I think you'll be happier with the autotools system. Now if
someone else in the know would help you configure it right you should be
able to find out if it's optimization issues you're dealing with or not.

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