public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Martin Liška" <mliska@suse.cz>, dwz@sourceware.org
Subject: Re: ☺ Buildbot (GNU Toolchain): dwz - build successful (master)
Date: Wed, 29 Jun 2022 09:17:04 +0200	[thread overview]
Message-ID: <87tu843pn3.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <Yrt2EEXUJful31ix@wildebeest.org> (Mark Wielaard's message of "Tue, 28 Jun 2022 23:43:44 +0200")

* Mark Wielaard:

> I am not sure why the abi-note would pull in all these sockeraddr
> declarations.

It's because low-level system headers in glibc depend on thread
descriptor layout, and the thread descriptor contains the
thread-specific copy of _res, which in turn contains socket addresses.

I don't know what has changed here, maybe we have more headers that
include <descr.h> (with the struct pthread/thread descriptor
definition).  The _res thing has been in place for about twenty years,
so that's not it.

Thanks,
Florian


  reply	other threads:[~2022-06-29  7:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25 21:56 builder
2022-06-25 22:17 ` Mark Wielaard
2022-06-27  7:25   ` Martin Liška
2022-06-28 21:43     ` Mark Wielaard
2022-06-29  7:17       ` Florian Weimer [this message]
2022-06-30 14:23       ` Martin Liška
2022-06-30 20:05         ` Mark Wielaard
2022-07-01  6:42           ` Martin Liška
2022-07-01  7:43             ` Mark Wielaard
2022-07-01  7:53               ` Martin Liška
  -- strict thread matches above, loose matches on Subject: below --
2022-11-03 22:18 builder
2022-07-11  8:44 builder
2022-07-11  8:44 builder
2022-07-07 15:29 builder
2022-07-07 13:12 builder
2022-07-07 13:10 builder
2022-07-07 12:46 builder
2022-07-07 12:46 builder
2022-07-07 12:39 builder
2022-07-07 12:38 builder
2022-07-07 12:32 builder
2022-07-07 12:31 builder
2022-07-01  7:56 builder
2022-06-30 12:50 builder
2022-06-30 12:55 ` Mark Wielaard
2022-06-25 21:55 builder

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=87tu843pn3.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dwz@sourceware.org \
    --cc=mark@klomp.org \
    --cc=mliska@suse.cz \
    /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).