unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: GLIBC patches <libc-alpha@sourceware.org>
Subject: Re: [PATCH] NEWS: Mention libpthread, libdl, libutil, libanl integration
Date: Sat, 9 Oct 2021 07:09:01 +0900	[thread overview]
Message-ID: <CAAfxs755_otKkq5ms-a654gSyHO7C1_QOMK_doO9F_KMPgGYuQ@mail.gmail.com> (raw)
In-Reply-To: <871r7roomm.fsf@oldenburg.str.redhat.com>

On Wed, Jul 21, 2021 at 9:09 PM Florian Weimer via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> ---
>  NEWS | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index efc105b6b4..dd333109a5 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -9,6 +9,20 @@ Version 2.34
>
>  Major new features:
>
> +* All functionality formerly implemented in the libraries libpthread,
> +  libdl, libutil, libanl has been integrated into libc.  New
> +  applications do not link with -lpthread, -ldl, -lutil, -lanl anymore.
> +  For backwards compatibility, empty static archives libpthread.a,
> +  libdl.a, libutil.a, libanl.a are provided, so that the linker options
> +  keep working.  Applications which have been linked against glibc 2.33

Hello,

I have updated the OpenRISC port to GLIBC_2.35 as it is not upstream yet.
I noticed when building a few applications in buildroot (gdb,
sysvinit) that have
hard codings of -lutil, they now fail when compiling with the openrisc
toolchain.

I got them to compile by removing -luti.

How should we go about patching that in a way they can build with older versions
of glibc and with the openrisc toolchain on version 2.35.  Should they
detect the
glibc version?

Sysvinit issue:
  https://git.savannah.nongnu.org/cgit/sysvinit.git/tree/src/Makefile#n144

Buildroot GDB issue:
  https://github.com/buildroot/buildroot/blob/master/package/gdb/gdb-python-config#L32

-Stafford

  parent reply	other threads:[~2021-10-08 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 12:08 [PATCH] NEWS: Mention libpthread, libdl, libutil, libanl integration Florian Weimer via Libc-alpha
2021-07-29  2:19 ` Carlos O'Donell via Libc-alpha
2021-07-29  7:56 ` Alexander Monakov via Libc-alpha
2021-10-08 22:09 ` Stafford Horne via Libc-alpha [this message]
2021-10-09 12:18   ` Florian Weimer
2021-10-10  0:45     ` Stafford Horne via Libc-alpha
2021-10-10 13:34       ` 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

  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=CAAfxs755_otKkq5ms-a654gSyHO7C1_QOMK_doO9F_KMPgGYuQ@mail.gmail.com \
    --to=libc-alpha@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=shorne@gmail.com \
    /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).