Rene, Thank you for the response. I'll see if I can make this clear. I am trying to build Ardour 2.0 on a Zenwalk 4.4.1 system with gcc-3.4.6 For Ardour 2.0, I need the following dependencies: 1. gcc/g++ 3.x or above 2. scons 0.96 or above http://www.scons.org/ 3. python (2.3.4 or above) http://www.python.org/ 4. gettext 0.12.1 or above 5. pkg-config 0.20 or abovehttp://www.freedesktop.org/software/pkgconfig/ 6. libtool http://www.gnu.org/software/libtool/ 7. JACK 0.100 or later ( libjack) http://jackaudio.org/ 8. XML2 http://xmlsoft.org/ 9. XSLT http://xmlsoft.org/XSLT/ 10. libart_lgpl 2.3.16 or later (libart, libart_lgpl )http://www.gnome.org/ 11. samplerate 0.1.2 or later (libsamplerate)http://www.mega-nerd.com/SRC/ 12. raptor (libraptor, libraptor1) http://librdf.org/raptor/ 13. lrdf ((librdf, librdf0) http://sourceforge.net/projects/lrdf 14. glib 2.10 or above (libglib2, libglib2.0, libglib2.0-0 )http://www.gtk.org/ 15. GTK+ 2.8 or above (plus other GTK requirements like Pango, ATK, Cairo) (libgtk2, libgtk2.0, libgtk2.0-0) http://www.gtk.org/ 16. libgnomecanvas (libgnomecanvas2, libgnomecanvas2-0)http://directory.fsf.org/libs/misc/libgnomecanvas.html 17. liblo (liblo, liblo0) http://liblo.sourceforge.net/ 18. boost (libboost http://boost.org/ 19. glib2-devel I have compiled and installed all of the above, (except for boost), and installed bjam. I didn't understand the configuration of bjam, so I skipped that, (maybe that is part of my problem), and just ran the following command from my boost_1_33_1 directory: bjam "-sTOOLS=gcc" install I received a python error, not sure what it was, it flashed by quickly, and a lot of the following errors that looked repetitive: ...failed gcc-Link-action bin/boost/libs/program_options/build/libboost_program_options.so/gcc/release/shared-linkable-true/libboost_program_options-gcc-1_33_1.so... ...skipped <@boost!lib>libboost_program_options-gcc-1_33_1.so for lack of <@boost!libs!program_options!build/libboost_program_options.so/gcc/release/shared-linkable-true>libboost_program_options-gcc-1_33_1.so... Then at the end of the compile I get the following errors: ...skipped <@boost!lib>libboost_program_options-gcc-mt-1_33_1.so for lack of <@boost!libs!program_options!build/libboost_program_options.so/gcc/release/shared-linkable-true/threading-multi>libboost_program_options-gcc-mt-1_33_1.so... FileClone /usr/local/lib/libboost_program_options-gcc-mt-1_33_1.so.1.33.1 HardLink /usr/local/lib/libboost_regex-gcc-d.so HardLink /usr/local/lib/libboost_regex-gcc-mt-d.so HardLink /usr/local/lib/libboost_regex-gcc.so HardLink /usr/local/lib/libboost_regex-gcc-mt.so HardLink /usr/local/lib/libboost_signals-gcc-d.so HardLink /usr/local/lib/libboost_signals-gcc-mt-d.so HardLink /usr/local/lib/libboost_signals-gcc.so HardLink /usr/local/lib/libboost_signals-gcc-mt.so HardLink /usr/local/lib/libboost_serialization-gcc-d.so HardLink /usr/local/lib/libboost_serialization-gcc-mt-d.so HardLink /usr/local/lib/libboost_serialization-gcc.so ...on 100th target... HardLink /usr/local/lib/libboost_serialization-gcc-mt.so ...skipped <@boost!lib>libboost_wserialization-gcc-d.so for lack of <@boost!lib>libboost_wserialization-gcc-d-1_33_1.so.1.33.1... ...skipped <@boost!lib>libboost_wserialization-gcc-mt-d.so for lack of <@boost!lib>libboost_wserialization-gcc-mt-d-1_33_1.so.1.33.1... ...skipped <@boost!lib>libboost_wserialization-gcc.so for lack of <@boost!lib>libboost_wserialization-gcc-1_33_1.so.1.33.1... ...skipped <@boost!lib>libboost_wserialization-gcc-mt.so for lack of <@boost!lib>libboost_wserialization-gcc-mt-1_33_1.so.1.33.1... HardLink /usr/local/lib/libboost_thread-gcc-mt-d.so HardLink /usr/local/lib/libboost_thread-gcc-mt.so HardLink /usr/local/lib/libboost_filesystem-gcc-d.so HardLink /usr/local/lib/libboost_filesystem-gcc-mt-d.so HardLink /usr/local/lib/libboost_filesystem-gcc.so HardLink /usr/local/lib/libboost_filesystem-gcc-mt.so HardLink /usr/local/lib/libboost_date_time-gcc-d.so HardLink /usr/local/lib/libboost_date_time-gcc-mt-d.so HardLink /usr/local/lib/libboost_date_time-gcc.so HardLink /usr/local/lib/libboost_date_time-gcc-mt.so HardLink /usr/local/lib/libboost_iostreams-gcc-d.so HardLink /usr/local/lib/libboost_iostreams-gcc-mt-d.so HardLink /usr/local/lib/libboost_iostreams-gcc.so HardLink /usr/local/lib/libboost_iostreams-gcc-mt.so HardLink /usr/local/lib/libboost_prg_exec_monitor-gcc-d.so HardLink /usr/local/lib/libboost_prg_exec_monitor-gcc-mt-d.so HardLink /usr/local/lib/libboost_prg_exec_monitor-gcc.so HardLink /usr/local/lib/libboost_prg_exec_monitor-gcc-mt.so HardLink /usr/local/lib/libboost_test_exec_monitor-gcc-d.so HardLink /usr/local/lib/libboost_test_exec_monitor-gcc-mt-d.so HardLink /usr/local/lib/libboost_test_exec_monitor-gcc.so HardLink /usr/local/lib/libboost_test_exec_monitor-gcc-mt.so HardLink /usr/local/lib/libboost_unit_test_framework-gcc-d.so HardLink /usr/local/lib/libboost_unit_test_framework-gcc-mt-d.so HardLink /usr/local/lib/libboost_unit_test_framework-gcc.so HardLink /usr/local/lib/libboost_unit_test_framework-gcc-mt.so HardLink /usr/local/lib/libboost_program_options-gcc-d.so HardLink /usr/local/lib/libboost_program_options-gcc-mt-d.so HardLink /usr/local/lib/libboost_program_options-gcc.so HardLink /usr/local/lib/libboost_program_options-gcc-mt.so ...failed updating 46 targets... ...skipped 54 targets... ...updated 84 targets... root[boost_1_33_1]# (Excuse the long output) So...is this helpful as to what is going on? Douglas

David, Tried the following: bjam "-sTOOLS=mingw" install Even worse... ...skipped <@boost!lib>libboost_prg_exec_monitor-mgw.a for lack of <@boost!lib>libboost_prg_exec_monitor-mgw-1_33_1.a... ...skipped <@boost!lib>libboost_prg_exec_monitor-mgw-mt.a for lack of <@boost!lib>libboost_prg_exec_monitor-mgw-mt-1_33_1.a... ...skipped <@boost!lib>libboost_test_exec_monitor-mgw-d.a for lack of <@boost!lib>libboost_test_exec_monitor-mgw-d-1_33_1.a... ...skipped <@boost!lib>libboost_test_exec_monitor-mgw-mt-d.a for lack of <@boost!lib>libboost_test_exec_monitor-mgw-mt-d-1_33_1.a... ...skipped <@boost!lib>libboost_test_exec_monitor-mgw.a for lack of <@boost!lib>libboost_test_exec_monitor-mgw-1_33_1.a... ...skipped <@boost!lib>libboost_test_exec_monitor-mgw-mt.a for lack of <@boost!lib>libboost_test_exec_monitor-mgw-mt-1_33_1.a... ...skipped <@boost!lib>libboost_unit_test_framework-mgw-d.a for lack of <@boost!lib>libboost_unit_test_framework-mgw-d-1_33_1.a... ...skipped <@boost!lib>libboost_unit_test_framework-mgw-mt-d.a for lack of <@boost!lib>libboost_unit_test_framework-mgw-mt-d-1_33_1.a... ...skipped <@boost!lib>libboost_unit_test_framework-mgw.a for lack of <@boost!lib>libboost_unit_test_framework-mgw-1_33_1.a... ...skipped <@boost!lib>libboost_unit_test_framework-mgw-mt.a for lack of <@boost!lib>libboost_unit_test_framework-mgw-mt-1_33_1.a... ...skipped <@boost!lib>libboost_program_options-mgw-d.a for lack of <@boost!lib>libboost_program_options-mgw-d-1_33_1.a... ...skipped <@boost!lib>libboost_program_options-mgw-mt-d.a for lack of <@boost!lib>libboost_program_options-mgw-mt-d-1_33_1.a... ...skipped <@boost!lib>libboost_program_options-mgw.a for lack of <@boost!lib>libboost_program_options-mgw-1_33_1.a... ...skipped <@boost!lib>libboost_program_options-mgw-mt.a for lack of <@boost!lib>libboost_program_options-mgw-mt-1_33_1.a... ...failed updating 942 targets... ...skipped 264 targets... Douglas On 4/11/07, David Daeschler wrote:

