On Sun, Sep 02, 2012 at 09:00:48PM +0200, Armin K. wrote:
> On 09/02/2012 07:01 PM, Ken Moffat wrote:
> >
> > ./bootstrap.sh --prefix=/scratch/ken/BOOSTmultishared/usr
> > ./b2 -j3 2>&1 | tee buildlog
> > ./b2 install threading=multi link=shared 2>&1 | tee instlog
> > ls -lR ../BOOSTmultishared/usr/lib/*.a
> > ls ../BOOSTmultishared/usr/lib/*.so* | wc -l
> >
> > That last one reports 52, i.e. 26 .so symlinks, and 26 actual
> > .so.1.51.0 shared libraries.
> >
> > ĸen
> >
>
> From what I know, if you use it like that, install target will cause
> packages to be rebuilt because you changed the options!
After you wrote that, I looked at my logs :
...patience...
...patience...
...patience...
...patience...
...found 27714 targets...
...updating 9802 targets...
So, it appears to do that. But since it only seemed to taks a
couple of seconds before it moved on to the 'common.mkdir' part of
the install, I'm not totally convinced :)
Looking at the build log, I see that libraries are created in
bin.v2/libs/${lib-name}/build/gcc-*/release/ in variously
link-static/threading-multi/ (*.a) and threading-multi/ (*.so).
So, yes, any non-default option will probably cause things to be
rebuilt. But threading-multi is now built by default, at least on
the OS we care about. I will admit that NOT specifying it will
cause redundant static libs to be built.
>
> Also, there is no need to modify prefix and bootstrap.sh script
>
> You can just pass --prefix=/path/to/boost/usr to the ./b2 install thing.
>
> See ./b2 --help for more info.
Yeah, I looked at that - its references to the old bjam instead of
b2 didn't thrill me with confidence that it was up to date [ it's
documentation - tends to be out of date until someone notices].
ĸen
> --
> http://linuxfromscratch.org/mailman/listinfo/blfs-dev
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
