Directory structure of glibc and header files installed on Linux

[Peng Yu]

> FWIW, whenever I need to build a project I don't know how to build yet, I
> often look at how my distro does that. If it's something complicated (which
> seems to be the case with glibc), I use the configuration provided by my
> distro.
>
> You said you're using Ubuntu. I found that Ubuntu provides a way to build a
> package from source by using `apt source …` and then `dpkg-buildpackage …`,
> see: https://askubuntu.com/a/246721/266507 (unless I misunderstand
> something, the `dpkg-buildpackage` will probably run a script that in turn
> runs `configure`, `make`, etc, and at the end would package a deb file).
>
> Side note: apt will download sources for the version of glibc that is
> installed in your Ubuntu. Ubuntu is mostly known as a distro providing
> ancient software (except perhaps browsers), so the glibc you'll get will
> likely be very old. It may or may not be what you want.

Debian packages are old. It just creates a .deb file. It introduces
another sets of tools which I don't know the details. If there are any
problems, I will not know how to fix along the way.

It is still too complicated. The original question is to understand
the directory structure. Then, the question became, compile glibc,
installing system from scratch ... I don't think approaches like this
makes sense. it makes a simple thing more complicated than necessary.

I think the main problem is that there is not a doc for the directory
structure of glibc. That should have been done.

-- 
Regards,
Peng