Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Linux From Scratch
User Name
Linux From Scratch This Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.


  Search this Thread
Old 07-22-2011, 03:24 AM   #16
LQ Veteran
Registered: Sep 2003
Posts: 10,532
Blog Entries: 7

Rep: Reputation: 2389Reputation: 2389Reputation: 2389Reputation: 2389Reputation: 2389Reputation: 2389Reputation: 2389Reputation: 2389Reputation: 2389Reputation: 2389Reputation: 2389

Originally Posted by sudeepkulkarni View Post
Here is what I do while installing any package:

1. Unpack the package archive in the host OS itself.
2. Change its permissions
3. cp -rv /path/to/<pkg-name> $LFS/tools
4. mkdir -v $LFS/tools/<pkg-build>
5. cd <pkg-build>
6. $LFS/tools/<pkg-name>/configure...........
7. make
8. make install

IS there something wrong with this scheme? Do I have to create the sources directory?
That is not correct and definitely not what is in the book (3.1 and 5.3 are there for a reason).

You need to follow the book to the letter, especially when you are new at this! Not doing so will get you into trouble and will also make it harder, if not impossible, for us to help you.
Old 04-25-2012, 05:35 AM   #17
LQ Newbie
Registered: Apr 2012
Posts: 1

Rep: Reputation: Disabled
Just posting this in case someone with the same issue finds this thread.
I'll skip the why's and just go to the facts.
I started an lfs with two partitions sdb1 100M, sdb2 10G. I mounted sdb1 as /mnt/lfs and sdb2 as /mnt/lfs/usr.
Because sdb1 was only 100M, I put tools in /mnt/lfs/usr/tools and adjusted the original symlink from
ln -sv $LFS/tools / to

ln -sv $LFS/usr/tools /

so the building of the tools worked fine. The problem is, and I only realised this after restarting, when I used the chroot line in LFS 6.4

chroot "$LFS" /tools/bin/env -i.

this then looks for /tools/bin/env at the new root, ie /mnt/lfs/tools/bin/env, which didn't exist because it was at /mnt/lfs/usr/tools/bin/env. I could have just added a new symlink, eg ln -sv $LFS/usr/tools $LFS/ but too late now.

Anyway, hope this helps because although RTFM should be every LFS attemptees mantra, it doesn't always help.

Old 04-25-2012, 07:44 AM   #18
Registered: May 2007
Distribution: LFS
Posts: 584

Rep: Reputation: 171Reputation: 171
Originally Posted by chog

Anyway, hope this helps because although RTFM should be every LFS attemptees mantra, it doesn't always help.
Hello chog,

I guess your comments may help someone. But you probably will agree that the book doesn't say to put the tools directory where you did. RTFM usually never helps much when we choose to deviate from the manual.


chroot, lfs

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Chrooting into a Linux environment LXer Syndicated Linux News 0 06-29-2008 09:00 PM
no kernel module build environment" Error message during RPM install gotmonkey Linux - Hardware 7 12-07-2007 02:08 AM
Gentoo Install 'FATAL: kernel too old' when chrooting into environment HayGuyyys Linux - General 9 02-02-2007 10:37 PM
BLFS: Error on chrooting into LFS environment StevePhM Linux From Scratch 13 08-01-2005 03:28 AM
build environment arkss Linux - Software 0 06-25-2005 03:54 PM

All times are GMT -5. The time now is 02:00 AM.

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