Swig error when I compile CEL on MacOSX

[mathieusuen@…]

Hi

When I compile CEL I get the following error on MacOSX:

$  jam
...patience...
...found 1076 target(s)...
...updating 230 target(s)...
C++ ./out/macosxx86/optimize/libs/celtool/camera.o 
C++ ./out/macosxx86/optimize/libs/celtool/navigation.o 
C++ ./out/macosxx86/optimize/libs/celtool/persisthelper.o 
C++ ./out/macosxx86/optimize/libs/celtool/stdmsgchannel.o 
C++ ./out/macosxx86/optimize/libs/celtool/stdpcimp.o 
Archive ./out/macosxx86/optimize/libs/libceltool-1.3.a 
ranlib: file: ./out/macosxx86/optimize/libs/libceltool-1.3.a(staticvarcleanup.o) has no symbols
Ranlib ./out/macosxx86/optimize/libs/libceltool-1.3.a 
ranlib: file: ./out/macosxx86/optimize/libs/libceltool-1.3.a(staticvarcleanup.o) has no symbols
RunSwig ./out/macosxx86/optimize/plugins/behaviourlayer/python/blcel.cpp 
swig error : Unrecognized option -force_cpusubtype_ALL
swig error : Unrecognized option -fno-common
Use 'swig -help' for available options.
...

I use swig 1.3.33:

SWIG Version 1.3.33

Compiled with /usr/bin/g++-4.0 [i386-apple-darwin9.1.0]
Please see http://www.swig.org for reporting bugs and further information

The rev of CEL is 3191 from the svn

Thanks

[sunshine]

This bug is caused by r2294. cel/plugins/behaviorlayer/python/Jamfile incorrectly passes $(CRYSTAL.CFLAGS) to the Swig rule in argument 4, which is supposed to be for Swig options only. Unfortunately, r2294 incorrectly assumes that $(CRYSTAL.CFLAGS) contains only options which also happen to be valid for Swig itself. Clearly, this is a bad assumption since $(CRYSTAL.CFLAGS) can validly contain any options accepted by the compiler tool chain.