LFS - first apparent problem

itsjustme · 07-18-2003, 09:50 AM

OK, so I type in 'make install' as user lfs and didn't get any errors. woo hoo.

Now I'm in section 5.8.1. The book says to
mkdir ../binutils-build
well, that, of course, gives me a permission denied.

so I just drop the ../ and do 'mkdir binutils-build'. So now I have /LFS/static/binutils-build. So, I make my usual assumption and un-tar the binutils-2.13.2.tar.bz2 file into there and of course it creates yet another directory, binutils-2.13.2. Hmmm... I don't really see the need for the extra binutils-build directory. Now I am in /LFS/static/binutils-build/binutils-2.13.2.

Of course, the binutils-build directory is probably supposed to be in the /LFS directory, not the /LFS/static directory.

I should have chosen the title:
'Fun with my LFS' rather than '...first apparent problem'

Edit: Hey I just saw the other 2 replies from fancypiper and azmeen... thanks.

Azmeen · 07-18-2003, 10:03 AM

Assuming that /LFS is mounted from some partition on your hard disk. You should use an entry like:

Code:

/dev/hda13       /lfs         ext2        defaults         1   1

in your /etc/fstab.

After that, as root, chown /lfs (whatever you've chosen) to the user lfs so he wouldn't have permission issues and whatnot.

Furthermore, it's better to untar the apps outside of $LFS/static...

I came out with the following partitioning scheme:

Code:

-- /
   |-/static
   |-/packages
       |- gcc/
       |- glibc/
       |- bash/
       \- whatever/

Hope this helps!

itsjustme · 07-18-2003, 10:21 AM

yeah, I have

/dev/hda11 /LFS ext3 ......

And followed along in the book and did the chown thing, but I think that was just for the static directory. It never said anything about chown for /LFS. (or I missed it.)

echo $LFS is /LFS (I had this setup from when I installed slackware, before I saw that the book uses /mnt/lfs.)

I am using the files provided on the LFS CD I purchased, so I should have all the correct packages for this. I copied the packages into /LFS/packages, but I was moving them into /LFS/static, just because that seemed to be the thing to do.

Where exactly is your binutils-build directory??
Mine is in /LFS/static. Should that be back up in /LFS? Or, down in /LFS/packages?

Thanks for the input...

Azmeen · 07-18-2003, 10:34 AM

Mine would be something like: /mnt/lfs/packages/binutils-build.

Actually anywhere other than om (whatever path)/binutils/ would be a good idea.

I'd also stay out of building in $LFS/static as well... Why? Because I'd like to see what directories are being created... I just love watching them grow

If you still want to build somewhere in $LFS/static... then create another directory... something like $LFS/static/workplace where you do all your compiling. Then when you're finished you can just rm -rf $LFS/static/workplace instead of hunting down the directories you've created on the way to building your LFS system and separating them from the real core dir tree you've built.

itsjustme · 07-18-2003, 10:48 AM

Hmmm... OK, I think I might now be seeing the forest in those trees.

I'll un-tar the packages to, say, /LFS/packages/temp, and then, when running the configure and make commands, since they all seem to have the --prefix=$LFS/static option, the stuff that needs to be in /static will go there and everything else will be outside of that.

I'm gonna start over now, before I go any further, and use that scheme.

thanks...

Azmeen · 07-18-2003, 10:52 AM

Quote:

Originally posted by itsjustme
I'll un-tar the packages to, say, /LFS/packages/temp, and then, when running the configure and make commands, since they all seem to have the --prefix=$LFS/static option, the stuff that needs to be in /static will go there and everything else will be outside of that.

Precisely! I have a feeling that you will do well in this experiment... Good luck!

Don't forget to share your success story!

Azmeen · 07-22-2003, 09:31 AM

Hey itsjustme,

Any updates on how your installation went?

While setting up my LFS system, I came up with a simple and downright dirty packaging system, something similar to Slack's installpkg.

The packages I have made are as follows:

Code:

misclibs/:
total 3080
drwxr-xr-x    2 root     root         4096 Jul 18 20:31 ./
drwxr-xr-x    6 root     root         4096 Jul 18 20:09 ../
-rw-r--r--    1 root     root      1637878 Jul 18 20:04 openssl-0.9.7b-i686.tbz
-rw-r--r--    1 root     root       183338 Jul 18 20:16 pcre-4.3-i686.tbz
-rw-r--r--    1 root     root       105815 Jul 18 20:22 popt-1.7-i686.tbz
-rw-r--r--    1 root     root      1198134 Jul 18 20:30 slang-1.4.9-i686.tbz

netapps/:
total 784
drwxr-xr-x    2 root     root         4096 Jul 18 18:23 ./
drwxr-xr-x    6 root     root         4096 Jul 18 20:09 ../
-rw-r--r--    1 root     root       788257 Jul 18 18:23 lynx-2.8.4-i686.tbz

netlibs/:
total 1004
drwxr-xr-x    2 root     root         4096 Jul 18 18:23 ./
drwxr-xr-x    6 root     root         4096 Jul 18 20:09 ../
-rw-r--r--    1 root     root      1014407 Jul 18 18:23 curl-7.10.4-i686.tbz

shells/:
total 1180
drwxr-xr-x    2 root     root         4096 Jul 18 18:21 ./
drwxr-xr-x    6 root     root         4096 Jul 18 20:09 ../
-rw-r--r--    1 root     root       192141 Jul 18 18:02 tcsh-6.12.00-i686.tbz
-rw-r--r--    1 root     root       997469 Jul 18 18:18 zsh-4.1.1-i686.tbz

The package name follows a convention of name-version-architecture.tbz. Basically it's a tar.bz file containing precompiled binaries.

If you're interested in becoming a fellow tester of this packaging system do give me a shoutout.

Cheers!

itsjustme · 07-22-2003, 12:58 PM

Well, I've been busy doing other stuff. (goofing off

)

I got through Ch. 5 and plan to start Ch. 6 today. So, I reckon I'm not ready to be any sort of tester.

I'll keep that in mind though.

regards....