Hello,
I'm currently looking at Bug #11280 which started biting me again with
hrev49327 after being absent for a while. I've circled it in pretty much
already, but now I need to make some modification in the sources (stuff
that goes in libbe.so) to get any further.
The problem is that the bug is very elusive, changes quickly make it go
away. And so far I've had no luck reproducing it with any self-built
libbe.so at all -- while with the libbe in the haiku hrev49327 package
(from the package repo) it happens very often. It already vanishes when
I use a libbe.so built by me from unmodified source on the same git
tag... so something significant enough must be different in the stuff I
build.
Unfortunately, reproducing a bit-identical libbe.so is impossible with
gcc2 generally, its name mangling includes a string of random chars in
certain symbol names (things in anonymous name spaces). However, the
symbol names alone hopefully shouldn't make a difference, so the
question is, are there other differences. (I did successfully build a
bit-identical gcc4-version of libbe.so, but that doesn't help right now)
For building on Linux I use the following commands:
../configure --use-xattr-ref --build-cross-tools x86_gcc2
../../buildtools/ --build-cross-tools x86
jam -q -j4 @nightly-anyboot
Is there anything otherwise special done on our build infrastructure?
Are there any necessary configure flags? Is there a UserBuildConfig that
I need? Any other differences?
Greetings,
Julian
