Re: [Boost-build] Cygwin static build run from the Windows command line fails

Subject: Re: [Boost-build] Cygwin static build run from the Windows command line fails
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2016-02-23 10:57:23

Beman,

Are you doing this from cygwin shell with cygwin build of b2 or from
Windows shell with msvc build of b2, or something else?

It seems that you actually use Windows shell with cygwin gcc, so when
Boost.Build asks gcc where its toolchain is installed it reports /usr, and
that clearly does not work in Windows shell.

Do you have a particular reason for using cygwin? If you would like to test
with gcc, would not mingw make for a more convenient option?

Thanks,

On Tue, Feb 23, 2016, 18:51 Beman Dawes <bdawes_at_[hidden]> wrote:

> The problem is that b2 invokes ar.exe and ranlib.exe in
> "/usr/x86_64-pc-cygwin/bin" rather than "c:/cygwin64/bin"
>
> Compiles and shared builds work OK because user-config.jam has this entry:
>
>     using gcc : c++03 : c:/cygwin64/bin/g++ : <cxxflags>"-Wconversion" ;
>
> As a work around, I've created a symlink from
> "c:/usr/x86_64-pc-cygwin/bin" to "c:/cygwin64/bin", and that works fine.
> But it would save a lot of aggravation if b2 just worked without the
> workaround. Incidentally, the msvc toolset does not have this problem.
>
> Thanks,
>
> --Beman
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>
-- 
Vladimir Prus
http://vladimirprus.com