2010/6/15 JonY <[email protected]>
> On 6/15/2010 18:47, Ruben Van Boxem wrote:
>
>> I have updated the MSYS package to provide an out-of-the-box solution for
>> problems with MSYS's link.exe and configure scripts. Should you still need
>> it, you can download the MSYS coreutils package from the mingw sourceforge
>> site under MSYS->coreutils.
>>
>> You don't have to explicitely redownload, as only one file has been
>> removed,
>> namely msys/bin/link.exe. If you have it, please remove it yourself if you
>> experience problems with a configure script and "link" is mentioned as the
>> cause.
>>
>>
> Hi,
>
> No, coreutils is not at fault, do not remove link.exe. It is due to
> configure not finding the correct "ld" linker.
>
I'm sure coreutils is not at fault, I believe it is a PATH order issue. It's
just that link.exe is not really useful/used, and a lot of projects have
trouble with it, some examples:
1) http://www.devkitpro.org/viewtopic.php?f=2&t=1758
2)
http://www.awake24.de/documents/cint/Compiling%20CINT%20on%20Windows.htm(cygwin,
yes, path order issue with link.exe, yes)
3)
https://wiki.mozilla.org/ReferencePlatforms/Win32#FURTHER_CONFIGURATION_DETAILS
4) I'm assuming an msys using MSVC is pretty funky as well, as link is not
what it seems anymore... (link is MSVC linker as well)
Anyways, ln.exe is better than link and I think not many configure scripts
use link as a file linker anymore, due to the missing error checking.
If I can fix the PATH order, I'll do that, but I have no idea where to start
looking there.
------------------------------------------------------------------------------
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
