On Thu, 03 May 2012 16:52, Scott Robertson wrote:
> Hello,
>
> Can someone explain what the directory structure is supposed to look like
> in Chapter 5?
>
> 1. Where does the Binutils folder/directory go? Where does the GCC folder
> go? That's all the further I have gotten so far. I think I will probably
> want to know where all the folders go. I created a separate partition for
> LFS, and put the folders there, is that right, or not? Or is it supposed to
> go into the /mnt/lfs folder? Or somewhere else?
>
At Chapter 3.1 Packages and Patchws Introduction.
$LFS/sources can be used both as the place to store the tarballs and patches
and as a working directory. By using this directory, the required elements
will be located on the LFS partition and will be available during all stages
of the building process.
To create this directory, execute the following command, as user root, before
starting the download session:
mkdir -v $LFS/sources
and
At Chapter 5.3 General Compilation Instructions
Important
To re-emphasize the build process:
1. Place all the sources and patches in a directory that will be
accessible from the chroot environment such as /mnt/lfs/sources/. Do not put
sources in /mnt/lfs/tools/.
2. Change to the sources directory.
3. For each package:
1. Using the tar program, extract the package to be built.
In Chapter 5, ensure you are the lfs user when extracting the package.
2. Change to the directory created when the package was
extracted.
3. Follow the book's instructions for building the package.
4. Change back to the sources directory.
5. Delete the extracted source directory and any
<package>-build directories that were created in the build process unless
instructed otherwise.
>
> 2. Can someone also explain permissions? Who is supposed to have
> permissions on what? What permissions are supposed to be on the Binutils
> and GCC directories? root? lfs?
>
> And what are they supposed to be? read, write and execute?
>
At Chapter 4.3 Adding thge LFS User
When logged in as user root, making a single mistake can damage or destroy a
system. Therefore, we recommend building the packages in this chapter as an
unprivileged user. You could use your own user name, but to make it easier to
set up a clean working environment, create a new user called lfs as a member
of a new group (also named lfs) and use this user during the installation
process. As root, issue the following commands to add the new user:
At Chapter 4.4 Setting up the Environment
Setting the user file-creation mask (umask) to 022 ensures that newly created
files and directories are only writable by their owner, but are readable and
executable by anyone (assuming default modes are used by the open(2) system
call, new files will end up with permission mode 644 and directories with
mode 755).
> 3. What directory am I supposed to be in when I execute the commands? As
> I said, I have an LFS partition, so am I supposed to be in /media/LFS? Or
> more like /mnt/lfs? Or somewhere else?
>
See answer above or to spell it out:
$LFS/sources/binutils-x.xx
> 4. Also, what does the two dots and slash mean? ../(some command)
>
> How does that factor into it?
>
>
On Thu, 03 May 2012 18:39, Scott Robertson wrote:
> 1) I don't think that is true. The manual contradicts itself. On the one
> hand it tells you to put stuff in $LFS/tools, but then it specifically
> recommends NOT putting things in there during the initial compilation
> process. It also tells people to create an LFS partition and suggests that
> it be used, but doesn't say how or when (at least as far as I've gotten).
> It also seems to contradict itself by telling people to uncompress the
> tar.bz2 files, but then proceeds as if they were not uncompressed, so
> clearly there are some contradictory logic errors in the manual.
It clearly says that the COMPILED programes go into $LFS/tools at 4.2 Creating
the $LFS/tools directory:
All programs compiled in Chapter 5 will be installed under $LFS/tools to keep
them separate from the programs compiled in Chapter 6. The programs compiled
here are temporary tools and will not be a part of the final LFS system. By
keeping these programs in a separate directory, they can easily be discarded
later after their use. This also prevents these programs from ending up in
the host production directories (easy to do by accident in Chapter 5).
In 5.3 General Compilation Instructions:
Place all the sources and patches in a directory that will be accessible from
the chroot environment such as /mnt/lfs/sources/. Do not put sources
in /mnt/lfs/tools/.
This is not a contradiction.
..sending me 4 unhelpful e-mails
Dont know where you get the 4 messages from ... I only sent 2 but both were
addressed to you personally and the list. This is a standard practice with
list server mail which I believe is to ensure that you (the OP) gets a
response as soon as possible even if the list server fails for whatever
reason.
I still wish you good luck with your LFS journey.
Tony
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
