[Top][All Lists]

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

Re: LT_PATH_NM uses too strict a check

From: JonY
Subject: Re: LT_PATH_NM uses too strict a check
Date: Sun, 26 Dec 2010 09:00:42 +0800
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20080213 Thunderbird/ Mnenhy/

Hash: SHA1

On 12/25/2010 21:46, Ximin Luo wrote:
> On 25/12/10 01:49, Bob Friesenhahn wrote:
>> What you are doing is not normal behavior.  A cross-compile is a build
>> in which the built binaries are not run on the build host and a
>> different set of build tools must be used.
> A lot of things aren't "normal behaviour", including cross-compiling in
> general. This is not a valid reason to dismiss my report. What's more, in my
> case, a "different set of build tools" is completely unnecessary. You would be
> using the *exact same tools* as in the non-cross-compile case.

No, cross compile is very normal, its expected to work fine by just
setting the triplets, that is what autotools is great for. You are cross
compiling as long as host != build. Setting --host without setting
- --build is assumed to be cross compile.

What GMP is doing is not normal, the way it uses those triplets. IMHO
they should really be using --with-arch or some such to set the CPU insn

I suppose you want to set both --build and --host to be equal to each
other when doing GMP.

Version: GnuPG v2.0.16 (MingW32)


Attachment: 0xED74C077.asc
Description: application/pgp-keys

reply via email to

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