Install Script :)
clydew at clydew.net
Wed Jun 21 13:59:59 PDT 2000
Thank you. It's just what I needed.
On Wed, 21 Jun 2000, Richard wrote:
> > What do you do to get your script to stop when
> > an error occurs? Does this also work for something
> > simple like a copy?
> The script will stop on any error, including a copy.
> The way that is done is on the first line:
> #!/bin/bash -ex
> # -x trace output of each line
> # -e stop if anything outside  or test returns an error
> The bad news is that some packages do some
> recovery action after an error, and report the
> status of the recovery action to my script. The
> most anoying one today was binutils did not
> compile because my host system's ranlib had
> gone walkies. No errors were reported until
> after the chroot environment gets entered,
> and then very little worked because as from
> binutils was not there.
> How about a note in the book along the line of:
> if ./configure fails try cat config.log
> This told me why gcc was failing (no /usr/bin/as)
> Bad day today - I said nasty things about the red hat
> install disk until I remembered they use the old lilo and
> the boot directory is on cylinder 1200ish.
> Mail archive: http://www.pcrdallas.com/mail-archives/lfs-discuss
> IRC access: server: irc.linuxfromscratch.org port: 6667 channel: #LFS
> Unsubscribe: email lfs-discuss-request at linuxfromscratch.org and put
> "unsubscribe" (without the quotation marks) in the body of the message
> (no subject is required)
Mail archive: http://www.pcrdallas.com/mail-archives/lfs-discuss
IRC access: server: irc.linuxfromscratch.org port: 6667 channel: #LFS
Unsubscribe: email lfs-discuss-request at linuxfromscratch.org and put
"unsubscribe" (without the quotation marks) in the body of the message
(no subject is required)
More information about the lfs-dev