Hmm, could well be, I just downloaded a binary of bjam rather than building it, so I bet the default download is a windows build. I did get the install to work like this, however, my project doesn't find the boost includes, even though I installed to /usr/local, shouldn't they be picked up there? What autotools magic do I need if that isn't the case? Thanks Gaz -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of David Abrahams Sent: 24 October 2004 07:00 To: boost-users@lists.boost.org Subject: [Boost-users] Re: Bjam and cygwin "Foster, Gareth" writes:

Just for other peoples information (these mails show up in an searchable online archive somewhere afterall afaik), I fixed this problem by setting the path 'in a windows' way, rather than a unix way, even though I was building from the cygwin shell. That means ...

bjam "-sTOOLS=GCC" "--target=/usr/local" install

Becomes ...

bjam "-sTOOLS=GCC" "--target=c:\cygwin\usr\local" install

That's from memory, so excuse any slight inacuracies in the syntax there. It does get rid of the <directory-guist> weirdness.

Hope this helps somebody somewhere.

Regards

That's surely because you're using a bjam that was built for windows, not for Cygwin. If you rebuild bjam under Cygwin I think you'll see that Cygwin paths work. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users