Some time ago we found out that bigloo needed to be built with 'gcc -O2' on
ARM platforms, when using gcc-3.3, since with -O3 some failure occured when
building bdb. Moreover that bug appeared to be fixed in gcc-3.4, and
gcc-2.95 is not able to build bigloo correctly either.
But finally, it appears that even with 'gcc-3.3 -O2' and gcc-3.4 (3.4-0pre4)
there is a problem, which shows up at least in bdb, bmem, and skribe, when
those programs early get a segfault.
Since the old build failure on arm was that using -O3 prevented to build
bdb, it could well be that although -O2 allows it to build, the generated
code is bad.
I'll try to build at -O0, and then at -O1 if -O0 worked, and will let you
know. I should also have a closer look at how gcc-3.2 performs, but that
would be a pain to have to use it, since it's supposed to be phased out from
Debian...
--
Yann Dirson <[EMAIL PROTECTED]> | Why make M$-Bill richer & richer ?
Debian-related: <[EMAIL PROTECTED]> | Support Debian GNU/Linux:
Pro: <[EMAIL PROTECTED]> | Freedom, Power, Stability, Gratuity
http://ydirson.free.fr/ | Check <http://www.debian.org/>
