Visit Jeremy's Blog.
Go Back > Blogs > threekgtvr4
User Name


Rate this Entry

LFS by a newbie, part deux progress report...

Posted 01-07-2007 at 05:05 AM by threekgtvr4

Well, since my last post on building <a href="">LFS 6.2</a>, I've completed chapter 5 with no further problems and moved on to chapter 6. I should have finished with the LFS build in 8 days, but it's taking me some extra time because I am using the <a href="">More Control and Package Management Using Package Users</a> hint. The reason it's taking me longer is because the More Control hint was written for LFS 6.0, and some things have changed since that release, nothing mega huge, but enough to slow me down a little bit. Not to mention that I've been modifying the more_control_helpers that come with the package management scheme.

As with chapter 5, I made my own shell scripts for steps 6.2.2-6.6. I only really needed the one for setting up the chroot environment (steps 6.2.2-6.5) but I decided to make the others just in case I decide to build LFS again, which I plan to do. I will build LFS again as soon as I have this current build done and running because I want to take all my new found knowledge and see how smoothly and quickly I can actually build LFS when I don't have anything slowing me down.

Just today it's taken me almost 10 hours to get GCC-4.0.3 compiled and installed. This is because I decided today to go ahead and modify the "build" script. I took it and split it into 4 seperate "install" scripts. One for configure, one for make, one for the test and one for the installation. Each of the scripts make their own .err and .log file and stores them in the "package user's" home directory along with a timestamp that shows how long each portion of the package installation took.

I also altered the "install_package" and "add_package_user". With the "install_package" script, I kept the original functionality and added the ability for you to optionally pass the path to the LFS sources and the name of the package (i.e. glibc, gcc, binutils). With my changes what happens is that "add_package_user" can now automatically populate the "package user's" home with the source tarball and patches by giving "install_package" the optional arguments. With the original scripts, the items from /etc/pkgusr/skel-package would be chowned to the package user. I have it set up the same way except now it automatically chowns the 4 build scripts and the source tarball and any associated patches.

Since I'm extremely new to shell scripting, it was difficult to decipher a lot of it. But I've fully tested it all and have them running successfully. I just need to go through all the ones I've altered and make the appropriate changes to the comments to reflect all of changes and give the proper credit.

That's all I have for today, but will be back eventually, probably after I'm done with the build, as all the other packages have a short install time.
Posted in Uncategorized
Views 1045 Comments 0
« Prev     Main     Next »


All times are GMT -5. The time now is 12:47 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration