Re: [Boost-users] Failed gcc link and targets

13 Apr 2007

      Douglas,

Where did you get the bjam executable you used?

Are you running bjam from the msys command prompt or from a windows
command prompt?

What version of MINGW are you using?

At one point I had to use the standard command prompt to build boost.  I
would add the directory to the GCC binary to my PATH variable and open
up a standard command prompt (though it looks like bjam now finds mingw
automatically).  I would use the stage option to build everything so my
command line was:

bjam "-sTOOLS=mingw" stage

I see in my stage directory libboost_program_options-mgw.lib, so
something must have worked.  I do notice that in your output there is
a .a extension on the library.  Maybe you need to clean out some of the
cruft left from the older -TOOLS=gcc and start fresh.  I think the
following command will do it:

bjam "-sTOOLS=mingw" clean

More resources:
http://www.boost.org/tools/build/v1/mingw-tools.html

Hope this helps,
- David

On Thu, 2007-04-12 at 12:54 -0700, Douglas Linford wrote:
...
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
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users