From: Andreas Jaeger <aj@suse.de>
To: Neale.Ferguson@softwareAG-usa.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-s390x progress
Date: 07 Mar 2001 15:24:14 +0100 [thread overview]
Message-ID: <hobsrd3be9.fsf@gee.suse.de> (raw)
In-Reply-To: <20010307141337Z131097-407+2208@vger.kernel.org>
In-Reply-To: <20010307141337Z131097-407+2208@vger.kernel.org> (Neale.Ferguson@softwareAG-usa.com's message of "Wed, 7 Mar 2001 09:04:31 +0200")
Neale.Ferguson@softwareAG-usa.com writes:
> I've been using the "Linux from Scratch" (LFS) document as a guide for building
> a basic Linux system. The only things I've done outside the instructions
> include:
>
> 1. Built 32 bit version of binutils, gcc, glibc for s390x
> 2. Built kernel
> 3. Created /root64 and populated it with /usr /bin etc.
> 4. Built 64-bit libncurses
>
> I've now built statically linked 64-bit versions of:
> 1. bash
> 2. bzip2
> 3. diffutils
> 4. fileutils
>
> These are all installed in the /root64 tree.
>
> According to the LFS instructions I should now build grep, gzip, make,
> sed, shellutils, tar, and textutils, before going onto the next phase.
> However, I cannot find grep, sed, or tar srpms on the SuSE CDs.
this is getting off-topic but from SuSE 7.1:
$ rpm -q -f `which grep`
base-2001.1.15-0
You'll find in the base rpm also the sources of sed and tar.
Hope this helps - and have fun with Linux on your small;-) machine,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
prev parent reply other threads:[~2001-03-07 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 7:04 2.4.0-s390x progress Neale.Ferguson
2001-03-07 14:24 ` Andreas Jaeger [this message]
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=hobsrd3be9.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=Neale.Ferguson@softwareAG-usa.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.