Weird problems, compiling/making--->Problem SOLVED!

Curtis Haas WonderBoy5150 at
Thu Mar 21 16:16:21 PST 2002

I feel like such a fool...
In my scripts, the first one that runs (for LFS-3.1) creates the directory
structure for the new LFS partition and then copies all the files and
scripts needed to install the system to $LFS/usr/src.

The second script is what caused all my problems... it is the 'unpacker'
script. It unpacks all the files from the lfs-packages-3.1.tar &
lfs-bootscripts-3.1.tar to the $LFS/usr/src directory.
Now since I know that some of the programs have to be re-install again in
Chapter6, the script then creates the folder $LFS/usr/src/chapter6. Then the
script copies the source trees that are needed again in Chapter6 too that
chapter6 folder, and that was where I found my problem, thanks to this

The 'copying routine' in my script was using: cp -r
And not: cp -a

I've learned now that '-r' will not copy everything.

Can someone tell me if, in the *NIX world, are directory/sub-directory
structures referred to as 'archives'?
Because the man page for 'cp' says '-a' means archive. That's it.

I may be a newbie, but at least I didn't give up on this problem. It may
have taken me 20+ installs over a 2 week period, but alas, I found my
problem. I 'learned' something I guess..
I made scripts for LFS-3.2 and they are working happily along with LFS-3.1.

  ----- Original Message ----- 
  From: Curtis Haas 
  To: lfs-support at 
  Sent: Wednesday, March 13, 2002 9:57 AM
  Subject: Weird problems, compiling/making

  3 month linux newbie here... LFS for 1 of those.
  LFS version: 3.1
  Glibc version: 2.2.4
  System: Intel P200MHz MMX 128M RAM
  Using the lfs-packages-3.1.tar from the site.

  Has anyone else besides me noticed having problems when, say a program fails to compile:
  You remove the source tree for that program.
  You re-extract the files for that program.
  The "new and fresh" source tree is put in the same location as the failed one.
  You re-issue the same exact commands that you did before, yet this time the program compiles and installs without error???

  Here is what I have been playing around with.
  I have 2 directories setup.
  Each of these folders contains "cheesy scripts" that I made to make the installation process of LFS go quicker so I don't have to keep running back to the machine 50 times or so.
  With this information being said, why would what happened up above happen? I would restart the script at the program it bombed on and would work fine, and all I did was remove/re-extract the source tree.

  At first I though it was the 'Optimized' "scripts" that was causing me grief, but after re-partitioning and setting up a new file system then using 'Un-Optimized' "scripts" it's doing the same thing.
  These are the programs, in order, that are causing me grief:
  (This is only in the Chapter6 programs)

  For some reason in the back of my mind, the chroot env is "sprinkling" the Host Distribution on my system with some saved settings or something. All these scripts are doing is just one installation of a program after another, all in order in the book.
  The "scripts" are basically text files with '#!/bin/sh' header.....don't laugh, I don't know programming :-(
  I am going to try the 'Un-Optimized' scripts again, after I reinstall my distribution, something might have gotten screwed up, but that doesn't explain what I said up above.

  In this January 2002 archive, this guy seems to have had the same problems I am having, but with just gcc...

  I have screen shots of what the programs do. Sorry for not saving the original text output, but I don't think the output or the screen shots matter in my case. If any of you would like to take a look at my so called "scripts" I can attach them in a reply.

  2 more questions:
  Why does the 'echo' command not like this symbol ' (apostrophe)

  And say I have a hint, how do I post it.
  It's for gdm (Gnome display manager) without having to installing all of gnome

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the lfs-support mailing list