Re: [blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
When you installed poppler, you should have created /usr/lib/pkgconfig/poppler.pc. Check to see if that is present. I have no idea what LIBQPDF is. LD_LIBRARY_PATH is for specifying library paths for running programs. I suspect you want LIBRARY_PATH for gcc to find included files. It would help to see the error, but not too much before of after the error. Just the line that actually generates the error and it's output would be fine. -- Bruce Thanks Bruce, /usr/lib/pkgconfig/poppler.pc does not exist. Not sure how to create it or what should be in it. What record I have shows the error as: filter/pdftoopvp/oprs/OPRS.cxx:27:22: fatal error: goo/gmem.h: No such file or directory compilation terminated. make: *** [pdftoopvp-OPRS.o] Error 1 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Virtual box
On 11/05/12 08:27, Rahul Udasi wrote: Hi, has anyone built lfs on a virtual machine? Sent from my BlackBerry device on the Rogers Wireless Network I have built LFS on VMware Player, VMware Sserver, VMware ESXi and VirtualBox. The snapshot-feature is great, use it! Groet, Thomas -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Virtual box
Hi, I started LFS using VirtualBox sometime ago (version 6.3?) and run into problems during gcc tests. There were some bad failures as well as bad successes regarding (if I rememeber correctly) scheduling/threads. I tried it natively and that did work. (The hardware was an Apple MacBook Core Duo.) Anway, does nobody else had strange test results using VirtualBox? Only me? (A little bit off-topic: I use VirtualBox (Windows host, Linux guest) to build some project and I found a reproducable bug which causes some files not to be rebuild after beeing changed. I use a script which replaces symlinks and I guess some meta data is not written/synced correctly. VMWare does not show this bug, but is slower in execution .. ;) So... imho you should at least pay attention if something goes wrong.) But you are right, snapshotting is/would be very helpfull. Using btrfs instead of ext3 is no alternative as this causes a big deviation, I guess. Regards, doak --- Original message --- From: Thomas de Roo tho...@de-roo.org To: lfs-support@linuxfromscratch.org Sent: '12-11-05, 13:30 On 11/05/12 08:27, Rahul Udasi wrote: Hi, has anyone built lfs on a virtual machine? Sent from my BlackBerry device on the Rogers Wireless Network I have built LFS on VMware Player, VMware Sserver, VMware ESXi and VirtualBox. The snapshot-feature is great, use it! Groet, Thomas -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] What Is The LFS Partition?
Howdy, I've done a major reset by giving up on installing an LFS system on my old 32-bit computer, and am now installing it on a new 64-bit system. The new system now has Fedora as the host system. It's installed on /dev/sdb and I want to put LFS on a blank 256G SSD -- /dev/sda. In trying to format /dev/sda I'm running into a conceptual problem. I partition the disk into: /dev/sda1 for /boot /dev/sda2 Extended partition /dev/sda5 swap /dev/sda6 for / /dev/sda7 for /usr and so forth. This is following the suggestions in the LFS book, section 2.2.1.3. When I go to section 2.3 to create a file system on the partition, the book says: To create an ext3 file system on the LFS partition, run the following: mke2fs -jv /dev/xxx Replace xxx with the name of the LFS partition (hda5 in our previous example). What should xxx be in the above example? I'm confused because the book speaks of THE LFS partition, as if there were just one, but there are obviously a number of partitions. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
I may not be responding correctly so my responses don't end up in the correct thread -- if so, I apologize When you installed poppler, you should have created /usr/lib/pkgconfig/poppler.pc. Check to see if that is present. Actually /usr/lib/pkgconfig/poppler.pc does exist. However, I am using a x86_64 system and have a /usr/lib64/pkgconfig also. When I built poppler and libqpdf I just used teh defaults. In /usr/lib64/pkgconfig there is a poppler.pc file which lists the version as 0.16. The poppler.pc in /usr/lib lists the version as 0.20.5. Should I uninstall and recompile poppler and libqpdf with LIBDIR=/usr/lib64? Would the correct steps be to first do a make uninstall for poppler and libqpf, then remove the directories created when the tarball was extracted, re-extract the archive, then proceed with ./configure --LIBDIR=/usr/lib64 and then try to recompile cups-filters? Thanks -- Leon -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Le lundi 05 novembre à 14:24, Alan Feuerbacher a écrit : Howdy, I've done a major reset by giving up on installing an LFS system on my old 32-bit computer, and am now installing it on a new 64-bit system. The new system now has Fedora as the host system. It's installed on /dev/sdb and I want to put LFS on a blank 256G SSD -- /dev/sda. In trying to format /dev/sda I'm running into a conceptual problem. I partition the disk into: /dev/sda1 for /boot /dev/sda2 Extended partition /dev/sda5 swap /dev/sda6 for / /dev/sda7 for /usr and so forth. This is following the suggestions in the LFS book, section 2.2.1.3. When I go to section 2.3 to create a file system on the partition, the book says: To create an ext3 file system on the LFS partition, run the following: mke2fs -jv /dev/xxx Replace xxx with the name of the LFS partition (hda5 in our previous example). What should xxx be in the above example? I'm confused because the book speaks of THE LFS partition, as if there were just one, but there are obviously a number of partitions. The right one is / (/dev/sda6) and in next section you'll see that you'll have to mount /usr (don't forget to create the filesystem for it). IMHO, the /boot can wait but you'll have to take it in consideration later. -- Ph. Delavalade -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
Leon Goldman wrote: I may not be responding correctly so my responses don't end up in the correct thread -- if so, I apologize When you installed poppler, you should have created /usr/lib/pkgconfig/poppler.pc. Check to see if that is present. Actually /usr/lib/pkgconfig/poppler.pc does exist. However, I am using a x86_64 system and have a /usr/lib64/pkgconfig also. When I built poppler and libqpdf I just used teh defaults. In /usr/lib64/pkgconfig there is a poppler.pc file which lists the version as 0.16. The poppler.pc in /usr/lib lists the version as 0.20.5. Should I uninstall and recompile poppler and libqpdf with LIBDIR=/usr/lib64? Would the correct steps be to first do a make uninstall for poppler and libqpf, then remove the directories created when the tarball was extracted, re-extract the archive, then proceed with ./configure --LIBDIR=/usr/lib64 and then try to recompile cups-filters? In LFS we said do do 'ln -sv lib /lib64 ln -sv lib /usr/lib64' All of LFS and BLFS assumes that. The only reason to have separate lib directories is for the case when you have a 32-bit binary program that you can't build with 64-bit system. See the discussion 'iii. LFS Target Architectures' in LFS. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Virtual box
Rahul Udasi wrote: Hi, has anyone built lfs on a virtual machine? BLFS shows how to build qemu-kvm. LFS can be built there. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Philippe Delavalade wrote: When I go to section 2.3 to create a file system on the partition, the book says: To create an ext3 file system on the LFS partition, run the following: mke2fs -jv /dev/xxx Replace xxx with the name of the LFS partition (hda5 in our previous example). What should xxx be in the above example? I'm confused because the book speaks of THE LFS partition, as if there were just one, but there are obviously a number of partitions. The right one is / (/dev/sda6) and in next section you'll see that you'll have to mount /usr (don't forget to create the filesystem for it). Thank you! But I still don't understand what I'm doing. How do I know which of the various devices (/dev/sdaN) is supposed to be used with mke2fs? I read the man page for mke2fs and it's as clear as mud. And the LFS book is completely unclear about exactly what is going on. Are you saying that I have to run mke2fs for EACH of the devices /dev/sda1, /dev/sda2 and so forth? I already know (please excuse my ignorance) that running mke2fs with /dev/sda completely wipes out the partitions I just made, so that's obviously not supposed to be done. IMHO, the /boot can wait but you'll have to take it in consideration later. I don't understand this at all. Later we mount the various partitions. Is that what you're referring to? Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Philippe Delavalade wrote: Le lundi 05 novembre à 14:24, Alan Feuerbacher a écrit : Howdy, I've done a major reset by giving up on installing an LFS system on my old 32-bit computer, and am now installing it on a new 64-bit system. The new system now has Fedora as the host system. It's installed on /dev/sdb and I want to put LFS on a blank 256G SSD -- /dev/sda. In trying to format /dev/sda I'm running into a conceptual problem. I partition the disk into: /dev/sda1 for /boot /dev/sda2 Extended partition /dev/sda5 swap /dev/sda6 for / /dev/sda7 for /usr For an SSD drive, I suggest getting gptdisk (fdisk syntax) or gparted (challenging syntax) and partitioning the drive as a gpt drive. The first partition should be at sector 2048 or 1 MB. Make /boot 1 M, swap 2G, / 20G, and /home as desired. I like to leave some space. I advise against a separate /usr. The reasons for that (small, expensive disk drives) are not really valid any more. For an ssd drive, you will want to disable atime *after* completing LFS. For example: /dev/sdc6 / ext4 noatime,discard,data=writeback There are no extended partitions for a gpt partitions disk. None are needed. and so forth. This is following the suggestions in the LFS book, section 2.2.1.3. When I go to section 2.3 to create a file system on the partition, the book says: To create an ext3 file system on the LFS partition, run the following: mke2fs -jv /dev/xxx Replace xxx with the name of the LFS partition (hda5 in our previous example). What should xxx be in the above example? I'd use: mkfs -t ext2 /dev/sda1 mkfs -t ext4 /dev/sda6 mount /dev/sda6 /mnt/lfs Mount sda1 as /boot in chapter 6. You don't need any others while building LFS. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Le lundi 05 novembre à 17:04, Feuerbacher, Alan a écrit : Thank you! But I still don't understand what I'm doing. How do I know which of the various devices (/dev/sdaN) is supposed to be used with mke2fs? I read the man page for mke2fs and it's as clear as mud. And the LFS book is completely unclear about exactly what is going on. The book suppose that you have some knowledge about linux and partitions :-) And the man about mke2fs is not so unclear, as I can remember. Are you saying that I have to run mke2fs for EACH of the devices /dev/sda1, /dev/sda2 and so forth? You'll have to do it for /dev/sda6 and for /dev/sda7 ; on sda2, I think you plane to install your home and that can wait ; for /dev/sda1 I think you can wait still the installation of the bootloader ; and /dev/sda5 is the swap, you'll see what to do with it at the end of your current section. Anyway, there is certainly a swap partition on your host system. I already know (please excuse my ignorance) that running mke2fs with /dev/sda completely wipes out the partitions I just made, so that's obviously not supposed to be done. Rigth :-) IMHO, the /boot can wait but you'll have to take it in consideration later. I don't understand this at all. Later we mount the various partitions. Is that what you're referring to? The /boot is not used until installing grub or lilo. Maybe, an ext2 could be better for this little partition. For your home, if I guess what you want to do, I mean for sda2, maybe you can use ext4. -- Ph. Delavalade -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Bruce wrote: But I still don't understand what I'm doing. I get the feeling that you are not ready for LFS. Use a standard distro for a while. Perhaps you don't know how persistent I am. :-) Seriously, I've used Unix and Linux as a plain user for 33 years. Now I want to learn the nuts and bolts. Using a standard distro is not going to teach me much about making filesystems and so forth, because the work is already done for you. One of the problems with learning the nuts and bolts of Linux is, as Richard Stallman wrote back in the 1990s, that the documentation is sparse at best. I have no problem with that, and learning by experimenting, but sometimes it's a lot more efficient to get help from gurus. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Bruce wrote: For an SSD drive, I suggest getting gptdisk (fdisk syntax) or gparted (challenging syntax) and partitioning the drive as a gpt drive. The first partition should be at sector 2048 or 1 MB. Make /boot 1 M, swap 2G, / 20G, and /home as desired. I like to leave some space. I advise against a separate /usr. The reasons for that (small, expensive disk drives) are not really valid any more. Yow! Maybe I should think about just using a regular hard drive. But I'm a glutton for punishment. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Feuerbacher, Alan wrote: One of the problems with learning the nuts and bolts of Linux is, as Richard Stallman wrote back in the 1990s, that the documentation is sparse at best. That's not true today. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
On Mon, Nov 05, 2012 at 09:39:10AM -0600, Bruce Dubbs wrote: Leon Goldman wrote: Actually /usr/lib/pkgconfig/poppler.pc does exist. However, I am using a x86_64 system and have a /usr/lib64/pkgconfig also. When I built poppler and libqpdf I just used teh defaults. In /usr/lib64/pkgconfig there is a poppler.pc file which lists the version as 0.16. The poppler.pc in /usr/lib lists the version as 0.20.5. Should I uninstall and recompile poppler and libqpdf with LIBDIR=/usr/lib64? Would the correct steps be to first do a make uninstall for poppler and libqpf, then remove the directories created when the tarball was extracted, re-extract the archive, then proceed with ./configure --LIBDIR=/usr/lib64 and then try to recompile cups-filters? In LFS we said do do 'ln -sv lib /lib64 ln -sv lib /usr/lib64' All of LFS and BLFS assumes that. The only reason to have separate lib directories is for the case when you have a 32-bit binary program that you can't build with 64-bit system. See the discussion 'iii. LFS Target Architectures' in LFS. Ah, the 'joys' of multilib. First, I cannot recommend that you ever run 'make uninstall' : that is hardly ever tested - in most cases it will work fine. But if it doesn't, your system might be broken. As Bruce says, we don't support multilib in the book. If your existing system is multilib, you might want to look at cross-lfs (specifically cblfs - from memory, almost everything is built as both 32-bit and 64-bit). For sorting out what you have done : everything in lib64 should be 64-bit (use file to check the binaries), everything in lib on multilib should be 32-bit. You haven't specified -m64 or -m32 on what you've done, so looking at the programs you compiled should tell you if your gcc defaults to 32-bit or 64-bit : I would expect 32-bit but knowing is better than assuming. If you are building as 64-bit, use PKG_CONFIG_PATH=/usr/lib64/pkgconfigfile as well as LIBDIR, and forcing -m64 if you need to. If you build as 32-bit on that system, and 64-bit turns out to be its default, use -m32 as well as .usr/lib. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Philippe Delavalade wrote: I read the man page for mke2fs and it's as clear as mud. And the LFS book is completely unclear about exactly what is going on. The book suppose that you have some knowledge about linux and partitions :-) Well I do have *some* knowledge. It's just a matter of how much. :-) Seriously, I'm doing this in order to learn about all this stuff. And the man about mke2fs is not so unclear, as I can remember. It is to me. I'll have to think a lot more about what you and Bruce have told me, in terms of the mke2fs man page, and try to understand what I'm missing. Are you saying that I have to run mke2fs for EACH of the devices /dev/sda1, /dev/sda2 and so forth? You'll have to do it for /dev/sda6 and for /dev/sda7 ; on sda2, I think you plane to install your home and that can wait ; for /dev/sda1 I think you can wait still the installation of the bootloader ; and /dev/sda5 is the swap, you'll see what to do with it at the end of your current section. My plan WAS to have /dev/sda1 as the /boot partition, and the rest as whatever fdisk forces you to have. After some experimentation and absorbing the material in the LFS book, I hit on this: /dev/sda1 /boot500M /dev/sda2 extended partition containing everything else /dev/sda5 swap 32G (I have 16G of RAM) /dev/sda6 /usr /dev/sda7 /opt and so forth, following the LFS book. Questions: Why would I NOT use mke2fs immediately to make filesystems on sda1, sda2 and sda5? I want to know enough to really understand what is going on sufficiently that I could teach it to my grandmother. :-) Why would I wait until the installation of the bootloader? Wait for what? Anyway, there is certainly a swap partition on your host system. Yes, but what does that have to do with the LFS system? I already know (please excuse my ignorance) that running mke2fs with /dev/sda completely wipes out the partitions I just made, so that's obviously not supposed to be done. Rigth :-) Ok, then: how does one get that information from the man page on mke2fs? IMHO, the /boot can wait but you'll have to take it in consideration later. I don't understand this at all. Later we mount the various partitions. Is that what you're referring to? The /boot is not used until installing grub or lilo. Maybe, an ext2 could be better for this little partition. For your home, if I guess what you want to do, I mean for sda2, maybe you can use ext4. OK, but the LFS book clearly says that every partition will be ext3. Je ne comprends pas. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Bruce wrote: One of the problems with learning the nuts and bolts of Linux is, as Richard Stallman wrote back in the 1990s, that the documentation is sparse at best. That's not true today. Ok, then, in addition to beating myself up with LFS, can you suggest any reading material that really goes into the nuts and bolts? I mean like discussing the details of what I'm trying to learn from you and Philippe with regard to mke2fs and partitioning and all that? Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
On Mon, Nov 05, 2012 at 08:24:32AM -0500, Alan Feuerbacher wrote:
Howdy,
I've done a major reset by giving up on installing an LFS system on my
old 32-bit computer, and am now installing it on a new 64-bit system.
The new system now has Fedora as the host system. It's installed on
/dev/sdb and I want to put LFS on a blank 256G SSD -- /dev/sda.
In trying to format /dev/sda I'm running into a conceptual problem. I
partition the disk into:
/dev/sda1 for /boot
/dev/sda2 Extended partition
/dev/sda5 swap
/dev/sda6 for /
/dev/sda7 for /usr
and so forth. This is following the suggestions in the LFS book, section
2.2.1.3.
I would definitely go with your later idea of using a conventional
disk, at least until you understand what you are doing.
BUT, the partition layout is just an example. If this is intended
to eventually become your only disk (running LFS all the time),
/boot is good. If you will always have a distro, you can use its
/boot and swap - but you will need to make sure the distro doesn't
remove the LFS entr{y,ies} when updating. After that, it becomes a
matter of choice:
/usr is very old-school - most people don't bother to separate it
from / (and therefore / will need to be big).
/ will be where you build LFS - but if you then use that system to
build a newer one, you need another equally big partition. In my
own case I've got six 8GB filesystems available for building [ small,
for a modern desktop, but then I deviate by putting my /sources on an
nfs mount ].
You also need /home separate, so that you can share it between the
systems.
Oh, you also need to format all the partitions before you can use
them. 'man mkfs.ext4' might look frightening, but in most cases all
you need are the defaults, so 'mkfs -t ext4 /dev/sdXN' is usually
all you need. This is one of the places where the documentation
*is* thorough and extensive!
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Le lundi 05 novembre à 17:47, Feuerbacher, Alan a écrit : Philippe Delavalade wrote: I read the man page for mke2fs and it's as clear as mud. And the LFS book is completely unclear about exactly what is going on. The book suppose that you have some knowledge about linux and partitions :-) Well I do have *some* knowledge. It's just a matter of how much. :-) Seriously, I'm doing this in order to learn about all this stuff. That was my goal too ! Now, I have always to learn ! And the man about mke2fs is not so unclear, as I can remember. It is to me. I'll have to think a lot more about what you and Bruce have told me, in terms of the mke2fs man page, and try to understand what I'm missing. Are you saying that I have to run mke2fs for EACH of the devices /dev/sda1, /dev/sda2 and so forth? You'll have to do it for /dev/sda6 and for /dev/sda7 ; on sda2, I think you plane to install your home and that can wait ; for /dev/sda1 I think you can wait still the installation of the bootloader ; and /dev/sda5 is the swap, you'll see what to do with it at the end of your current section. My plan WAS to have /dev/sda1 as the /boot partition, and the rest as whatever fdisk forces you to have. After some experimentation and absorbing the material in the LFS book, I hit on this: /dev/sda1 /boot500M /dev/sda2 extended partition containing everything else /dev/sda5 swap 32G (I have 16G of RAM) /dev/sda6 /usr /dev/sda7 /opt and so forth, following the LFS book. That's not what was in your first post ; now, THE lfs partition is sda2 ; I'd never used a proc partition. And I don't know about fdisk, I prefer cfdisk :-) Questions: Why would I NOT use mke2fs immediately to make filesystems on sda1, sda2 and sda5? I want to know enough to really understand what is going on sufficiently that I could teach it to my grandmother. :-) There no need to wait but the boot partition is used later, that's all, no problem to install the filesystem right now. Why would I wait until the installation of the bootloader? Wait for what? of course, why not :-) Anyway, there is certainly a swap partition on your host system. Yes, but what does that have to do with the LFS system? One swap is sufficient. I already know (please excuse my ignorance) that running mke2fs with /dev/sda completely wipes out the partitions I just made, so that's obviously not supposed to be done. Rigth :-) Ok, then: how does one get that information from the man page on mke2fs? IMHO, the /boot can wait but you'll have to take it in consideration later. I don't understand this at all. Later we mount the various partitions. Is that what you're referring to? The /boot is not used until installing grub or lilo. Maybe, an ext2 could be better for this little partition. For your home, if I guess what you want to do, I mean for sda2, maybe you can use ext4. OK, but the LFS book clearly says that every partition will be ext3. Je ne comprends pas. The book suggests ext3 and it is of course a safe idea and ext2 is not so convinient for large partition. -- Ph. Delavalade -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
I might suggest trying gentoo linux or at least look at the installation instructions. Using mke2fs does not remove your partitions it formats them to the desired file system and as for using a ssd drive up it might be better to use a standard drive for now until you can setup an environment that allows you to do some of the compiling in temp ram file systems to cut down on the rewrites on the ssd drive. And as for documentation the web is full of I formation I relied on it when I first built LFS but I also had several years of experience installing gentoo and that helped a lot. On Nov 5, 2012 10:52 AM, Feuerbacher, Alan afeuerbac...@allegromicro.com wrote: Bruce wrote: One of the problems with learning the nuts and bolts of Linux is, as Richard Stallman wrote back in the 1990s, that the documentation is sparse at best. That's not true today. Ok, then, in addition to beating myself up with LFS, can you suggest any reading material that really goes into the nuts and bolts? I mean like discussing the details of what I'm trying to learn from you and Philippe with regard to mke2fs and partitioning and all that? Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Feuerbacher, Alan wrote: Philippe Delavalade wrote: I read the man page for mke2fs and it's as clear as mud. And the LFS book is completely unclear about exactly what is going on. The book suppose that you have some knowledge about linux and partitions :-) Well I do have *some* knowledge. It's just a matter of how much. :-) Seriously, I'm doing this in order to learn about all this stuff. And the man about mke2fs is not so unclear, as I can remember. It is to me. I'll have to think a lot more about what you and Bruce have told me, in terms of the mke2fs man page, and try to understand what I'm missing. Are you saying that I have to run mke2fs for EACH of the devices /dev/sda1, /dev/sda2 and so forth? You'll have to do it for /dev/sda6 and for /dev/sda7 ; on sda2, I think you plane to install your home and that can wait ; for /dev/sda1 I think you can wait still the installation of the bootloader ; and /dev/sda5 is the swap, you'll see what to do with it at the end of your current section. My plan WAS to have /dev/sda1 as the /boot partition, and the rest as whatever fdisk forces you to have. After some experimentation and absorbing the material in the LFS book, I hit on this: /dev/sda1 /boot500M /dev/sda2 extended partition containing everything else /dev/sda5 swap 32G (I have 16G of RAM) /dev/sda6 /usr /dev/sda7 /opt and so forth, following the LFS book. /boot of 500M is a little large. I normally use 100M, but it probably doesn't matter. For a first build, do not use a separate /usr. Don't open yourself to potential problems until you understand more. You do not need 32G of swap. That 2x RAM rule is obsolete. http://askubuntu.com/questions/49109/i-have-16gb-ram-do-i-need-32gb-swap I suggest 2G swap. You can always add more later. If you are going to use a MSDOS partition table, why skip 2 parimary partitions? It really doesn't matter that much though. Questions: Why would I NOT use mke2fs immediately to make filesystems on sda1, sda2 and sda5? I want to know enough to really understand what is going on sufficiently that I could teach it to my grandmother. :-) You can do it whenever you like. Why would I wait until the installation of the bootloader? Wait for what? I think the idea was to put off the decision until you actually needed to install something on the partition. It really doesn't matter though. Anyway, there is certainly a swap partition on your host system. Yes, but what does that have to do with the LFS system? All systems can share the same swap space. It actually makes some sense to have the swap partition on a different drive for marginally improved performance (but you really don't want to use swap anyway, just have it available if absolutely needed). Ok, then: how does one get that information from the man page on mke2fs? Man pages are not meant as a primary learning tool. They are supposed to be quick references for options, etc. mke2fs is used to create an ext2, ext3, or ext4 filesystem, usually in a disk partition. What part do you not understand? OK, but the LFS book clearly says that every partition will be ext3. In Section 3.3 it says Instructions for creating other file systems can be found at http://www.linuxfromscratch.org/blfs/view/svn/postlfs/filesystems.html.; ext3 is just used as the primary example. If you don't know why you want to deviate from the book, don't. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
On Mon, Nov 05, 2012 at 04:47:48PM +, Feuerbacher, Alan wrote: Why would I NOT use mke2fs immediately to make filesystems on sda1, sda2 and sda5? I want to know enough to really understand what is going on sufficiently that I could teach it to my grandmother. :-) If you are using ext2/3/4 then you *should* use it to make a filesystem on each partition (except for swap). That way, if you lose your notes about what is where, you can mount the filesystem from a running system to see what it contains :) Why would I wait until the installation of the bootloader? Wait for what? Wait for confidence ? 8) The bootloader for an existing linux system, even on a different disk, can have an entry for LFS added to it. If you have an existing system, there is no reason why the LFS disk needs to be sda. Anyway, there is certainly a swap partition on your host system. Yes, but what does that have to do with the LFS system? You can use it. Only one system can run at a time. OK, but the LFS book clearly says that every partition will be ext3. Je ne comprends pas. It used to say ext2. For a modern, large, disk (and where a kernel which understands ext4 is alwayys going to be used), ext4 is better. For /boot, ext3 or ext2 is probably more efficient - my own /boot [ about 100MB ] is large, so plenty of space for a journal. Until a couple of days ago, when I updated a few things on my previous machine, I had forgotten that the version of e2fsprogs in LFS-6.6 was slightly too old for ext4, which was why /home on that box was still ext3 (it has an old 6.6 system available). During the boot, the filesystems all had to be fscked (last checked more than 200 days ago) : '/' on ext4 wizzed through, /home on ext3 took for ever. Some people use different filesystems, and obviously they need to install the tools for those. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
Thank you all. It would appear that I am too far in over my head and I should quit while I am ahead. Only next choice seems to be to reinstall the OS and leave well enough alone. For now I will leave it as broken as it is an hope I don't make it worse. Leon On 11/05/2012 11:37 AM, Ken Moffat wrote: On Mon, Nov 05, 2012 at 09:39:10AM -0600, Bruce Dubbs wrote: Leon Goldman wrote: Actually /usr/lib/pkgconfig/poppler.pc does exist. However, I am using a x86_64 system and have a /usr/lib64/pkgconfig also. When I built poppler and libqpdf I just used teh defaults. In /usr/lib64/pkgconfig there is a poppler.pc file which lists the version as 0.16. The poppler.pc in /usr/lib lists the version as 0.20.5. Should I uninstall and recompile poppler and libqpdf with LIBDIR=/usr/lib64? Would the correct steps be to first do a make uninstall for poppler and libqpf, then remove the directories created when the tarball was extracted, re-extract the archive, then proceed with ./configure --LIBDIR=/usr/lib64 and then try to recompile cups-filters? In LFS we said do do 'ln -sv lib /lib64 ln -sv lib /usr/lib64' All of LFS and BLFS assumes that. The only reason to have separate lib directories is for the case when you have a 32-bit binary program that you can't build with 64-bit system. See the discussion 'iii. LFS Target Architectures' in LFS. Ah, the 'joys' of multilib. First, I cannot recommend that you ever run 'make uninstall' : that is hardly ever tested - in most cases it will work fine. But if it doesn't, your system might be broken. As Bruce says, we don't support multilib in the book. If your existing system is multilib, you might want to look at cross-lfs (specifically cblfs - from memory, almost everything is built as both 32-bit and 64-bit). For sorting out what you have done : everything in lib64 should be 64-bit (use file to check the binaries), everything in lib on multilib should be 32-bit. You haven't specified -m64 or -m32 on what you've done, so looking at the programs you compiled should tell you if your gcc defaults to 32-bit or 64-bit : I would expect 32-bit but knowing is better than assuming. If you are building as 64-bit, use PKG_CONFIG_PATH=/usr/lib64/pkgconfigfile as well as LIBDIR, and forcing -m64 if you need to. If you build as 32-bit on that system, and 64-bit turns out to be its default, use -m32 as well as .usr/lib. ĸen -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Thank you all very much for your advice! Here's what I propose to do now, given your inputs: Don't put LFS on the SSD -- use a regular hard drive. Set up the partitions like this, using an ext4 filesystem: /dev/sda1 /boot 100M /dev/sda2 Extended Linux partition ~100G /dev/sda5 Linux swap 2G /dev/sda6 / ~98G Use mke2fs -t ext4 to create filesystems on /dev/sda1 and /dev/sda6. I should NOT use mke2fs to create filesystems on /dev/sda2 and /dev/sda5. I don't fully understand why not, though. Can someone explain? Under the above scheme, the extended linux partition CONTAINS the swap and / logical partitions, so it seems reasonable that you would not use mke2fs both on it, and on the partitions it contains, right? On the other hand, why would swap not be considered a filesystem? And why would you not make a filesystem on sda2, thereby (in my naive brain, anyway) not having to make a filesystem on sda6? Further, why would you not make the whole drive -- /dev/sda -- one filesystem? Another thing is that there seem to be several notions of a filesystem. From http://www.ibm.com/developerworks/linux/library/l-linux-filesystem/ I get this general definition: What is a file system? I'll start with an answer to the most basic question, the definition of a file system. A file system is an organization of data and metadata on a storage device. The man page for mke2fs talks about making filesystems in disk partitions. So a filesystem in the general sense can contain one or more filesystems in the mke2fs sense, and it's not always clear to me (again, a newbie to this stuff) which one is being talked about. I suppose experience will take care of that. There were good and interesting answers from various people, and I'll comment further after I go home and try again. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Partitions and filesystems are not identical on Linux/Unix systems. You carve a drive up into partitions, and you are free to format each partition with whatever filesystem you want. Every other operating system I am aware of does not make this distinction. I suppose the reason is to avoid duplicating the code needed to create a partition whenever someone creates a new type of filesystem. Swap space does not have a filesystem because it does not store files. It stores memory pages. You do need to specify that it will be a swap partition when you create the partition. sda2 is not really a partition. It contains the extended partitions. In your case, sda5 and sda6. sda refers to the drive, not to the partitions that you have on the drive. You can make a partition the same size as the drive, but it is the partition that contains the filesystem, not the drive. - Original Message - From: Alan Feuerbacher afeuerbac...@allegromicro.com To: LFS Support List lfs-support@linuxfromscratch.org Sent: Monday, November 5, 2012 1:11:04 PM Subject: Re: [lfs-support] What Is The LFS Partition? Thank you all very much for your advice! Here's what I propose to do now, given your inputs: Don't put LFS on the SSD -- use a regular hard drive. Set up the partitions like this, using an ext4 filesystem: /dev/sda1 /boot 100M /dev/sda2 Extended Linux partition ~100G /dev/sda5 Linux swap 2G /dev/sda6 / ~98G Use mke2fs -t ext4 to create filesystems on /dev/sda1 and /dev/sda6. I should NOT use mke2fs to create filesystems on /dev/sda2 and /dev/sda5. I don't fully understand why not, though. Can someone explain? Under the above scheme, the extended linux partition CONTAINS the swap and / logical partitions, so it seems reasonable that you would not use mke2fs both on it, and on the partitions it contains, right? On the other hand, why would swap not be considered a filesystem? And why would you not make a filesystem on sda2, thereby (in my naive brain, anyway) not having to make a filesystem on sda6? Further, why would you not make the whole drive -- /dev/sda -- one filesystem? Another thing is that there seem to be several notions of a filesystem. From http://www.ibm.com/developerworks/linux/library/l-linux-filesystem/ I get this general definition: What is a file system? I'll start with an answer to the most basic question, the definition of a file system. A file system is an organization of data and metadata on a storage device. The man page for mke2fs talks about making filesystems in disk partitions. So a filesystem in the general sense can contain one or more filesystems in the mke2fs sense, and it's not always clear to me (again, a newbie to this stuff) which one is being talked about. I suppose experience will take care of that. There were good and interesting answers from various people, and I'll comment further after I go home and try again. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
dennisjperk...@comcast.net wrote: ... sda refers to the drive, not to the partitions that you have on the drive. You can make a partition the same size as the drive, but it is the partition that contains the filesystem, not the drive. Thank you! That clears up a lot. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
dennisjperk...@comcast.net wrote: Partitions and filesystems are not identical on Linux/Unix systems. You carve a drive up into partitions, and you are free to format each partition with whatever filesystem you want. Every other operating system I am aware of does not make this distinction. Not true. Windows has FAT and NTFS. sda2 is not really a partition. It contains the extended partitions. In your case, sda5 and sda6. Actually an extended partition is a partition, but it has sub-partitions. All this stuff is avoided with a GUID Partition Table (GPT) which is a lot more sane in the world of large disk drives. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Le lundi 05 novembre à 21:11, Feuerbacher, Alan a écrit : Thank you all very much for your advice! Here's what I propose to do now, given your inputs: Don't put LFS on the SSD -- use a regular hard drive. Set up the partitions like this, using an ext4 filesystem: /dev/sda1 /boot 100M /dev/sda2 Extended Linux partition ~100G /dev/sda5 Linux swap 2G /dev/sda6 / ~98G This seems odd to me. Maybe I'm wrong but your swap seems too small for your 16GB of RAM and you told you have a Fedora on sdb2, so swap is certainly on that drive (i don't know about fedora but I can't imagine there's no swap on sdb). The boot partition is not required ; you've already a boot partition or directory on sdb. What do you plane to put on your extended sda2 ? Following the lfs book, you just need one partition ; you can have a /usr partition if you like and a var one and a tmp one, etc. It's your first built and, maybe I'm wrong, but you'll certainly not work with lfs for this first time, perhaps later... As to me, I built lfs many times but I never continue whith blfs ; debian is my work system ; lfs is just to learn and undertand more deeply a lot of things. Use mke2fs -t ext4 to create filesystems on /dev/sda1 and /dev/sda6. Ext4 seems inapropriate for your little boot partition. IMHO use ext2. I should NOT use mke2fs to create filesystems on /dev/sda2 and /dev/sda5. I don't fully understand why not, though. Can someone explain? On the swap partition, you'll don't write anything ; this partition is used by the system as a memory when your ram is unsufficient. Under the above scheme, the extended linux partition CONTAINS the swap and / logical partitions, so it seems reasonable that you would not use mke2fs both on it, and on the partitions it contains, right? sda2 doesn't contain0 sda5 and sda6. You've misunderstood something (or it's me :-) ). On the other hand, why would swap not be considered a filesystem? See above. And why would you not make a filesystem on sda2, thereby (in my naive brain, anyway) not having to make a filesystem on sda6? Further, why would you not make the whole drive -- /dev/sda -- one filesystem? sda is too big ; you are obliged to make a partition on it. If you consider an usb stick, if it is a litte one, it will be on sdf (for instance) but if it is more thant 2GB (I'm not sure for the size) it will be on sdf1. I don't know why but it is so :-) So your disk sda must have one partition (or more). Another thing is that there seem to be several notions of a filesystem. From http://www.ibm.com/developerworks/linux/library/l-linux-filesystem/ I get this general definition: What is a file system? I'll start with an answer to the most basic question, the definition of a file system. A file system is an organization of data and metadata on a storage device. That's right but there's many possible organisations : fat16 (on floppies), fat32 (with old microsoft windows), ntfs with windows xp, vista, seven... linux use usually ext2/3/4 ; there's lot of other filesystems. The man page for mke2fs talks about making filesystems in disk partitions. So a filesystem in the general sense can contain one or more filesystems in the mke2fs sense, and it's not always clear to me (again, a newbie to this stuff) which one is being talked about. I suppose experience will take care of that. I don't really understand what you mean, sorry :-) Hope this can help but was I clear enough ? -- Ph. Delavalade -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
Philippe Delavalade wrote: Set up the partitions like this, using an ext4 filesystem: /dev/sda1 /boot 100M /dev/sda2 Extended Linux partition ~100G /dev/sda5 Linux swap 2G /dev/sda6 / ~98G This seems odd to me. Maybe I'm wrong but your swap seems too small for your 16GB of RAM Various people had various suggestions. Bruce suggested 2G, and gave me a link to an article that suggested somewhere between 0 and 32G. :-) and you told you have a Fedora on sdb2, so swap is certainly on that drive (i don't know about fedora but I can't imagine there's no swap on sdb). I want the LFS installation to be completely independent of the host system. I'm considering the host system merely as a vehicle to install LFS. The boot partition is not required ; Yes, but section 2.2.1.3 highly recommends it. you've already a boot partition or directory on sdb. What do you plane to put on your extended sda2 ? I don't know yet. This is mainly a learning expedition now. Also, I'm trying to stick as closely as possible to the LFS book. Bruce gets testy if you don't do that, you see. :-) Following the lfs book, you just need one partition ; you can have a /usr partition if you like and a var one and a tmp one, etc. It's your first built and, maybe I'm wrong, but you'll certainly not work with lfs for this first time, perhaps later... You mean I'm going to do all this more than once? :-) As to me, I built lfs many times but I never continue whith blfs ; debian is my work system ; lfs is just to learn and undertand more deeply a lot of things. I see. Well, I'm too ignorant yet to know what I'll end up doing. But I'm with you on the learning part. That's why I'm doing this. Use mke2fs -t ext4 to create filesystems on /dev/sda1 and /dev/sda6. Ext4 seems inapropriate for your little boot partition. IMHO use ext2. The LFS book suggests ext3 and some people today have suggested ext4. I should NOT use mke2fs to create filesystems on /dev/sda2 and /dev/sda5. I don't fully understand why not, though. Can someone explain? On the swap partition, you'll don't write anything ; this partition is used by the system as a memory when your ram is unsufficient. Ok. So is swap not considered a filesystem by convention, or for some other reason? Under the above scheme, the extended linux partition CONTAINS the swap and / logical partitions, so it seems reasonable that you would not use mke2fs both on it, and on the partitions it contains, right? sda2 doesn't contain0 sda5 and sda6. You've misunderstood something (or it's me :-) ). I'm probably using the wrong terminology, but I meant contain in the sense that fdisk displays the sector numbers of sda5 and sda6 as inside the sector numbers of sda2. And why would you not make a filesystem on sda2, thereby (in my naive brain, anyway) not having to make a filesystem on sda6? Further, why would you not make the whole drive -- /dev/sda -- one filesystem? sda is too big ; you are obliged to make a partition on it. Too big? The drive I'm going to use here is a new 3TB one I bought on sale a few days ago. The SSD I was using until now is 256GB. And no matter how big a drive is, you still have to make one or more partitions on it, right? Or are you thinking in terms of making partitions of, say, 100GB each for different spins of various distros and LFS? If you consider an usb stick, if it is a litte one, it will be on sdf (for instance) but if it is more thant 2GB (I'm not sure for the size) it will be on sdf1. I don't know why but it is so :-) I've never used a usb stick in a linux system. But what you describe sounds a bit odd. The man page for mke2fs talks about making filesystems in disk partitions. So a filesystem in the general sense can contain one or more filesystems in the mke2fs sense, and it's not always clear to me (again, a newbie to this stuff) which one is being talked about. I suppose experience will take care of that. I don't really understand what you mean, sorry :-) The IBM article defined a filesystem as an organized set of data. That's a very general definition. That's quite different from the very specific notion of a filesystem as used in the mke2fs man page. Hope this can help but was I clear enough ? You've helped a lot, thank you very much! Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
I didn't think about that. It's been years since I've done this in Windows. Technically true and you said it better. But you wouldn't format it. - Original Message - From: Bruce Dubbs bruce.du...@gmail.com To: LFS Support List lfs-support@linuxfromscratch.org Sent: Monday, November 5, 2012 1:49:20 PM Subject: Re: [lfs-support] What Is The LFS Partition? dennisjperk...@comcast.net wrote: Partitions and filesystems are not identical on Linux/Unix systems. You carve a drive up into partitions, and you are free to format each partition with whatever filesystem you want. Every other operating system I am aware of does not make this distinction. Not true. Windows has FAT and NTFS. sda2 is not really a partition. It contains the extended partitions. In your case, sda5 and sda6. Actually an extended partition is a partition, but it has sub-partitions. All this stuff is avoided with a GUID Partition Table (GPT) which is a lot more sane in the world of large disk drives. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] What Is The LFS Partition?
On Mon, Nov 05, 2012 at 10:11:15PM +, Feuerbacher, Alan wrote: Philippe Delavalade wrote: sda is too big ; you are obliged to make a partition on it. Too big? The drive I'm going to use here is a new 3TB one I bought on sale a few days ago. The SSD I was using until now is 256GB. And no matter how big a drive is, you still have to make one or more partitions on it, right? I'm not sure that I agree with Philippe on this point, but it is certainly conventional to use at least one partition. Or are you thinking in terms of making partitions of, say, 100GB each for different spins of various distros and LFS? That seems excessively large, unless you intend to replicate your *data* into each distro. Sharing /home across _distros_ can get interesting (different groups and UIDs) but has to be a better way to go. For LFS, of course, you can easily change the UIDs and group numbers to match one host distro. Even at 100GB, you probably want to use ext4 (if using one of the ext fs's) to speed up the inevitable fscks. I suggest you google for something like ext2 ext3 ext4 comparison to get a better idea of the differences between them. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Not set up to use the correct startfiles at the 6.17 sanity check
This is my second LFS build, but it's been a while. This time I'm
trying to build with Package Users as described in this hint:
http://www.linuxfromscratch.org/hints/downloads/files/more_control_and_pkg_man.txt
For the sanity check at 6.17
http://www.linuxfromscratch.org/lfs/view/stable/chapter06/gcc.html,
I get the correct program interpreter ([Requesting program
interpreter: /lib64/ld-linux-x86-64.so.2]), but
grep -o '/usr/lib.*/crt[1in].*succeeded' dummy.log
yeilds no output, which means I'm apparently not set up to use the
correct startfiles. My dummy.log is located here:
http://sprunge.us/dcfi
Suprisingly, I have all the /usr/lib{,64}/*crt* files though:
http://sprunge.us/edEL
What can I do to debug/fix this?
-- Harry Prevor
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
[lfs-support] LFS Problem Section 5.4 Version 7.2
Hi there! When I try to prepare Binutils for configuration on the first pass (section 5.4.1) I get this strange error that prohibits me from making it later 1. lfs@mint /mnt/lfs/sources/binutils-2.22 $ ../binutils-2.22/configure --prefix=/tools --with-sysroot=$LFS --with-lib-path=/tools/lib --target=$LFS_TGT --disable-nls --disable-werror 2. checking build system type... i686-pc-linux-gnu 3. checking host system type... i686-pc-linux-gnu 4. checking target system type... i686-pc-linux-gnu 5. checking for a BSD-compatible install... /usr/bin/install -c 6. checking whether ln works... yes 7. checking whether ln -s works... yes 8. checking for a sed that does not truncate output... /bin/sed 9. checking for gawk... gawk 10. checking for gcc... gcc 11. checking for C compiler default output file name... 12. configure: error: in `/mnt/lfs/sources/binutils-2.22': 13. configure: error: C compiler cannot create executables 14. See `config.log' for more details. I got the config.log file, however all I saw was gcc a gcc problem. I also did the bash version check 1. 2. lfs@mint /mnt/lfs/sources/binutils-build $ bash version-check.sh 3. bash, version 4.2.24(1)-release 4. /bin/sh - /bin/dash 5. Binutils: (GNU Binutils for Ubuntu) 2.22 6. bison (GNU Bison) 2.5 7. /usr/bin/yacc - /usr/bin/bison.yacc 8. bzip2, Version 1.0.6, 6-Sept-2010. 9. Coreutils: 8.13 10. diff (GNU diffutils) 3.2 11. find (GNU findutils) 4.4.2 12. GNU Awk 3.1.8 13. /usr/bin/awk - /usr/bin/gawk 14. gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 15. (Ubuntu EGLIBC 2.15-0ubuntu10.3) 2.15 16. grep (GNU grep) 2.10 17. gzip 1.4 18. Linux version 3.2.0-23-generic (buildd@palmer) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #36-Ubuntu SMP Tue Apr 10 20:41:14 UTC 2012 19. m4 (GNU M4) 1.4.16 20. GNU Make 3.81 21. patch 2.6.1 22. Perl version='5.14.2'; 23. GNU sed version 4.2.1 24. tar (GNU tar) 1.26 25. version-check.sh: line 30: makeinfo: command not found 26. Texinfo: 27. xz (XZ Utils) 5.1.0alpha 28. gcc: error trying to exec 'cc1': execvp: No such file or directory 29. gcc compilation failed It seems to be a gcc problem, however, it is installed. I am using Mint 13 Cinnamon as my host computer. Any ideas as to what I need to do to fix this problem? Thanks-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS Problem Section 5.4 Version 7.2
Mark Mark wrote: I got the config.log file, however all I saw was gcc a gcc problem. Ialso did the bash version check 1. 2. lfs@mint /mnt/lfs/sources/binutils-build $ bash version-check.sh 3. bash, version 4.2.24(1)-release 4. /bin/sh - /bin/dash Needs to be bash 5. Binutils: (GNU Binutils for Ubuntu) 2.22 6. bison (GNU Bison) 2.5 7. /usr/bin/yacc - /usr/bin/bison.yacc 8. bzip2, Version 1.0.6, 6-Sept-2010. 9. Coreutils: 8.13 10. diff (GNU diffutils) 3.2 11. find (GNU findutils) 4.4.2 12. GNU Awk 3.1.8 13. /usr/bin/awk - /usr/bin/gawk 14. gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 15. (Ubuntu EGLIBC 2.15-0ubuntu10.3) 2.15 16. grep (GNU grep) 2.10 17. gzip 1.4 18. Linux version 3.2.0-23-generic (buildd@palmer) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #36-Ubuntu SMP Tue Apr 10 20:41:14 UTC 2012 19. m4 (GNU M4) 1.4.16 20. GNU Make 3.81 21. patch 2.6.1 22. Perl version='5.14.2'; 23. GNU sed version 4.2.1 24. tar (GNU tar) 1.26 25. version-check.sh: line 30: makeinfo: command not found Needs the texinfo package 26. Texinfo: 27. xz (XZ Utils) 5.1.0alpha 28. gcc: error trying to exec 'cc1': execvp: No such file or directory 29. gcc compilation failed It appears that gcc is not installed. It seems to be a gcc problem, however, it is installed. I am using Mint 13 Cinnamon as my host computer. Any ideas as to what I need to do to fix this problem? What makes you think gcc is installed? I don't know how mint handles packages, but The three above need to be installed. For gcc Google says: sudo apt-get install gcc g++ autoconf automake bison flex libtool You probably want to add bash and texinfo to that. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS Problem Section 5.4 Version 7.2
On Mon, Nov 05, 2012 at 07:33:06PM -0800, Mark Mark wrote: Hi there! When I try to prepare Binutils for configuration on the first pass (section 5.4.1) I get this strange error that prohibits me from making it later Please don't number the lines or insert a tab in front of them - it wastes space. It's perfectly acceptable to paste a block of lines, which will be easier for you if you are using a mouse. 13. configure: error: C compiler cannot create executables 14. See `config.log' for more details. I got the config.log file, however all I saw was gcc a gcc problem. I was going to point out that if configure reports the C compiler cannot create executables (on a linux system) it seems pretty likely that gcc is involved, and I was going to ask for details of the error message immediately before this when configure tried to compile the code fragment and failed. But on balance I think you have answered this below. I also did the bash version check 3. bash, version 4.2.24(1)-release 4. /bin/sh - /bin/dash /bin/sh should be symlinked to /bin/bash : dash is unlikely to be good enough. 25. version-check.sh: line 30: makeinfo: command not found 26. Texinfo: That doesn't look like a useful version of texinfo, does it ? 27. xz (XZ Utils) 5.1.0alpha 28. gcc: error trying to exec 'cc1': execvp: No such file or directory 29. gcc compilation failed You appear to be missing 'cc1'. apt-get install build-essential. $DEITY knows why ubuntu package things like this (a compiler, but not able to compile!). ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS Problem Section 5.4 Version 7.2
On Mon, Nov 05, 2012 at 10:02:06PM -0600, Bruce Dubbs wrote: 28. gcc: error trying to exec 'cc1': execvp: No such file or directory 29. gcc compilation failed It appears that gcc is not installed. It seems to be a gcc problem, however, it is installed. I am using Mint 13 Cinnamon as my host computer. Any ideas as to what I need to do to fix this problem? What makes you think gcc is installed? There are enough examples of this on google to suggest that ubuntu mispackaged gcc, or even broke their packaging during gcc-4.4 - it seems to be fairly common that ubuntu users end up with gcc but without cc1 ! ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Not set up to use the correct startfiles at the 6.17 sanity check
On 11/05/2012 09:10 PM, Harry Prevor wrote:
This is my second LFS build, but it's been a while. This time I'm
trying to build with Package Users as described in this hint:
http://www.linuxfromscratch.org/hints/downloads/files/more_control_and_pkg_man.txt
For the sanity check at 6.17
http://www.linuxfromscratch.org/lfs/view/stable/chapter06/gcc.html,
I get the correct program interpreter ([Requesting program
interpreter: /lib64/ld-linux-x86-64.so.2]), but
grep -o '/usr/lib.*/crt[1in].*succeeded' dummy.log
yeilds no output, which means I'm apparently not set up to use the
correct startfiles. My dummy.log is located here:
http://sprunge.us/dcfi
I see a number of suspect lines in there. In particular, a bunch that
look like:
COMPILER_PATH=/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.1/:/bin/../lib/gcc/
LIBRARY_PATH=/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.1/:/bin/../lib/gcc/:/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.1/../../../../lib64/:/lib/../lib64/:/usr/lib/../lib64/:/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.1/../../../:/lib/:/usr/lib/
And similarly...
attempt to open /bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.1/crtend.o
succeeded
I see numerous similar lines in your output - basically, it appears to
be looking in /bin and /lib for gcc files, rather than /usr/{bin,lib}.
Does ls /lib/gcc give any output? Also, did you deviate from the
book's instructions in any way other than adding Package User commands?
Even if you did not do so deliberately, you might want to go back
through your command history to verify what you actually typed vs.
what's in the book.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
