boost-1.47 fails to build when go is installed

[ltreugene@…]

Macports was selfupdate to 2.0.0. Before selfupdate, the port-tree was clean with "clean".

From the main.log

:notice:configure --->  Configuring boost
:debug:configure Using compiler 'Mac OS X llvm-gcc 4.2'
:debug:configure Executing org.macports.configure (boost)
:debug:configure Environment: CPATH='/opt/local/include' CFLAGS='-pipe -O2 -arch x86_64' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-pipe -O2 -arch x86_64' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.6' CXX='/xcode4.0.2/usr/bin/llvm-g++-4.2' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/boost/work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2 -m64' LDFLAGS='-L/opt/local/lib -arch x86_64' OBJC='/xcode4.0.2/usr/bin/llvm-gcc-4.2' FCFLAGS='-pipe -O2 -m64' INSTALL='/usr/bin/install -c' OBJCFLAGS='-pipe -O2 -arch x86_64' FFLAGS='-pipe -O2 -m64' CC_PRINT_OPTIONS='YES' CC='/xcode4.0.2/usr/bin/llvm-gcc-4.2'
:debug:configure Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/boost/work/boost_1_47_0" && ./bootstrap.sh --prefix=/opt/local --without-libraries=python --without-libraries=mpi --with-icu=/opt/local'
:debug:configure Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/boost/work/boost_1_47_0" && ./bootstrap.sh --prefix=/opt/local --without-libraries=python --without-libraries=mpi --with-icu=/opt/local 
:info:configure -n Building Boost.Build engine with toolset darwin... 
:info:configure 
:info:configure Failed to build Boost.Build build engine
:info:configure Consult 'bootstrap.log' for more details
:info:configure shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/boost/work/boost_1_47_0" && ./bootstrap.sh --prefix=/opt/local --without-libraries=python --without-libraries=mpi --with-icu=/opt/local " returned error 1
:error:configure Target org.macports.configure returned: configure failure: shell command failed (see log for details)
:debug:configure Backtrace: configure failure: shell command failed (see log for details)
    while executing
"$procedure $targetname"
:info:configure Warning: the following items did not execute (for boost): org.macports.install org.macports.configure org.macports.build org.macports.destroot
:notice:configure Log for boost is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/boost/main.log

[jmroot (Joshua Root)]

Please remember to preview and use WikiFormatting, fill in the Port field, and cc the maintainer.

[adfernandes (Andrew Fernandes)]

Can you attach the bootstrap.log file?

It should be located in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/boost/work/boost_1_47_0, I think.

I also noticed that you have XCode installed at /xcode4.0.2/. This should not be a problem, but perhaps boost is expecting it to live in /Developer/.

It would also help to attach MacPorts' main.log file using sudo port -dv install boost to enable more debugging output. Thanks!

[martin.eisenhardt@…]

I can confirm the problem, same thing over here.

[adfernandes (Andrew Fernandes)]

Aha! I think I see the error. According to the attached logs, your default C compiler is llvm-gcc-4.2, correct?

This compiler is not supported by boost. You can't compile boost without a very recent version of llvm; currently, I do not believe that apple ships a compiler that can compile boost.

Have you used gcc-select to make llvm the default compiler?

How are you compiling boost? Is it choosing llvm itself?

Thanks, -Andrew.

[ltreugene@…]

Hi,

I did not use gcc_select so far to set the llvm as default compiler. Due to I need to test/debug iphone app, I have XCode 4.2 and I think Apple uses llvm-gcc-4.2 as its compiler.

I tried to compile booth due to MongoDB has dependency on it.

[martin.eisenhardt@…]

I am not using LLVM and get the same error - minus the LLVM-related lines in the log. The relevant portion in my log file reads as follows:

:debug:configure configure phase started at Fri Aug  5 13:14:54 CEST 2011
:notice:configure --->  Configuring boost
:debug:configure Using compiler 'Mac OS X gcc 4.2'
:debug:configure Executing org.macports.configure (boost)

So, no LLVM, but still the same error.

[adfernandes (Andrew Fernandes)]

So, no LLVM, but still the same error.

Can you lease attach the booststrap.log file? Not the MacPorts' main.log; the main.log file is created by MacPorts and it probably thinks it is using gcc, but the bootstrap.log file will say what boot is actually using.

Thanks!

[martin.eisenhardt@…]

Just attached my bootstrap.log - still looks like it is using gcc, but I cannot make much of the errors it shows.

[martin.eisenhardt@…]

Cc Me!

[gamperl@…]

Cc Me!

[adfernandes (Andrew Fernandes)]

Hmm... I've been playing with this, and I cannot get boost to fail it's install.

One thing I notice about the booststrap.log errors that have been attached; they use "smart quotes" in a way that makes me wonder if there are locale issues at play, UTF-8 encodings versus Latin1 or so on.

Anyone that wants to jump in here, I'm ready to hear opinions.

(I think I've said this before, many times and many ways... I hate the boost build system. There is a cmake version available, but it still needs work, especially with regard to MPI and Python integration.)

[ltreugene@…]

My system is set as

LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8

I don't mind to set it to Latin1 and see whether the problem can be fixed by this.

[ltreugene@…]

I tried it and set the

LANG=en_US.ISO-8859 and LC_ALL=en_US.ISO-8859. The build still failed.

Let me attach the log for you to check.

[adfernandes (Andrew Fernandes)]

Thanks for checking this; much appreciated.

Unfortunately, the way that boost gets built is that it first builds its own build system bjam, not the same bjam that you can download from their repository. This system is python-like and completely undocumented. It is also built in C. It may or may not be using the LANG and LC_ALL environment variables as it should.

Besides, I'm still guessing what the problem might be; the language issue was only a wild guess based on the encoding of the uploaded logs. :-(

[gamperl@…]

The problem is caused by 'go'. After uninstalling the 'go' port, everything works find. For more detail see: #30203

[martin.eisenhardt@…]

I can confirm that uninstalling go solves the problem. It is really a shame that boost and go won't go together on the same machine ... :(

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #31129.

If this is only a problem with "go" being present, then you can prevent it using a code block like the one found in ImageMagick or nodejs. But it sounds like this is really a bug in "go" that should be fixed there since it would probably affect many other ports.

[adfernandes (Andrew Fernandes)]

This will, I hope, be fixed with #31169.

[susheel.varma@…]

uninstalled go and then installed boost.