It seems Ubuntu has only static libraries for boost, 

/usr/lib/libboost_serialization.a
/usr/lib/libboost_serialization-gcc-1_33_1.a
/usr/lib/libboost_serialization-gcc-mt-1_33_1.a

While Fedora Core uses shared libraries, most specifically,

/usr/lib/libboost_serialization.so.2

As far as you know should this make a difference?

On Thu, 2007-06-07 at 13:34 -0700, Yigal Weinstein wrote:
> > > 2. For Ubuntu/Feisty does anyone know the correct path to the root of
> > > boost so as to get "-f" to work in btool?  No matter how I configure I
> > > still cannot get it to work?  That is I can't get $BOOST right where
> > > --with-boost=$BOOST I used to configure the making of barry.
> > 
> >     --with-boost=/usr
> > 
> > That should do the trick, as it expects include/ and lib/ to be in
> > the directory you specify.
> > - Chris
> Letting --with-boost=/usr fails.
> 
> ldd /usr/bin/btool | grep -i boost
> 
> produces nothing and I get the same failures as before.
> 
> The boost libraries in /usr/lib that I have are in libboost_.txt
> The boost include directory is /usr/include/boost.  I have included the
> files and folders I have in /usr/include/boost in include_boost.txt.  I
> don't know how to search for what is failing.  I have gone through
> config.log, config.status and neither of them seem to have problems.  
> 
> There are seemingly no reported errors in the make either, attached is
> the make standard output, make.log.
> 
> ?
> ---------------------------------------
> The program upldif works great and I have all my Evolution contacts now
> nicely stored in my 8100.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to