On Sun, Jan 10, 2016 at 05:56:33PM +0000, Read, James C wrote:
> Hi,
> 
> 
> below is a very simple script, the intention of which is to do all of chapter 
> 5 in one sweep and avoid having to type all the commands in (error prone and 
> nauseating after the umpteenth time round).
> 

I've no idea if it is related to your warnings from texinfo's
configure, but I think there is a basic problem with your script.
After each package has finished, you have a line, e.g.

> echo '***!!!*** Binutils Pass 1 finished'

For each package, a quick look suggests you linked every command
with '&&', so that echo will only happen if the binutils pass 1
commands did all complete with error.  And similarly for every other
package.

But what happens if a package DOES fail somewhere ?  You skip over
the echo, but the *next* command (start of next package) is not
dependent on a successful return code.  So, if a package fails for
some reason, it probably left its source around, and then the next
package started.

I will guess that you have one or more extracted packages lying
around because it/they failed to complete.

And whatever error messages came from that/those packages have
long-since scrolled off the screen.  In fact, your added echo
messages with the '***!!!*** ' prefixes will scroll off the screen
quickly - knowing where the build has reached is useful (I do it
myself), but mixing your messages with the output from configure,
make, etc is not going to be especially informative - unless you are
sitting in front of the screen speed-reading.

iActually, I can also see a missing '&&' after an 'esac'.  I'm always
wary of adding '&&' after 'fi' or 'esac', it can be easy to break
things, (syntax errors), but nevertheless I think you need to check
for an error at that point.  And also after 'done' (although none of
those constructs in the book are likely to fail, they give the same
opportunity for the next command to run unconditionally after a
previous failure).

As people have said : do not try to script it until you have
successfully built and booted LFS.  And pay attention to what shows
up at the end of a command, and if uncertain 'echo $?'.  Then for
your next builds go wild if you want to.

ĸen
-- 
This email was written using 100% recycled letters.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to