|
Boost Users : |
From: Markus Ruettimann (toomy_at_[hidden])
Date: 2003-12-26 05:06:51
Hi Dave,
Sorry for the incomplete report.
STLPort was built with the gcc-cygwin.mak makefile.
I have built the bjam and boost from within the console of winXP.
I realy looked for the prebuilt bjam.exe, could not find it anywhere :-/
The build vommand is
bjam "-sTOOLS=gcc-stlport" "-sSTLPORT_ROOT=C:\develop\cpp\STLport-4.6" >
buildResult.txt
I snipped some of the errors, one of the "File or Path name too long" and
the other "Thread support is unavailible" These are the only kind of
errors i get.
I have errors such as:
--- snip ---
Assembler messages:
FATAL: can't create
libs\regex\build\bin\libboost_regex.lib\gcc-stlport\release\runtime-link-dynamic\stlport-anachronism
s-on\stlport-cstd-namespace-std\stlport-debug-alloc-off\stlport-iostream-on\stlport-version-4.5.3\c_regex_traits_common.
obj: File or path name too long
--- snip ---
In file included from libs/thread/src/condition.cpp:12:
C:/develop/cpp/boost-1.30.2/boost/thread/condition.hpp:17:5: #error Thread
support is unavailable!
In file included from libs/thread/src/condition.cpp:14:
--- snip ---
Thanks very much for your effort.
Markus
On Thu, 25 Dec 2003 17:29:35 -0500, David Abrahams
<dave_at_[hidden]> wrote:
> Markus Ruettimann <toomy_at_[hidden]> writes:
>
>> Hi all
>> I'm an enthusiastic user of boost since quite a long time. I used
>> MSVC6.0 so far.
>> How ever, I changed to cygwin g++ 3.3.1 for project reasons.
>> I have succesfuly built the latest STLPort version (4.6) and I also
>> use it successfully.
>>
>> How ever, I am not able to build the toolset gcc-stlport. There are
>> errors in the threadding
>> lib and elsewhere, and such ugly things as "to long path names" errors
>> in the console.
>
> Can you please post the exact command you're using to build with, and
> a few of the error messages?
>
>> Does anybody know how to build this toolset and link them together as
>> one static lib?
>>
>> I use boost-1.30.2 with cygwin g++ 3.3.1 on winXP professional.
>>
>> PS: When I build the bjam stuff, what builds without any errors, it
>> uses the MSVC compiler (the output it creates looks like this).
>
> Like what?
>
>> Is this a problem?
>
> It's fine to build bjam with MSVC as long as you're using it from a
> windows command-prompt. If you intend to build from a Cygwin bash
> command-prompt, you need to build bjam from within Cygwin.
>
> That said, I'm not sure why everyone seems to want to rebuild bjam
> when they could download prebuilt binaries.
>
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net