From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: Konstantin Kharlamov <Hi-Angel@yandex.ru>,
Florian Weimer <fweimer@redhat.com>,
Peng Yu via Libc-help <libc-help@sourceware.org>
Subject: Re: Directory structure of glibc and header files installed on Linux
Date: Fri, 5 Mar 2021 08:19:42 -0300 [thread overview]
Message-ID: <D4380711-4938-4E1C-8E27-F4D798089854@linaro.org> (raw)
In-Reply-To: <CABrM6wnDyMNEiL-6a4kVjkeDZfa9Tiu_a-wJwGNXCcrBwL2H4Q@mail.gmail.com>
> Il giorno 4 mar 2021, alle ore 23:38, Peng Yu <pengyu.ut@gmail.com> ha scritto:
>
>
>>
>> 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.
>
The problem here is we giving you the readily available information and steps on how you can proceed and obtain what you initially want, but you instead want *us* to spend time compiling and summarizes games instead of do yourself the research.
> I think the main problem is that there is not a doc for the directory
> structure of glibc. That should have been done.
I do not disagree, if you want to contribute I can give you access to glibc wiki and help you document this properly.
next prev parent reply other threads:[~2021-03-05 11: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
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 [this message]
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=D4380711-4938-4E1C-8E27-F4D798089854@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Hi-Angel@yandex.ru \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=pengyu.ut@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).