|
Boost-Build : |
Subject: Re: [Boost-build] Building libraries for gcc with cygwin
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2012-10-18 05:46:21
> -----Original Message-----
> From: Steven Watanabe [mailto:watanabesj_at_[hidden]]
> Sent: Tuesday, October 16, 2012 10:06 PM
> To: Boost.Build developer's and user's list
> Subject: Re: [Boost-build] Building libraries for gcc with cygwin
>
> AMDG
>
> On 10/16/2012 10:18 AM, Paul A. Bristow wrote:
> > I have gcc at C:\cygwin\bin\gcc.exe
> >
> > and g++ C:\cygwin\bin\g++.exe
> >
> > (using NetBeans to compile things OK, but now I need the Boost
> > libraries like Boost.Test)
> >
> > I have boost-trunk at my I: partition, and have built the MSVC libraries OK.
> >
> > cd /cygdrive/i/boost-trunk
> >
> > and doing a b2 thus
> >
> > b2 -a --build-dir=/cygdrive/i/boost-trunk toolset=gcc
> > --build-type=complete --without-python --without-mpi stage
> > threading=multi > build_gcc_dll_libs_trunk_16Oct12.log 2>&1
> >
> > Should I be concerned that gcc visibility says no.
> >
>
> I don't think so.
>
> > - g++ -shared-* supported : yes
> > - gcc visibility : no
> >
> > But clearly something is going horribly wrong from the rest of the
> > messages L (Full log attached)
> >
>
> I think I've seen this reported before. IIRC, the culprit is Boost.Locale. Does it work with
--without-locale?
As always, you are right :-)
Building now....
Performing configuration checks
- 32-bit : yes
- x86 : yes
- has_icu builds : no
warning: Graph library does not contain MPI-based parallel components.
note: to enable them, add "using mpi ;" to your user-config.jam
- gcc visibility : no
- long double support : no
Component configuration:
- atomic : building
- chrono : building
- context : building
- date_time : building
- exception : building
- filesystem : building
- graph : building
- graph_parallel : building
- iostreams : building
- locale : not building
- math : building
- mpi : not building
- program_options : building
- python : not building
- random : building
- regex : building
- serialization : building
- signals : building
- system : building
- test : building
- thread : building
- timer : building
- wave : building
...patience...
...patience...
...patience...
...patience...
...found 7901 targets...
...updating 2151 targets...
common.mkdir \cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic
common.mkdir \cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build
common.mkdir \cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build\gcc-3.4.4
common.mkdir \cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build\gcc-3.4.4\debug
common.mkdir \cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build\gcc-3.4.4\debug\threading-multi
gcc.compile.c++
\cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build\gcc-3.4.4\debug\threading-multi\lockpool.o
gcc.link.dll
\cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build\gcc-3.4.4\debug\threading-multi\libboost_atom
ic-gcc34-mt-d-1_52.dll.a
Creating library file:
\cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build\gcc-3.4.4\debug\threading-multi\libboost_atom
ic-gcc34-mt-d-1_52.dll.a
common.copy stage\lib\libboost_atomic-gcc34-mt-d-1_52.dll.a
\cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build\gcc-3.4.4\debug\threading-multi\libboost_atom
ic-gcc34-mt-d-1_52.dll.a
1 file(s) copied.
common.copy stage\lib\libboost_atomic-gcc34-mt-d-1_52.dll
\cygdrive\i\boost-trunk\boost\bin.v2\libs\atomic\build\gcc-3.4.4\debug\threading-multi\libboost_atom
ic-gcc34-mt-d-1_52.dll
1 file(s) copied.
But this is slightly worrying
- gcc visibility : no
and this
- g++ -shared-* supported : yes
is no longer shown either????
But some libraries are building (though I fear that I need to upgrade from gcc 3.4.4 from other
messages).
Thanks
Paul
--- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow_at_[hidden]
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk