From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Add test for linking against most static libraries
Date: Fri, 28 Oct 2016 20:21:00 -0000 [thread overview]
Message-ID: <daa38a1a-a28f-f371-e3e8-4b4892691ad4@redhat.com> (raw)
In-Reply-To: <ad2b0c11-6a3c-160e-0c79-49fd68e58150@redhat.com>
On 10/28/2016 02:55 PM, Florian Weimer wrote:
> On 10/28/2016 07:33 PM, Joseph Myers wrote:
>> On Fri, 28 Oct 2016, Carlos O'Donell wrote:
>>
>>> I'm kinda baffled by this. We don't set it in config-sysdirs.
>>>
>>> I expect you have a local patch that hid this.
>>
>> I expect he happened to have a compiler that searched a system
>> include directory with crypt.h.
>
> This is what seems to have happened, at least according to
> elf/tst-linkall-static.o.d. It happened on all systems I tested
> this.
>
> I suspect the only way to guard against this is to parse the default
> compiler search paths from gcc -v and replace the variants of
> /usr/include found therein with a carefully prepared directory tree
> of installed headers and some linked-in kernel headers.
That's what my build private scripts do :-)
I rebuild a sysroot out of a few headers and an install of master
kernel headers to detect immediate UAPI breakage as it goes in upstream.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-10-28 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 12:57 Florian Weimer
2016-10-28 14:51 ` Carlos O'Donell
2016-10-28 17:30 ` Carlos O'Donell
2016-10-28 17:33 ` Joseph Myers
2016-10-28 17:42 ` Florian Weimer
2016-10-28 17:48 ` Joseph Myers
2016-10-28 18:30 ` Carlos O'Donell
2016-10-28 20:16 ` Carlos O'Donell
2016-10-28 20:22 ` Joseph Myers
2016-10-29 2:41 ` Carlos O'Donell
2016-10-28 18:55 ` Florian Weimer
2016-10-28 20:08 ` Joseph Myers
2016-10-28 20:27 ` Florian Weimer
2016-10-28 20:52 ` Joseph Myers
2016-10-28 20:21 ` Carlos O'Donell [this message]
2016-10-28 18:27 ` Carlos O'Donell
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=daa38a1a-a28f-f371-e3e8-4b4892691ad4@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/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).