gawk not being found
whstrain at mindless.remove.com
Fri Sep 28 14:57:39 PDT 2001
Yes I did originally have problems with the kernel headers. So I had to
My question is, do I need to delete and re-unpack all the packages that I
compiled while I was in the "missing kernel header" situation or can I just
recompile them as they stand unpacked.
I don't understand what happened when we deleted ncurses and unpacked it
again. I don't understand the "decision" the computer made and why it
changed stuff in the unpacked directory. Maybe I don't truly understand what
the commands in the script do.
I'm not sure if I would recognize if I was having problems with a package
unless it was obvious as this is my first LFS system.
"Gerard Beekmans" <gerard at linuxfromscratch.org> wrote in message
news:20010927224353.C1185 at gwaihir.linuxfromscratch.org...
> On Thu, Sep 27, 2001 at 06:13:12PM -0400, Howell Strain wrote:
> > I deleted the unpacked ncurses directory and unpacked it again. When I
> > re-ran it I did not get any error messages. What's the story? It made a
> > different "best" decision?
> > When I comiled Linux Kernel in Chp5 I didn't notice some errors. I made
> > all the way to ncurses in Chp6 before I noticed errors. At that point I
> > worked out my problem with Linux Kernel in Chp5 and re-ran all the steps
> > back up to ncurses where I had problems again?
> > When I re-ran all the steps back up to ncurses I did not delete the
> > trees and unpack again.
> > Do I need to delete and unpack all the source trees for Chp6 and start
> > over at the beginning of the chapter?
> I don't think that will be necessary. What exactly was wrong with the
> kernel headers? It's not that their contents will be different. So if a
> package didn't complain about the kernel headers then there's no reason to
> redo such package, unless you face a very weird extreme situation. Of
> course if it makes you feel better, by all means redo whatever you want to
> do. But I'd just continue and only recompile a package if you experience
> problems with it.
> Gerard Beekmans
> -*- If Linux doesn't have the solution, you have the wrong problem -*-
> Unsubscribe: send email to listar at linuxfromscratch.org
> and put 'unsubscribe lfs-support' in the subject header of the message
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message
More information about the lfs-support