Modify

Opened 8 years ago

Closed 8 years ago

#2930 closed Bugs (invalid)

Error building boost, cannot find -lpython

Reported by: francois.chenais@… Owned by:
Milestone: Boost 1.39.0 Component: Building Boost
Version: Boost 1.38.0 Severity: Problem
Keywords: Cc:

Description

An error occurs while linking

bin.v2/libs/python/build/gcc-4.1.2/release/debug-symbols-on/inlining-on/threading-multi/libboost_python-gcc41-mt-1_38.so.1.38.0

bjam pass -lpython instead of lib with version; -lpython2.4 for me. All others targets are built.

I'm on a centOS 5.2 with :

  • python 2.4
  • boost-jam 3.1.12

Attachments (1)

boost-1.38.0-building-error.txt.gz (11.8 KB) - added by francois.chenais@… 8 years ago.
boost-1.38.0 building error

Download all attachments as: .zip

Change History (9)

Changed 8 years ago by francois.chenais@…

boost-1.38.0 building error

comment:1 Changed 8 years ago by Steven Watanabe

Run

bjam --help python.init

for more info.

comment:2 Changed 8 years ago by francois.chenais@…

I've tried setting

using python : 2.4 ;

in

tools/build/v2/user-config.jam

before reporting the bug. But without success.

The command line is

+ umask 022 + cd /home/cea/chenais/rpmbuild/BUILD + cd boost_1_38_0 + LANG=C + export LANG + unset DISPLAY ++ /usr/bin/python -c 'import sys; print sys.version[0:3]' + PYTHON_VERSION=2.4 + PYTHON_ROOT=/usr + EXPAT_INCLUDE=/usr/include + EXPAT_LIBPATH=/usr/lib64 + ICU_PATH=/usr + bjam -d2 --toolset=gcc variant=release debug-symbols=on inlining=on link=static,shared threading=multi

The attached file shows that bjam use 2.4 version of python.


Build request: object(property-set)@2263 <asynch-exceptions>off <debug-symbols>on <define>NDEBUG <exception-handling>on <extern-c-nothrow>off <inlining>on <link>shared <optimization>speed <os>LINUX <pch>on <preserve-test-targets>off <profiling>off <python-debugging>off <python>2.4 <rtti>on <runtime-debugging>off <runtime-link>shared <stdlib>native <target-os>linux <threadapi>pthread <threading>multi <toolset-gcc:version>4.1.2 <toolset>gcc <variant>release <warnings-as-errors>off <warnings>on

Target requirements: <conditional>@Jamfile</tmp/rpmbuild/BUILD/boost_1_38_0>%Jamfile</tmp/rpmbuild/BUILD/boost_1_38_0>.handle-static-runtime <define>BOOST_ALL_NO_LIB=1 <include>. <link>shared:<define>BOOST_ALL_DYN_LINK=1 <python>2.4,<target-os>linux:<python.interpreter>python <tag>@Jamfile</tmp/rpmbuild/BUILD/boost_1_38_0>%Jamfile</tmp/rpmbuild/BUILD/boost_1_38_0>.tag <toolset-msvc:version>7.1:<rtti>off <toolset-msvc:version>7.1_stlport4:<rtti>off <toolset>msvc:<define>_CRT_SECURE_NO_DEPRECATE <toolset>msvc:<define>_SCL_SECURE_NO_DEPRECATE <warnings>off


Am I wrong ?

comment:3 Changed 8 years ago by anonymous

Summary: Error buildinf boost, cannot find -lpythonError building boost, cannot find -lpython

comment:4 in reply to:  description ; Changed 8 years ago by Steven Watanabe

Replying to francois.chenais@gmail.com:

I'm on a centOS 5.2 with :

  • python 2.4
  • boost-jam 3.1.12

You may need a more recent version of boost-jam. Other than that, I have no idea what's going on. The build log refers to a libs/python/build/pythonlib target which I can't find any trace of in the source. My best guess is that the old version of bjam is causing the wrong build files to be selected.

comment:5 in reply to:  4 Changed 8 years ago by anonymous

Replying to steven_watanabe:

Replying to francois.chenais@gmail.com:

I'm on a centOS 5.2 with :

  • python 2.4
  • boost-jam 3.1.12

You may need a more recent version of boost-jam. Other than that, I have no idea what's going on. The build log refers to a libs/python/build/pythonlib target which I can't find any trace of in the source. My best guess is that the old version of bjam is causing the wrong build files to be selected.

I've tried with last bjam (3.1.17) but it fails with the same error.

comment:6 Changed 8 years ago by Steven Watanabe

Ok. Can you post the output from

    bjam --with-python --debug-configuration toolset=gcc link=static debug-symbols=on inlining=on threading=multi -n

comment:7 Changed 8 years ago by Vladimir Prus

Francois, can you please provide output Steven has requested?

comment:8 Changed 8 years ago by Vladimir Prus

Resolution: invalid
Status: newclosed

There's not enough information to reproduce or fix.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.