public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] extras: New test/build infrastructure
Date: Fri, 25 Nov 2016 18:44:00 -0000	[thread overview]
Message-ID: <CAKCAbMh8pHSzZ=Sz-YJVD1cmZwZpzDncD4_RXDWsiGUX3tp_7g@mail.gmail.com> (raw)
In-Reply-To: <662a011c-f3f8-1c43-9b98-542d499b3dca@redhat.com>

On Fri, Nov 25, 2016 at 12:45 PM, Florian Weimer <fweimer@redhat.com> wrote:
> On 11/25/2016 05:14 PM, Zack Weinberg wrote:
>>
>> Can I ask why the new directory is called "extras"?  That makes it sound
>> like a home for extra features that we want to provide but not in the
>> core C library.  Something more obviously internal-use and
>> build/test-related would be better, I think.
>
> I plan to use bits of it for fixing localedef bugs and contributing Fedora
> changes upstream.  Those bits would then end up in installed binaries.
>
> The immediate need is for testing only and generic test support code
> (container setup, a fake DNS server implementation, and so on).

So maybe "support/" or "build-test-support/"?

>>> +libextras-static-only-routines := $(libextras-routines)
>>> +# Only build one variant of the library.
>>> +libextras-inhibit-o := .os
>>> +ifeq ($(build-shared),yes)
>>> +libextras-inhibit-o += .o
>>> +endif
>>
>> This doesn't look right if the goal is to build only the .a version of
>> the library.
>
> Could you clarify what worries you?  If there's just one variant, it has to
> be PIC, unless it's a static-only build.

I may well not understand what this combination of
-static-only-routines and -inhibit-o does, but what it *looks* like it
does is disable generation of .os (PIC) object files unconditionally,
and if shared libraries are enabled, it also disables .o (static)
object files. I would expect this to wind up either not working at
all, or producing only a *shared* library, or possibly only a
profiling library!

Also I don't know why this code would need to be PIC.

>> This library is _not_ part of the implementation and should not be using
>> __ names.  And I'm not sure it ought to be using features.h either.
>
> <features.h> is needed for __BEGIN_DECLS.  Including <sys/cdefs.h> would be
> even more extreme, I think.

Honestly I think sys/cdefs.h has a better claim to be a public
interface than features.h, since it exists on *BSD (and does in fact
define compatible __BEGIN_DECLS/__END_DECLS there too: see
https://github.com/freebsd/freebsd/blob/master/sys/sys/cdefs.h)

zw

  reply	other threads:[~2016-11-25 18:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 15:59 Florian Weimer
2016-11-25 16:14 ` Zack Weinberg
2016-11-25 17:11   ` Andreas Schwab
2016-11-25 17:46     ` Florian Weimer
2016-11-25 17:45   ` Florian Weimer
2016-11-25 18:44     ` Zack Weinberg [this message]
2016-11-25 18:49       ` Florian Weimer
2016-11-25 16:16 ` Florian Weimer
2016-11-25 17:29 ` Joseph Myers
2016-11-25 17:48   ` Florian Weimer
2016-11-25 18:24     ` Joseph Myers
2016-11-25 19:26       ` Florian Weimer

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='CAKCAbMh8pHSzZ=Sz-YJVD1cmZwZpzDncD4_RXDWsiGUX3tp_7g@mail.gmail.com' \
    --to=zackw@panix.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).