On Fri, Oct 11, 2019 at 03:02:18PM -0500, Trent wrote:
>
> You are the man, Ken.
>
> Your explanations helped a lot, and taught me something.
>
> What I had been doing is putting what I want doing in a text file, then
> copying the whole section, then pasting it into the command line all in one
> go.
>
> It turns out I had a typo in there, and everything was going by so fast I
> did not see it, nor even see the typo I had because some of it was
> successful, and part not. The successful part had pushed up the unsuccessful
> part so I did not see it had gone bad.
>
>
> Thank you so much!
>
Glad you found the problem. We always recommend doing your first
LFS manually, and yes that takes for ever and sometimes people get
confused by warning messages.
But after that there are the joys of scripting (pasting the commands
counts as scripting), and more specifically the joys of understanding
where, and how, your own scripts can fail. Good luck with the rest
of the build. Perhaps adding '&&' in a section, then checking the
status in $? at the end might help. Or, for tests, run them and
look at failures before trying to install (some test failures are
inevitable and not necessarily a reason to question the build).
Me, I'm still repeating my own past mistakes (currently, a typo in
building rust manually for a new prefix - builds fine, then fails in
the install).
ĸen
--
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
- Unseen Academicals
--
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
