All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: boost-1.36.0 fails when compiling; cannot find the compiler
Date: Fri, 13 Feb 2009 14:51:55 -0500	[thread overview]
Message-ID: <4995CF5B.6080103@balister.org> (raw)
In-Reply-To: <4995BFE1.7090900@dls.net>

[-- Attachment #1: Type: text/plain, Size: 4505 bytes --]

Mike (mwester) wrote:
> Boost 1.36.0 fails to build, do_compile log is below.  In a nutshell, it
> seems to have lost the PATH variable.  The 1.33.1 version builds just fine.
> 
> The compiler is present.  The PATH is set correctly, it appears, from
> the run.do_compile file.  So I can only presume that whatever "bjam" is,
> its resetting the PATH or something.
> 
> Nothing else has changed in the environment; 1.33.1 builds, 1.36.0
> doesn't, and I have no idea what the heck this "bjam" stuff is or how to
> debug it.
> 
> Any suggestions?  Does this work for anyone else?

It's been working on arm. And yes, the boost build system sucks :(

Philip

> 
> Mike (mwester)
> 
> 
> -----------
> + bjam -sTOOLS=gcc '-sGCC=armeb-linux-gnueabi-gcc -march=armv5te
> -mtune=xscale -mno-thumb-interwork -mno-thumb -mno-thumb-interwork
> -mno-thumb  -L/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib
> -Wl,-rpath-link,/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib
> -Wl,-O1 ${TARGET_LINK_HASH_STYLE}
> '\''-DBOOST_PLATFORM_CONFIG="boost/config/platform/linux-gnueabi.hpp"'\'''
> '-sGXX=armeb-linux-gnueabi-g++ -march=armv5te -mtune=xscale
> -mno-thumb-interwork -mno-thumb -mno-thumb-interwork -mno-thumb
> -L/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib
> -Wl,-rpath-link,/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib
> -Wl,-O1 ${TARGET_LINK_HASH_STYLE}
> '\''-DBOOST_PLATFORM_CONFIG="boost/config/platform/linux-gnueabi.hpp"'\'''
> -sGCC_INCLUDE_DIRECTORY=/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/include
> -sGCC_STDLIB_DIRECTORY=/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib
> -sNO_BZIP2=1 -sNO_ZLIB=1 '-sBUILD=release <optimization>space
> <inlining>on <debug-symbols>off' '-sPYTHON_VERSION=${PYTHON_VERSION}'
> --layout=system
> --builddir=/u/slug/slugos/tmp/work/armv5teb-linux-gnueabi/boost-1.36.0-r5/boost_1_36_0/armeb-linux-gnueabi
> --prefix=/usr --exec-prefix=/usr --libdir=/usr/lib --includedir=/usr/include
> warning: Graph library does not contain optional GraphML reader.
> note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the
> note: directories containing the Expat headers and libraries, respectively.
> warning: skipping optional Message Passing Interface (MPI) library.
> note: to enable MPI support, add "using mpi ;" to user-config.jam.
> note: to suppress this message, pass "--without-mpi" to bjam.
> note: otherwise, you can safely ignore this message.
> Building Boost.Regex with the optional Unicode/ICU support disabled.
> Please refer to the Boost.Regex documentation for more information
> (don't panic: this is a strictly optional feature).
> ...patience...
> ...patience...
> ...patience...
> ...found 5258 targets...
> ...updating 765 targets...
> MkDir1-quick-fix-for-unix bin.v2
> MkDir1-quick-fix-for-unix bin.v2/libs
> MkDir1-quick-fix-for-unix bin.v2/libs/math
> MkDir1-quick-fix-for-unix bin.v2/libs/math/build
> MkDir1-quick-fix-for-unix bin.v2/libs/math/build/gcc-4.3.1
> MkDir1-quick-fix-for-unix bin.v2/libs/math/build/gcc-4.3.1/release
> MkDir1-quick-fix-for-unix
> bin.v2/libs/math/build/gcc-4.3.1/release/threading-multi
> gcc.compile.c++
> bin.v2/libs/math/build/gcc-4.3.1/release/threading-multi/acosh.o
> armeb-linux-gnueabi-g++: : No such file or directory
> 
>     "armeb-linux-gnueabi-g++" "-march=armv5te" "-mtune=xscale"
> "-mno-thumb-interwork" "-mno-thumb" "-mno-thumb-interwork" "-mno-thumb"
> "-L/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib"
> "-Wl,-rpath-link,/u/slug/slugos/tmp/staging/armv5teb-linux-gnueabi/usr/lib"
> "-Wl,-O1" "${TARGET_LINK_HASH_STYLE}"  -ftemplate-depth-128 -O3
> -finline-functions -Wno-inline -Wall -fPIC -pthread
> -DBOOST_ALL_NO_LIB=1 -DBOOST_MATH_TR1_DYN_LINK=1 -DNDEBUG  -I"." -c -o
> "bin.v2/libs/math/build/gcc-4.3.1/release/threading-multi/acosh.o"
> "libs/math/build/../src/tr1/acosh.cpp"
> 
> ...failed gcc.compile.c++
> bin.v2/libs/math/build/gcc-4.3.1/release/threading-multi/acosh.o...
> ...removing bin.v2/libs/math/build/gcc-4.3.1/release/threading-multi/acosh.o
> gcc.compile.c++
> bin.v2/libs/math/build/gcc-4.3.1/release/threading-multi/asinh.o
> armeb-linux-gnueabi-g++: : No such file or directory
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2009-02-13 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 18:45 boost-1.36.0 fails when compiling; cannot find the compiler Mike (mwester)
2009-02-13 19:51 ` Philip Balister [this message]
2009-02-13 22:33   ` Erik Hovland
2009-02-16 19:35   ` Tim Ellis
2009-02-16 20:37     ` Philip Balister
2009-02-16 21:57       ` Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4995CF5B.6080103@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.