Re: [Boost-build] Compiling 1.34.1 on OpenSUSE 10.3

From: Ruediger Berlich (ruediger.berlich_at_[hidden])
Date: 2007-10-25 14:23:47

Hi there,

thanks for the hints. Here is how I got the library to compile on OpenSUSE
10.3 . Note that I did not have time to check whether everything works yet. 

- made sure the python-devel package was installed (has the Python.h file
and is *not* installed by default!)
- Ran configure
- Went to the boost_1_34_1/tools/jam/src directory
- Ran "./build.sh gcc --debug"
- From the top directory
ran "./tools/jam/src/bin.linuxx86.debug/bjam --user-config=user-config.jam"

Probably the "configure" call was'nt even necessary in this case ?

I am particularly unsure whether the compiler bug you mention also applies
to the configuration of the actual library files (rather than only bjam). 

If so: where would I have to add the compiler flag ? BTW, I believe the flag
is not called --fno-strict-alias , but  --fno-strict-aliasing

Thanks and best Regards,
Ruediger

Rene Rivera wrote:
> Vladimir Prus wrote:
>> On Wednesday 24 October 2007 18:27:30 Ruediger Berlich wrote:
>>> OpenSUSE 10.3 is still delivered with Boost 1.33.1 . Hence I've
>>> downloaded Boost 1.34.1 and tried to compile it. I ran the configure
>>> script and then make. The resulting bjam immediately dies with an error:
>>>
>>> ./tools/jam/src/bin.linuxx86/bjam  --user-config=user-config.jam
>>> /bin/sh: line 1:  2090
>>> Speicherzugriffsfehler  ./tools/jam/src/bin.linuxx86/bjam
>>> --user-config=user-config.jam
>>>
>>> "Speicherzugriffsfehler" means "memory access violation".
>>>
>>> This is on a Pentium-D dual-core system (4GB main memory) running with a
>>> 32-bit Linux kernel 2.6.22, g++ 4.2.1 .
>> 
>> Rene,
>> does this sound like that alias analysis issue with g++ 4.2?
> 
> Yep, it's the aliasing problem with gcc-4.2
> 
>> Have we figured the
>> exact cause of this crash,
> 
> Nope, other than it's a compiler bug.
> 
>> and any approach for working it around?
> 
> The only work around I know of is to compile a debug version, or with
> --fno-strict-alias, IIRC.
>