From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) by sourceware.org (Postfix) with ESMTPS id E20FE3858022 for ; Fri, 5 Mar 2021 02:38:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E20FE3858022 Received: by mail-io1-xd33.google.com with SMTP id z13so408490iox.8 for ; Thu, 04 Mar 2021 18:38:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=yWNVp7fNiS3q9evJx74ECwmgGHz/0wYIrkcJV/fxTy4=; b=GHPfo0r94TmPn9UmkG5fLOYfABdbVXbPNgrcSKmrvnkSi5wvkMQnqXWN1Id9CBvoRD g+jmY+X3yhEXqWKlOpYHdhqnGmlyKuYtZHCZbHeAypkTDZ4cGqAmIVWSKlhpdNsAYrcv ckv8VTv1lMNSQKgSxsaYTSRCSwG/Gg0I9dAGtpRd268Uttmo87/4/L62DnwGx+4AAWug lAmXcnXsJ9OBB8pBqYbQdgt9GO5QT25+y3VKtP+Ob+VepOG2t9g7QqL+iNpC8IM+hIen QC5sBeY5/6BYbqT8jJXX6tFnBmvLUIRbknHSEM2EoNqzfSZZjznCr1KbQx+BYs99Weih /22A== X-Gm-Message-State: AOAM5310FZjKX9xQCYPhbiYATXYC8UZSqRshmlmC++BChDoL6TKdBFNC LiLrlUcfM5zS+Sph/cLdNKPpuQWr3yCSNXkyQgo= X-Google-Smtp-Source: ABdhPJwQnjP8XL7kI5036tYKL4MzHvTGbo+0geqMkVRhFrqDPKkp6rj8mFyeQl9vo1g1GKfPLcT3duFDXoM+Z09PKi0= X-Received: by 2002:a02:77d0:: with SMTP id g199mr7247869jac.118.1614911892177; Thu, 04 Mar 2021 18:38:12 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6602:349:0:0:0:0 with HTTP; Thu, 4 Mar 2021 18:38:11 -0800 (PST) In-Reply-To: <358ee421ee4a9bd37a62ef21aea0773efffa8024.camel@yandex.ru> References: <87wnunnq3q.fsf@oldenburg.str.redhat.com> <358ee421ee4a9bd37a62ef21aea0773efffa8024.camel@yandex.ru> From: Peng Yu Date: Thu, 4 Mar 2021 20:38:11 -0600 Message-ID: Subject: Re: Directory structure of glibc and header files installed on Linux To: Konstantin Kharlamov Cc: Adhemerval Zanella , Florian Weimer , Peng Yu via Libc-help Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2021 02:38:14 -0000 > 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 (whi= ch > 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 =E2=80=A6` and then `dpkg-buildp= ackage =E2=80=A6`, > see: https://askubuntu.com/a/246721/266507 (unless I misunderstand > something, the `dpkg-buildpackage` will probably run a script that in tur= n > 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. --=20 Regards, Peng