Build error: "duplicate initialization of gcc"
I downloaded boost 1.37.0, unzipped and ran $ ./configure $ make install It dies reliably with: ------------------ ./tools/jam/src/bin.linuxx86/bjam -sICU_PATH=/usr --user-config=user-config.jam --prefix=/home/timm --exec-prefix=/home/timm --libdir=/home/timm/lib --includedir=/home/timm/include install error: at /home/timm/downloads/boost_1_37_0/tools/build/v2/build/project.jam:846 error: duplicate initialization of gcc with the following parameters: error: version = 4.3.2 error: previous initialization at /home/timm/downloads/boost_1_37_0/tools/build/v2/build/project.jam:846 Not all Boost libraries built properly. ------------------- This is on a relatively unmodified Ubuntu Intrepid linux install. I could only find one other mention of this problem on the web and it was a mailing list post with no answer, so I'm apparently doing something quite unusually wrong. FWIW, the reason I'm building from source rather than using a package is that the Ubuntu packages don't seem to provide a binary lib for MPI - am I missing something here? They provide header files, so it seems eccentric not to provide a package with libs. Tim
AMDG Tim Martin wrote:
I downloaded boost 1.37.0, unzipped and ran
$ ./configure $ make install
It dies reliably with: ------------------ ./tools/jam/src/bin.linuxx86/bjam -sICU_PATH=/usr --user-config=user-config.jam --prefix=/home/timm --exec-prefix=/home/timm --libdir=/home/timm/lib --includedir=/home/timm/include install error: at /home/timm/downloads/boost_1_37_0/tools/build/v2/build/project.jam:846 error: duplicate initialization of gcc with the following parameters: error: version = 4.3.2 error: previous initialization at /home/timm/downloads/boost_1_37_0/tools/build/v2/build/project.jam:846
Not all Boost libraries built properly. -------------------
This is on a relatively unmodified Ubuntu Intrepid linux install. I could only find one other mention of this problem on the web and it was a mailing list post with no answer, so I'm apparently doing something quite unusually wrong.
FWIW, the reason I'm building from source rather than using a package is that the Ubuntu packages don't seem to provide a binary lib for MPI - am I missing something here? They provide header files, so it seems eccentric not to provide a package with libs.
Is there a site-config.jam lying around somewhere? Try running bjam manually with --debug-configuration and look for a line like notice: Loading site-config configuration file site-config.jam from path/to/site-config.jam . In Christ, Steven Watanabe
Steven Watanabe wrote:
AMDG
Tim Martin wrote:
I downloaded boost 1.37.0, unzipped and ran
$ ./configure $ make install
This is on a relatively unmodified Ubuntu Intrepid linux install. I could only find one other mention of this problem on the web and it was a mailing list post with no answer, so I'm apparently doing something quite unusually wrong.
FWIW, the reason I'm building from source rather than using a package is that the Ubuntu packages don't seem to provide a binary lib for MPI - am I missing something here? They provide header files, so it seems eccentric not to provide a package with libs.
Is there a site-config.jam lying around somewhere? Try running bjam manually with --debug-configuration and look for a line like notice: Loading site-config configuration file site-config.jam from path/to/site-config.jam .
I'm sure there is -- Debian package tends to create it. So the right solution is to remove using gcc : ...... ; from user-config.jam that configure produced, and run the same bjam command again. - Volodya
Vladimir Prus wrote:
Steven Watanabe wrote:
[1.37.0 build reports "duplicate initialization of gcc"]
Is there a site-config.jam lying around somewhere?
I'm sure there is -- Debian package tends to create it. So the right solution is to remove
using gcc : ...... ;
from user-config.jam that configure produced, and run the same bjam command again.
You're quite right. For the record, there's one in /etc/site-config.jam. When I did as you suggested the build went fine. Is this something that the configure script should pick up on, in an ideal world? Not that it matters to me since I have a workaround. Tim
Tim Martin wrote:
Vladimir Prus wrote:
Steven Watanabe wrote:
[1.37.0 build reports "duplicate initialization of gcc"]
Is there a site-config.jam lying around somewhere?
I'm sure there is -- Debian package tends to create it. So the right solution is to remove
using gcc : ...... ;
from user-config.jam that configure produced, and run the same bjam command again.
You're quite right. For the record, there's one in /etc/site-config.jam. When I did as you suggested the build went fine.
Is this something that the configure script should pick up on, in an ideal world? Not that it matters to me since I have a workaround.
In an ideal world, the configure script does not exist, and "bjam --configure" notices you already have a toolchain configured. Hopefully for 1.38. - Volodya
participants (3)
-
Steven Watanabe -
Tim Martin -
Vladimir Prus