From: Chris Houser <chouser@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] segfault during bootstrap (rc6-r9)
Date: Sun Sep 23 21:11:01 2001 [thread overview]
Message-ID: <20010923230929.A482620@plato.zk3.dec.com> (raw)
I have been having problems getting build-ix86-1.0_rc6-r9.tbz2 to
bootstrap, using portage-1.6.9. During the 'merge' portion of the glibc
emerge, I would get this output:
...
/var/tmp/portage/glibc-2.2.4-r1/image/sbin/sln
>>> Completed installing into /var/tmp/portage/glibc-2.2.4-r1/image/
Saving ld-linux,libc6 and libpthread
/bin/cp: cannot create regular file `/tmp/ld-linux.so.2': Text file busy
...and then a segfault. I tried this a couple times, getting similar or
identical results.
Finally, I decided to manually step through what the bootstrap script
does:
# USE="build" ebuild /usr/portage/sys-apps/baselayout-1.6.3/baselayout-1.6.3.ebuild merge
# USE="build" ebuild /usr/portage/sys-devel/binutils-2.11.90.0.7/binutils-2.11.90.0.7.ebuild merge
# USE="build" ebuild /usr/portage/sys-devel/gcc/gcc-2.95.3-r5.ebuild merge
# ebuild /usr/portage/sys-libs/glibc/glibc-2.2.4-r1.ebuild merge
...and this seemed to work fine. I don't know why. I finished doing
the manual bootstrap, and it seems to be working fine:
# ebuild /usr/portage/sys-devel/binutils/binutils-2.11.90.0.27.ebuild merge
# emerge sys-devel/gcc
# emerge sys-apps/texinfo
I don't know what was broken before, or why it worked, but I thought I
should at least record what I did. Hopefully if anyone else sees the
same bootstrap error I did, we'll be able to find a fix.
My machine is now happily working on 'emerge system'. Thanks to
everyone on IRC that helped me a long the way.
--Chris
next reply other threads:[~2001-09-24 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-23 21:11 Chris Houser [this message]
2001-09-23 22:13 ` [gentoo-dev] segfault during bootstrap (rc6-r9) Joe DeRosa
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=20010923230929.A482620@plato.zk3.dec.com \
--to=chouser@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.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