From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-74208-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 68816 invoked by alias); 28 Oct 2016 20:21:00 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 68792 invoked by uid 89); 28 Oct 2016 20:20:59 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy=sysroot
X-HELO: mail-qk0-f174.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:subject:to:references:cc:from:organization
         :message-id:date:user-agent:mime-version:in-reply-to
         :content-transfer-encoding;
        bh=g4142V8K+Cv+T169xzcO1lyD/y3Ax+k0UpgkW+eLZFc=;
        b=gKjTEZEkqCUdw7p6qFpjElA6a+FRE3zc5JrmVyr/we2lXwSguBgNnXUkpBuMpHzune
         SM1sACJgZprozu8rwJopW6WrFPf+F3PaePRwHeKTzMDmgCvHpGDpO3NTZG9na7pbI5Vs
         m869dr8qAWjxHIItSO4UqUtTRKT/po98jbaOeV6WBHqPca6FaYD7TtmiKnvALz3hB8WW
         qy22ZzHvb8+XGDInC4FggB1MtbMJwAiaTmYLZRlTIE/aYDGBzn43F7TBXizLX9ixHotZ
         osMJBPsD7nS5BG6kDKmdU8Iv4PQ2CISi1M2lTUzTTnG2fdRpKgjeCQhzvQKdRHniBqFG
         klJA==
X-Gm-Message-State: ABUngvd2sh7Mvk/NYp/5uzB2o5v41XB7XX5ZFuNI+pIJBCcHuEWcKbjZIdLBgEW2ySBGmYOC
X-Received: by 10.55.161.196 with SMTP id k187mr12653862qke.149.1477686057127;
        Fri, 28 Oct 2016 13:20:57 -0700 (PDT)
Subject: Re: [PATCH] Add test for linking against most static libraries
To: Florian Weimer <fweimer@redhat.com>,
 Joseph Myers <joseph@codesourcery.com>
References: <20161028125742.928D7439942E0@oldenburg.str.redhat.com>
 <8b17140d-bbab-95c1-7458-7214f0e474ad@redhat.com>
 <9c9a0748-7101-a6a0-297e-106886589d81@redhat.com>
 <alpine.DEB.2.20.1610281732090.17460@digraph.polyomino.org.uk>
 <ad2b0c11-6a3c-160e-0c79-49fd68e58150@redhat.com>
Cc: libc-alpha@sourceware.org
From: Carlos O'Donell <carlos@redhat.com>
Message-ID: <daa38a1a-a28f-f371-e3e8-4b4892691ad4@redhat.com>
Date: Fri, 28 Oct 2016 20:21:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <ad2b0c11-6a3c-160e-0c79-49fd68e58150@redhat.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-SW-Source: 2016-10/txt/msg00568.txt.bz2

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.