[C++-sig] Re: boost.python on OS X 10.3 (Panther)

[Sean Spicer]

Okay...this is what I get now:

boxster.local 13> bjam "-sTOOLS=darwin -sBUILD=debug 
-sBUILD=<warnings>off -sRUN_ALL_TESTS=1 test"
-sBUILD=debug-tools.jam: No such file or directory
-sBUILD=<warnings>off-tools.jam: No such file or directory
-sRUN_ALL_TESTS=1-tools.jam: No such file or directory
test-tools.jam: No such file or directory
-sBUILD=debug-tools.jam: No such file or directory
-sBUILD=debug-tools.jam: No such file or directory
-sBUILD=<warnings>off-tools.jam: No such file or directory
-sBUILD=<warnings>off-tools.jam: No such file or directory
-sRUN_ALL_TESTS=1-tools.jam: No such file or directory
-sRUN_ALL_TESTS=1-tools.jam: No such file or directory
test-tools.jam: No such file or directory
test-tools.jam: No such file or directory
-sBUILD=debug-tools.jam: No such file or directory
-sBUILD=debug-tools.jam: No such file or directory
-sBUILD=<warnings>off-tools.jam: No such file or directory
-sBUILD=<warnings>off-tools.jam: No such file or directory
-sRUN_ALL_TESTS=1-tools.jam: No such file or directory
-sRUN_ALL_TESTS=1-tools.jam: No such file or directory
test-tools.jam: No such file or directory
test-tools.jam: No such file or directory
-sBUILD=debug-tools.jam: No such file or directory
-sBUILD=<warnings>off-tools.jam: No such file or directory
-sRUN_ALL_TESTS=1-tools.jam: No such file or directory
test-tools.jam: No such file or directory
<@boost!libs!python!test>crossmod_exception_a.so: required property 
<warnings>off incompatible with <warnings>on

Not much further....

sean

On Oct 29, 2003, at 6:25 PM, Rene Rivera wrote:

> [2003-10-29] David Abrahams wrote:
>
>> Sean Spicer <saspicer at mac.com> writes:
>>
>>> Well nuts...looks like I get the same error - I'm not too familiar
>>> with bjam, and in searching for the origination of the error I can't
>>> really find much other than the following lines in the Jamfile:
>>>
>>> bpl-test crossmod_exception
>>>    : crossmod_exception.py crossmod_exception_a.cpp
>>>    crossmod_exception_b.cpp
>>>    ;
>>>
>>> which, I must confess, I don't quite understand.
>>>
>>> The error sounds quite simple though, it's looks like it's just a
>>> conflict between the <warnings> setting (on v. off)
>>>
>>> Perhaps I'm missing something though ? I'll keep digging...
>>
>> I don't know why Rene added the <warnings>off requirement for OSX, but
>> you can deal with this by adding it to the BUILD request:
>>
>>    bjam ... "-sBUILD=<warnings>off"
>>
>> for example.
>
> I'm not sure why I added it either ;-) All I can think of now is that 
> once
> upon a time the build was getting so many warnings that it would fail.
>
> I'll go remove that requirement as soon as I get a chance.
>
>
> PS. It's good to hear that things are improving in the MacOSX world... 
> It
> gives me hope that I'll be able to port my software :-)
>
>
> -- grafik - Don't Assume Anything
> -- rrivera (at) acm.org - grafik (at) redshift-software.com
> -- 102708583 (at) icq
>
> _______________________________________________
> C++-sig mailing list
> C++-sig at python.org
> http://mail.python.org/mailman/listinfo/c++-sig
>
_______________________________________________________________________
Sean A. Spicer

"Your mind is a shovel, use it."  -anonymous

pgp key fingerprint: 8CED 19B7 3A3A BF54 B8E8  FB11 E044 F6B8 1585 9D54
pgp public key available at www.keyserver.net or pgpkeys.mit.edu (KEY 
ID: 15859D54)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/cplusplus-sig/attachments/20031029/fb923d43/attachment.pgp>