From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [RFC] elf: Implement filtering of symbols historically defined in libpthread
Date: Tue, 4 May 2021 06:28:33 -0700 [thread overview]
Message-ID: <CAMe9rOp=nBz_iTVZcbSR1c6qc_p98CN7-PBwNabuduD9nFAcJw@mail.gmail.com> (raw)
In-Reply-To: <87fsz2k5fm.fsf@oldenburg.str.redhat.com>
On Tue, May 4, 2021 at 6:13 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu:
>
> > Why re-linking is needed for the binary executable test?
>
> I don't want us to bundle the sources of an old glibc version, just to
> comply with the LGPL requirements for one single test (or talk to legal
> folks to figure out if this is required).
We can include both the source and the binary. We just use the pre-built
binary built against the older glibc. I don't see an issue here.
--
H.J.
next prev parent reply other threads:[~2021-05-04 13:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 18:01 [RFC] elf: Implement filtering of symbols historically defined in libpthread Florian Weimer via Libc-alpha
2021-05-04 6:55 ` Florian Weimer via Libc-alpha
2021-05-04 11:47 ` H.J. Lu via Libc-alpha
2021-05-04 12:04 ` Florian Weimer via Libc-alpha
2021-05-04 12:24 ` H.J. Lu via Libc-alpha
2021-05-04 12:27 ` Florian Weimer via Libc-alpha
2021-05-04 12:30 ` H.J. Lu via Libc-alpha
2021-05-04 12:33 ` Florian Weimer via Libc-alpha
2021-05-04 12:36 ` H.J. Lu via Libc-alpha
2021-05-04 12:43 ` Florian Weimer via Libc-alpha
2021-05-04 13:06 ` H.J. Lu via Libc-alpha
2021-05-04 13:13 ` Florian Weimer via Libc-alpha
2021-05-04 13:28 ` H.J. Lu via Libc-alpha [this message]
2021-05-04 12:59 ` Adhemerval Zanella via Libc-alpha
2021-05-04 21:08 ` Carlos O'Donell via Libc-alpha
2021-05-04 13:08 ` Andreas Schwab
2021-05-04 16:52 ` Florian Weimer via Libc-alpha
2021-05-04 21:28 ` Carlos O'Donell via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMe9rOp=nBz_iTVZcbSR1c6qc_p98CN7-PBwNabuduD9nFAcJw@mail.gmail.com' \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=schwab@linux-m68k.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).