Re: [lfs-support] Error when compiling gcc, can't find /usr/include
> On Jun 9, 2017, at 12:40 PM, Bruce Dubbs wrote: > > Stating page 36 indicates you are using the pdf version of the book. Do not > use the pdf ferion to copy/paste. It causes problems. Us the html verison > of the book. I think the book should say that the first time a shell command is given. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Error when compiling gcc, can't find /usr/include
On 6/9/2017 10:40 AM, Bruce Dubbs wrote: Isaac D. Cohen wrote: Hi everyone, I recently started building an LFS and I a few questions. I am using LFS book version 8.0. ... the book says that all sources should be put in a directory where they will accessible from the chroot environment. Does this mean that I should chroot to /media/LFS/ before building binutils? The book doesn't say to do so, but I just want to make sure. I was confused about all this for awhile, too. After following the instructions *carefully*, I understood that what you end up with is something like this: /mnt/lfs/sources /mnt/lfs/tools *After* getting into the chroot environment, these look like: /sources /tools Follow the instructions. They do not tell you to use chroot until Chapter 6. Just follow the instructions as given until you understand enough to change them. Use /mnt/lfs as a separate partition and put the sources in /mnt/lfs/sources. Alan -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Error when compiling gcc, can't find /usr/include
On Fri, 09 Jun 2017 12:19:18 -0400 "Isaac D. Cohen" wrote: > Hi everyone, > > I recently started building an LFS and I a few questions. I am using > LFS book version 8.0. On page 36 before building binutils (pass 1) > the book says that all sources should be put in a directory where > they will accessible from the chroot environment. Does this mean that > I should chroot to /media/LFS/ before building binutils? The book > doesn't say to do so, but I just want to make sure. No, you carry out Chapter 5 entirely on your host system. You can't chroot at this stage since you have as yet no new system to chroot into! However, chapter 6 is carried out in chroot and uses the same sources directory, so it needs to be accessible in both modes. The book recommends $LFS/sources. > Also, in the ./configure lines for both GCC and Binutils I noticed > that whenever there is a path (besides --sysroot) is always begins > with /tools. Is this because all paths here are offset from > --sysroot=/media/LFS? Or does this have to do with chroot? The /tools directory on the $LFS is where you put the intermediate tool set built in Chapter 5. To make the references in Chapter 5 and Chapter 6 work the same way, you create a symbolic link to it, also called tools, in the root directory of your host system. So in Chapter 5, $LFS/tools is reached through this link, in the Chapter 6 chroot environment, it is accessed directly. > Finally, the reason I'm asking all these questions is because when > compiling gcc (I'm using version 3.4.6) I get the following error: > > The directory that should contain system headers does not exist: > /media/isaac/LFS/usr/include > Makefile:2569: recipe for target 'stmp-fixinc' failed > make[1]: *** [stmp-fixinc] Error 1 > > What does this error mean? It seems like it is looking for a > /usr/include directory on my LFS volume. But I thought that command > before the build (that replaces /usr/include in gcc) was supposed to > take care of that. Anyway, what can I do about this error? You're right, it doesn't exist at this stage. But the instructions provided in the book are specifically designed to prevent this kind of error. You obviously haven't followed them sufficiently accurately. Are you working as the lfs user? Did you create the correct environment for this user as described in Chapter 4? If not, there could be preset environmental variables that are interfering with your build. And did you use the exact .config options provided for binutils? For your first LFS build, you must follow the book religiously from the beginning. > Thank you very much, > Isaac D. Cohen > -- H Russman -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Error when compiling gcc, can't find /usr/include
Isaac D. Cohen wrote: Hi everyone, I recently started building an LFS and I a few questions. I am using LFS book version 8.0. On page 36 before building binutils (pass 1) Stating page 36 indicates you are using the pdf version of the book. Do not use the pdf ferion to copy/paste. It causes problems. Us the html verison of the book. the book says that all sources should be put in a directory where they will accessible from the chroot environment. Does this mean that I should chroot to /media/LFS/ before building binutils? The book doesn't say to do so, but I just want to make sure. Follow the instructions. They do not tell you to use chroot until Chapter 6. Just follow the instructions as given until you understand enough to change them. Use /mnt/lfs as a separate partition and put the sources in /mnt/lfs/sources. Also, in the ./configure lines for both GCC and Binutils I noticed that whenever there is a path (besides --sysroot) is always begins with /tools. Is this because all paths here are offset from --sysroot=/media/LFS? Or does this have to do with chroot? Chapter is creating a set of temporary tools that you will use in Chapters 6 and beyond. Again follow the instructions. Create /mnt/lfs/tools and also a symlink /tools -> /mnt/lfs/tools. Finally, the reason I'm asking all these questions is because when compiling gcc (I'm using version 3.4.6) I get the following error: version 3.4.6 of what? gcc? Section 2.2 clearly says that the minimum version of gcc for LFS is 4.7. If you are experimenting beyond the book, you are on your own. -- Bruce The directory that should contain system headers does not exist: /media/isaac/LFS/usr/include Makefile:2569: recipe for target 'stmp-fixinc' failed make[1]: *** [stmp-fixinc] Error 1 What does this error mean? It seems like it is looking for a /usr/include directory on my LFS volume. But I thought that command before the build (that replaces /usr/include in gcc) was supposed to take care of that. Anyway, what can I do about this error? Thank you very much, Isaac D. Cohen PS. The reason I'm using such old versions of the packages (ex. gcc-4.3.6 and binutils 2.14) is because I have a book that goes through the Linux kernel part by part and explains how it works internally and I want to be able to follow along. The version used in the book is Linux kernel 2.6.11. If I'm going to use that kernel, I have to build the system out of packages from back then. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
[lfs-support] Error when compiling gcc, can't find /usr/include
Hi everyone, I recently started building an LFS and I a few questions. I am using LFS book version 8.0. On page 36 before building binutils (pass 1) the book says that all sources should be put in a directory where they will accessible from the chroot environment. Does this mean that I should chroot to /media/LFS/ before building binutils? The book doesn't say to do so, but I just want to make sure. Also, in the ./configure lines for both GCC and Binutils I noticed that whenever there is a path (besides --sysroot) is always begins with /tools. Is this because all paths here are offset from --sysroot=/media/LFS? Or does this have to do with chroot? Finally, the reason I'm asking all these questions is because when compiling gcc (I'm using version 3.4.6) I get the following error: The directory that should contain system headers does not exist: /media/isaac/LFS/usr/include Makefile:2569: recipe for target 'stmp-fixinc' failed make[1]: *** [stmp-fixinc] Error 1 What does this error mean? It seems like it is looking for a /usr/include directory on my LFS volume. But I thought that command before the build (that replaces /usr/include in gcc) was supposed to take care of that. Anyway, what can I do about this error? Thank you very much, Isaac D. Cohen PS. The reason I'm using such old versions of the packages (ex. gcc-4.3.6 and binutils 2.14) is because I have a book that goes through the Linux kernel part by part and explains how it works internally and I want to be able to follow along. The version used in the book is Linux kernel 2.6.11. If I'm going to use that kernel, I have to build the system out of packages from back then. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
