2010/6/15 JonY <[email protected]>
> On 6/15/2010 21:49, Ruben Van Boxem wrote:
>
>> Hmm, I think /mingw/bin or where your mingw-w64 toolchain bindir is should
>>> always be before MSYS's bindir, and that "." will certainly cause trouble
>>> with GCC's build system.
>>>
>>>
>> That's exactly why I said MSYS is special... and I don't know what will
>> break if I try to fix it. I still find it very odd that GMP configure even
>> knows about the name "link", because no mingw toolchain even has such a
>> thing. Shouldn't the script use ld or something else for its tests?
>>
>>
> IIRC MSYS post installs sets mingw/bin before MSYS bins, not after, and
> there was never a "." in my MSYS, never a good idea on anything resembling
> UNIX.
>
> Are you sure its a vanilla install?
>
I downloaded all MSYS packages, extracted them to the same dir, and
double-clicked msys.bat. Then I did "sh /postinstall/pi.sh" and "y" "y"
"m:/development/mingw64". It was pleased to not find "make" and said
everything was set up.
But: path *order* is okay, /usr/local/bin points to /local/bin and is empty
(until you put something in there yourself), then /mingw/bin, then /bin, so
mingw/bin is before MSYS bin. The "." comes from the /etc/profile file,
which explicitely prepends this to the rest of the path on line 19/21. I
just noticed Earnie's justification:
# My decision to add a . to the PATH and as the first item in the path list
# is to mimick the Win32 method of finding executables.
This still has nothing to do with the configure script even looking for a
"link" command IMHO.
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
