On Sat, 3 Jan 2009, Steven Watanabe wrote:
AMDG
Robert P. J. Day wrote:
The bjam syntax is out of date. echo "using python : $PYTHON_VERSION : %{_prefix} ;" >user-config.jam $BJAM --user-config=user-config.jam toolset=gcc debug release --prefix=$RPM_BUILD_ROOT/%{pfx} %{_prefix} install
"out of date" with respect to what?
It won't work with boost 1.37. It should have worked before 1.34.
remember, this is boost-1.31.0 so it might be that that bjam syntax is correct for back then, no?
Yep.
i got the LTIB packaging for boost-1.37.0 to work just by simplifying things down to their essense. the relevant part of the .spec file is now: ======================== ... %Build ./configure --prefix=$RPM_BUILD_ROOT/%{pfx}/%{_prefix} \ --with-bjam=/home/rday/bin/bjam make %Install rm -rf $RPM_BUILD_ROOT make install ... ========================= where /home/rday/bin/bjam is the result of doing a native configure, grabbing the native compilation of bjam, stashing it to the side where it would be found, then allowing boost to be build via LTIB, which (as i mentioned in an earlier post) wraps the entire build process with some aliases so that all compilation is done transparently with a cross-compile toolchain. and that seemed to work, barring a bunch of bzip2-related errors that i can see explained on the web page. so things seem to be humming along for now. thanks for all the guidance. i'm sure i'll have more silly questions in the near future. rday p.s. i'm assuming, then, that all that earlier python stuff you can see above is no longer necessary since, AFAICT, i don't need it now for 1.37.0. -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture. http://crashcourse.ca Waterloo, Ontario, CANADA ========================================================================