public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Add test for linking against most static libraries
Date: Fri, 28 Oct 2016 17:48:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1610281744490.17460@digraph.polyomino.org.uk> (raw)
In-Reply-To: <6ca11c8d-678c-c41f-1a03-c8c5ec4c7df2@redhat.com>

On Fri, 28 Oct 2016, Florian Weimer wrote:

> On 10/28/2016 07:33 PM, Joseph Myers wrote:
> 
> > > I'm going to commit the following immediate fix:
> > > 
> > > 2016-10-28  Carlos O'Donell  <carlos@redhat.com>
> > > 
> > > 	* elf/Makefile (CFALGS-tst-linkall-static): Define.
> > 
> > That's not the right fix.  The right way to address such issues is a
> > wrapper header in include/.
> 
> Is this for installed headers only?

<crypt.h> is an installed header.  We want glibc source files and tests to 
include installed headers via the same paths a normal program built with 
installed headers would, so #include <crypt.h> not #include 
<crypt/crypt.h>.  The way we achieve this is through the wrappers in 
include/, some of them trivial (e.g. cpio.h, an example of a wrapper added 
for testcase use for a similar issue), some less trivial.

> I've been using the <crypt/crypt.h> style for internal headers.

That may be reasonable if a file in one directory wants to include an 
internal header from another (though I'd think an internal header used in 
more than one directory should move to include/), but this isn't a case of 
an internal header.  It should have a wrapper that does #include 
<crypt/crypt.h>, so nothing other than the wrapper needs to use that path.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2016-10-28 17:48 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 [this message]
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
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=alpine.DEB.2.20.1610281744490.17460@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.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).