From: Tibor Rudas <a9101556@unet.univie.ac.at>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] building problems [continued...]
Date: Wed Aug 29 02:52:01 2001 [thread overview]
Message-ID: <01082910513300.15571@epsilon.mdy.univie.ac.at> (raw)
Hello
I'm still experiencing problems when trying to build gentoo from scratch.
To summarize the core of my problem: I want to build a little network
using gentoo. But: all machines are CD-less. So installing the
exclusive-bin version (for me) seems to be a nontrivial task.
I once succeeded (thanks to x86 on #gentoo) by using a different
linux's boot disk which provided me with NFS, chroot and working
internet connection to build gentoo from the 1.0_rc5-r4 build
image.
But since then I was not able to reproduce this success.
With the 1.0_rc5-r4 build image I end up getting the same
problems Marius Brueggemann got (bootstrap complaining,
seems to be the lvm related problem already reported to this
list).
When I extract build-ix86-1.0_rc6-r4.tbz2 I can neither
do env-update nor emerge rsync both complaining about
make.profile not being where it should.
Using build-ix86-1.0_rc6-r4.tbz2 and portage-20010827.tar.bz2
I could complete the bootstrap but emerge system first stopped
on building diffutils complaining about makeinfo missing.
After manually emerging texinfo I could resume emerge system
but it stops again with netkit-telnet:
make[1]: g++: command not found.
Is there a better way to get gentoo on a CD-less machine
(are there gentoo boot-floppies? Maybe the problem arises
from the fact that I'm chrooting from a different system)?
Or am I doing something seriously wrong?
regards
Tibor Rudas
next reply other threads:[~2001-08-29 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 2:52 Tibor Rudas [this message]
2001-08-29 8:05 ` [gentoo-dev] building problems [continued...] Chad Huneycutt
2001-08-29 10:42 ` Daniel Robbins
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=01082910513300.15571@epsilon.mdy.univie.ac.at \
--to=a9101556@unet.univie.ac.at \
--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