From: Florian Weimer <fweimer@redhat.com>
To: Kenny Bian via Libc-help <libc-help@sourceware.org>
Subject: Re: Build libc6-2.28 from source: ld-2.28.so cause errors when installing deb package
Date: Thu, 01 Jul 2021 08:42:45 +0200 [thread overview]
Message-ID: <87wnqah6vu.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAC9s0NaM9mn5G0jF6vXaKz=QJtapxKqRtHbZ+ZLq7h2U7=r5Sg@mail.gmail.com> (Kenny Bian via Libc-help's message of "Wed, 30 Jun 2021 23:01:22 -0700")
* Kenny Bian via Libc-help:
> We try to build libc6-2.28 from source code. Our board runs Ubuntu
> 18.04 in armhf architecture. We downloaded the source code from
> https://launchpad.net/ubuntu/+source/glibc/2.28-0ubuntu1.
> Here is what we did to create the deb package:
> 1. We build it by using these bash commands:
> /usr/bin/dpkg-source -x glibc_2.28-0ubuntu1.dsc libc6-2.28
> pushd libc6-2.28/
> mkdir build
> pushd build/
> ../configure \
> --host=arm-linux-gnueabihf \
> --prefix=/tmp/armhf/libc6/usr \
> --enable-obsolete-nsl
> make
> make install
make install without a temporary DESTDIR is not supported.
Unfortunately the instructions do not make this clear.
The issue is that make uses separate commands for installing files, and
half-way through the update, the system is in an inconsistent state and
further commands fail, and the installation is not able to complete as a
result.
Using a temporary directory with DESTDIR and then rsync avoids the issue
(cp truncates the destination file, causing other issues).
Thanks,
Florian
next prev parent reply other threads:[~2021-07-01 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 6:01 Kenny Bian
2021-07-01 6:42 ` Florian Weimer [this message]
2021-07-01 15:52 ` Mike Frysinger
2021-07-01 21:02 ` Florian Weimer
2021-07-02 7:52 ` Kenny Bian
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=87wnqah6vu.fsf@oldenburg.str.redhat.com \
--to=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).