Re: [jamboost] Milestone 2 getting closer

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-10-25 00:09:47

David Abrahams wrote:

>>This means that all libraries are now buildable on gcc and Milestone
>>2 is almost reached. Only some examples need to be added, some docs
>>tweaked and a package created.
>>
>>Dave, in the meantime, can you check that everything is buildable on 
>>your machine? I'm especially interested if
>>
>> bjam --v2 libs/python/example/getting_started1
> 
> gcc.link-dll libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/boost_python.so
> libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/numeric.o: In function `_ZN5boost6python7numeric35_GLOBAL__N_.._src_numeric.cpphUHPId18throw_load_failureEv':
> /cygdrive/c/boost/libs/python/build/../src/numeric.cpp:29: undefined reference to `__imp__PyExc_ImportError'

<snip>

> collect2: ld returned 1 exit status
> 
> g++ -g -L/usr/lib/python2.2/config -lpython2.2.dll -o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/boost_python.so -Wl,-soname,boost_python.so -shared libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/numeric.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/list.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/long.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/dict.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/tuple.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/str.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/aix_init_module.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/from_python.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/registry.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/type_id.o libs/python/build/
b!
> in/gcc/debug/shared-true/main-target-boost_python/enum.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/class.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/function.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/inheritance.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/life_support.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/pickle_support.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/errors.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/module.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/builtin_converters.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/arg_to_python_base.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/iterator.o libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/object_protocol.o libs/python/build
/!
> bin/gcc/debug/shared-true/main-target-boost_python/object_operators.o 

Ehmm... I would say that symblos from python's dll are not found. Don't 
know why. Does cygwin require "implib"? Is "python2.2.dll" something 
that it can understand?

> ...failed gcc.link-dll libs/python/build/bin/gcc/debug/shared-true/main-target-boost_python/boost_python.so...
> MkDir1 libs/python/example/bin/gcc/debug/shared-true
> : not found
> mkdir: cannot create directory `\r': No such file or directory
> 
> mkdir libs/python/example/bin/gcc/debug/shared-true 
> 
> ...failed MkDir1 libs/python/example/bin/gcc/debug/shared-true...
> ...skipped libs/python/example/bin/gcc/debug/shared-true/main-target-getting_started1 for lack of libs/python/example/bin/gcc/debug/shared-true...
> ...skipped <libs!python!example/gcc/debug/shared-true>getting_started1.o for lack of libs/python/example/bin/gcc/debug/shared-true/main-target-getting_started1...
> ...skipped <libs!python!example/gcc/debug/shared-true>getting_started1.so for lack of <libs!python!build/gcc/debug/shared-true>boost_python.so...

> To get these I had to change the line endings on gcc.jam -- otherwise
> I got many more
> 
> ^M:not found
> 
> messages. This is as a result of the fact that my Cygwin is installed
> with Unix line endings but my CVS is checked out with Windows line
> endings. I think we ought to work around this in the bjam source but I
> didn't see an easy way to do it yet.

Do we need to strip all '\r' symbols?

> Aside from that there appear to be some problems with type traits
> which are preventing me from getting very far. 

What are those problems?

> It also seems to be
> trying to link bpl.so despite the fact that one of its objects failed
> to build... 

Hmm... the output above indicates opposite. The worst I can suspect is 
wrong extension somewhere.

> but I'm a little uncertain of that one [things have been
> really scattered here since I've been trying to get my email working
> all day :( ]

I see.

- Volodya