From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: gcc: link scan order of /usr/lib and /usr/lib/w32api
Date: Fri, 26 Feb 2016 07:49:00 -0000 [thread overview]
Message-ID: <56D0037C.5050302@cygwin.com> (raw)
In-Reply-To: <56CF8A6C.3070706@users.sourceforge.net>
On 2016-02-25 17:12, JonY wrote:
> On 2/26/2016 01:44, Yaakov Selkowitz wrote:
>> JonY,
>>
>> It has been brought to my attention that /usr/lib/w32api is now taking
>> precedence over /usr/lib, which is a result of this commit:
>>
>> https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=227962
>> https://github.com/gcc-mirror/gcc/commit/c1b7008c95f97dd7c11997e7be7be7b58d113db0
>>
>>
>> This is incorrect, and results in the unfortunately-named w32api
>> libuuid.a being found instead of the completely unrelated *NIX libuuid
>> (which is what *NIX software expects to find).
>>
>> Linking from /usr/lib/w32api is handled in binutils, and this is the fix
>> that my cygwin cross-toolchains are using to support sysroots:
>>
>> https://github.com/cygwinports/cygwin32-binutils/blob/master/01-w32api-sysroot.patch
>>
>>
>> Please revert r227962.
>
> Ok, I'll do a new release soon.
Here's a patch:
https://github.com/cygwinports/gcc/blob/master/0027-link-w32api.patch
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-02-26 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 17:44 Yaakov Selkowitz
2016-02-25 23:12 ` JonY
2016-02-26 7:49 ` Yaakov Selkowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56D0037C.5050302@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).