Hi Douglas,

...

bjam "-sTOOLS=gcc" install

I believe this line should read bjam "-sTOOLS=mingw" install

...

...skipped <@boost!lib>libboost_wserialization-gcc-d.so for lack of <@boost!lib>libboost_wserialization-gcc-d-1_33_1.so.1.33.1...

I think this is caused boost detecting the lack of some wstring support in MINGW.

I have built boost under mingw and get the same error with wserialization. The error just means you do not have support for wide character archives. Not really a showstopper in most cases. If you want wstring support, boost recommends using stlport with mingw.

Hope this helps, - Dave

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

David, I am trying to build Ardour 2.0 on a Zenwalk 4.4.1 Linux system with gcc-3.4.6 For Ardour 2.0, I need the following dependencies: 1. gcc/g++ 3.x or above 2. scons 0.96 or above 3. python (2.3.4 or above) 4. gettext 0.12.1 or above 5. pkg-config 0.20 or above 6. libtool 7. JACK 0.100 or later ( libjack) 8. XML2 9. XSLT 10. libart_lgpl 2.3.16 or later (libart, libart_lgpl ) 11. samplerate 0.1.2 or later (libsamplerate) 12. raptor (libraptor, libraptor1) 13. lrdf ((librdf, librdf0) 14. glib 2.10 or above (libglib2, libglib2.0, libglib2.0-0 ) 15. GTK+ 2.8 or above (plus other GTK requirements like Pango, ATK, Cairo) (libgtk2, libgtk2.0, libgtk2.0-0) 16. libgnomecanvas (libgnomecanvas2, libgnomecanvas2-0) 17. liblo (liblo, liblo0) 18. boost (libboost) (I downloaded boost from boost.org and copied the bjam executable to /usr/local/bin/bjam) 19. glib2-devel I have compiled and installed all of the above, (except for boost), and installed bjam. I didn't understand the configuration of bjam, so I skipped that, (maybe that is part of my problem), and I am running the following command from a root terminal in the boost_1_33_1 directory: bjam "-sTOOLS=gcc" install And I am not using minGW. I don't think I have it compiled because I have gcc-3.4.6 and didn't think I had to use anything else. So....by the looks of the mingw-tools link you sent me, it looks like it is for Windows, I'm on a Linux box. Douglas

David, Not a problem...I do remember when I initiate the bjam script, I did see some message in regards to python, (and maybe something else), but it doesn't stay there long as it continues the build and when it returns to prompt, there is too much info in the terminal to scroll back up and see the original message. Does the install script create a log file that you can go back and see any error messages? Douglas

on Fri Apr 13 2007, David Daeschler wrote:

Douglas,

...

Does the install script create a log file that you can go back and see any error messages?

You could try dumping bjam output to a file... For example:

bjam "-sTOOLS=gcc" install > out.txt

Add 2>&1 at the end of that line so you capture stderr as well as stdout.

...and then looking to see if you notice any messages. There may be another way to do this built into bjam.

There isn't, since the above is sufficient. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com