[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bfd and cygpath

From: Peter Rosin
Subject: Re: bfd and cygpath
Date: Fri, 26 Apr 2013 23:55:25 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5

On 2013-04-26 23:48, Peter Rosin wrote:
> On 2013-04-26 18:51, NightStrike wrote:
>> On Fri, Apr 26, 2013 at 4:06 AM, Peter Rosin <address@hidden> wrote:
>>> You had LD=i686-w64-mingw32-gcc, which will not make libtool happy. You
>>> might try LD=i686-w64-mingw32-ld instead, but you shouldn't need to
>>> specify LD...
>> I'll try LD=i68...-ld, but libtool should really fix that.
> I humbly disagree. What you are doing is not supported. You are effectively
> "lying" (using the terminology of the libtool manual) to configure (by
> claiming you are on a MinGW host, when in fact you are on a Linux host).
> Compare with the Libtool manual section
> but think Linux/Wine instead of Cygwin as the build. When you have fixed
> this issue, you will probably bump into something else. E.g., I guess you
> should specify:
>      export lt_cv_to_host_file_cmd=func_convert_file_nix_to_w32
>      export lt_cv_to_tool_file_cmd=func_convert_file_nix_to_w32
> Further, will not the dependency tracking output from the MinGW gcc
> generate a bunch of w32 paths that mixes badly with Linux make?
> Are you absolutely sure that you have to "lie" to configure? Why not do
> the decent thing and leave --host unspecified so that config.guess can

Oops, --build, not --host.

> do its thing?
> And if you don't "lie", you might as well use a linux-hosted cross-compiler
> targeting mingw and just rely on wine to run testsuites etc. But even if
> you move from the "lying" case to the "fake" case (i.e. still using the
> mingw-hosted native compiler in wine), chances are that it will work
> better that the "lying" case. But I don't know that, haven't tried...
> The reason the "lying" and "fake" cases work when crossing from Cygwin
> to MinGW is that the true build system (Cygwin) understands w32 based
> paths (most of the time anyway). Your true build system (Linux) does not,
> so you are in uncharted territory.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]