Raoul:

I apologize. I have been going back and forth with Doug Currie as well
concerning building on OS X, and I got the two discussions mixed up. The
problem you are seeing is different from his.

So: what would be helpful would be to have both your configure command
(with all arguments and options) along with the output.

Separately, it would be helpful to know what command was used to install
boost. I think that you have already provided this.


shap


On Mon, 2008-08-04 at 18:12 -0700, Raoul Duke wrote:
> > Just so I am clear, is the configure output that you sent produced with
> > or without the --with-boost options to configure?
> 
> i think i've been doing it w/out any --with-boost at all?
> ...
> checking for unicode/uchar.h... no
> checking for boostlib >= 1.33.1... yes
> checking whether the Boost::System library is available... yes
> checking whether the Boost::Filesystem library is available... yes
> configure: error: Could not link against  !
> 
> so i just tried it
> 
> a) --with-boost, i get:
> ...
> checking for unicode/uchar.h... no
> checking for boostlib >= 1.33.1... yes
> checking whether the Boost::System library is available... yes
> checking whether the Boost::Filesystem library is available... yes
> configure: error: Could not link against  !
> 
> b) --with-boost=/opt/local/var/macports/software/boost/1.35.0_2
> ...
> checking for unicode/uchar.h... no
> checking for boostlib >= 1.33.1... configure: error: We could not
> detect the boost libraries (version 1.33 or higher). If you have a
> staged boost library (still not installed) please specify $BOOST_ROOT
> in your environment and do not give a PATH to --with-boost option.  If
> you are sure you have boost installed, then check your version number
> looking in <boost/version.hpp>. See http://randspringer.de/boost for
> more documentation.
> 
> sincerely.
> _______________________________________________
> bitc-dev mailing list
> [email protected]
> http://www.coyotos.org/mailman/listinfo/bitc-dev

_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to