public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Peng Yu <pengyu.ut@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Peng Yu via Libc-help <libc-help@sourceware.org>
Subject: Re: Directory structure of glibc and header files installed on Linux
Date: Thu, 4 Mar 2021 08:19:57 -0600	[thread overview]
Message-ID: <CABrM6wmkUu4HcvJ-WneZVFyBcOFpkavSjxFur=zVnpercyuigg@mail.gmail.com> (raw)
In-Reply-To: <87wnunnq3q.fsf@oldenburg.str.redhat.com>

I can see what files are in the ubuntu package libc6-dev. But that
does not help with where they come from and what the structure of the
glibc is. An explanation of the source tree would be helpful.

On 3/4/21, Florian Weimer <fweimer@redhat.com> wrote:
> * Peng Yu via Libc-help:
>
>> I'd like to know the complete list header files installed on Linux.
>
> The easiest way is to run build-many-glibcs.py and look at the install
> trees.  The answer varies from architecture to architecture.
>
> Thanks,
> Florian
>
>


-- 
Regards,
Peng

  reply	other threads:[~2021-03-04 14:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  2:37 Peng Yu
2021-03-04 10:57 ` Florian Weimer
2021-03-04 14:19   ` Peng Yu [this message]
2021-03-04 14:41     ` Adhemerval Zanella
2021-03-04 16:56       ` Peng Yu
2021-03-04 19:58         ` Adhemerval Zanella
2021-03-04 22:37           ` Peng Yu
2021-03-04 23:01             ` Konstantin Kharlamov
2021-03-05  2:38               ` Peng Yu
2021-03-05 11:19                 ` Adhemerval Zanella
2021-03-05  0:07             ` Adhemerval Zanella
2021-03-05  2:30               ` Peng Yu

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='CABrM6wmkUu4HcvJ-WneZVFyBcOFpkavSjxFur=zVnpercyuigg@mail.gmail.com' \
    --to=pengyu.ut@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-help@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).