From: David Abrahams (dave_at_[hidden])
Date: 2003-03-05 10:22:57
> Glad to see the darwin_notes are of some interest. Scott is
> absolutely correct: /usr/local_cci/gcc-3.2.2 is my own
> installation-specific directory name, a result of installing gcc with
> Perhaps someone could comment on the correct procedure for specifying
> a special -L path in the toolset darwin-tools.jam. I don't understand
> bjam usage well enough to prepend my special directory to the library
> search path.
[Boost.Build questions should go to the jamboost list]
Anyway, is it a fixed directory that you want in the library search
path, does it depend on the installation, or is it always someplace
relative to the rest of the toolset installation? Should it always go
in the library path for this toolset, or only when building
> ----- Original Message ----- From: "Scott A. Smith"
> <ssmith_at_[hidden]> Date: Tuesday, March 4, 2003 5:25 am Subject:
> [C++-sig] OSX darwin-tools glitch?
>> For fun I have once again tried to build Boost.Python using OSX.
>> Nothing worked well, so I decided I better follow the directions
>> recently posted: http://cci.lbl.gov/boost/ (darwin_notes). I rebuilt
>> gcc, rebuilt python, then tried BP w/ latest CVS. Although there are
>> lots of warnings, everything proceeded up to the end of the BP
>> build. Then I get these complaints:
>> ld: can't open: /usr/local_cci/gcc-3.2.2/lib/libstdc++.a (No such
>> file or directory, errno = 2) ld: can't open:
>> darwin6.4/3.2.2/libgcc.a(No such file or directory,
>> Having a look in the darwin-tools.jam file in the boost/tools/build
>> directory, I found that local-cci is explicitly used. My (plain)
>> install of GCC put the libraries into /usr/local/lib rather that
>> libstdc++.a /usr/local_cci/gcc- 3.2.2/lib. I altered the
>> darwin-tools.jam file to reflect this and the BP build then ran to
>> completion and produced libboost_python.dylib.
>> Am I doing something wrong or is there a glitch in the darwin-
>> tools.jamfile? I am not familiar with the directory /usr/local_cci,
>> perhaps Nick just used that for his GCC install?
>> Thanks & many thanks to Nick for putting up his build directions,
>> _______________________________________________ C++-sig mailing list
>> C++-sig_at_[hidden] http://mail.python.org/mailman/listinfo/c++-sig
> _______________________________________________ C++-sig mailing list
> C++-sig_at_[hidden] http://mail.python.org/mailman/listinfo/c++-sig
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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