Re: [lfs-support] gcc-4.9.0 changes
Le 24/04/2014 17:28, Frans de Boer a écrit : Ok, followed the advises from ticket #3552, now binutils chapter 6 reports failures: Running /sources-bss/binutils-2.24/ld/testsuite/ld-plugin/lto.exp ... FAIL: PR ld/12758 FAIL: PR ld/12760 FAIL: LTO 3 symbol FAIL: PR ld/13183 FAIL: LTO 3a FAIL: LTO 11 Running /sources-bss/binutils-2.24/ld/testsuite/ld-plugin/plugin.exp ... Concerning LTO, thus induced by gcc-4.9.0. Chapter 5 is completed without any errors, added --disable-werror to the binutils configure...Seems that others having no problem, so what could be wrong? Frans. I have exactly the same failures. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] ACL check errors: are they important?
Le 22/04/2014 13:31, Hazel Russman a écrit : On Mon, 21 Apr 2014 22:14:31 +0100 Ken Moffat zarniwh...@ntlworld.com wrote: From memory (so, I might be wrong) the book doesn't ever create a 'users' group in LFS... So, I _guess_ that the 'users' group exists on your host system and you will need to create it in LFS to get these tests to work. ĸen You're right. I do have a users group on my host system. But how does that affect the lfs partition? At this stage, we are in a chroot jail, using freshly-built software. Doesn't that mean complete independence from the host except for the running kernel and its virtual file systems? There would have been no previous need for a users group or a daemon user on LFS because acl was not included in the basic system and therefore there were no acl tests to be run. That must still be the case for LFS with sysVinit. But acl is apparently required for systemd, so I think it would make sense for section 6.6 to be different in the systemd edition of the book. I filed a ticket about that. It seems that the bin group membership of the daemon user is not needed. Could you confirm? Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] ACL check errors: are they important?
Le 22/04/2014 17:51, Hazel Russman a écrit : On Tue, 22 Apr 2014 13:42:58 +0200 Pierre Labastie pierre.labas...@neuf.fr wrote: It seems that the bin group membership of the daemon user is not needed. Could you confirm? Confirmed. It is also not necessary to set real home directories or shells for the bin and daemon users as specified in BLFS. /dev/null and /bin/false work perfectly well for these. Hazel Thanks for checking. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] kmod-17
Le 21/04/2014 17:50, TheOldFellow a écrit : Linux From Scratch - Version SVN-20140418 Everything fine, including installation of xz, but kmod-17 clearly isn't happy with the layout of the libs for xz. root:/sources/kmod-17# make make --no-print-directory all-recursive Making all in . CC libkmod/libkmod.lo CC libkmod/libkmod-list.lo CC libkmod/libkmod-config.lo CC libkmod/libkmod-index.lo CC libkmod/libkmod-module.lo CC libkmod/libkmod-file.lo CC libkmod/libkmod-elf.lo CC libkmod/libkmod-signature.lo CC libkmod/libkmod-hash.lo CC libkmod/libkmod-array.lo CC libkmod/libkmod-util.lo CCLD libkmod/libkmod-util.la CCLD libkmod/libkmod.la /usr/lib/liblzma.so: file not recognized: Is a directory collect2: error: ld returned 1 exit status Makefile:1211: recipe for target 'libkmod/libkmod.la' failed make[2]: *** [libkmod/libkmod.la] Error 1 Makefile:1803: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 Makefile:1030: recipe for target 'all' failed make: *** [all] Error 2 I've probably done something wrong:( Richard. what does ls -l /usr/lib/lilzma.so return ? (should be a link to ../lib/liblzma.so.xxx, where xxx is the version number). If it is not a link or a link to something which is not a library, you'd better go back to the last line of Xz installation. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] ACL check errors: are they important?
Le 21/04/2014 18:13, Hazel Russman a écrit : I am building a 7.5 LFS with systemd and currently working through chapter 6. Having successfully installed coreutils, I rebuilt acl and ran the test suite. Initially I got 47 errors! According to BLFS, the acl test suite requires a daemon user who is also in the bin group (currently section 6.6 of LFS-systemd does not include this user in /etc/passwd). Adding it reduced the number of errors from 47 to 10. However I have not been able to reduce them any further. BLFS also recommends giving bin and daemon proper home directories (I used /bin and /sbin respectively) and a shell, but this had no effect in my case. As far as I know, the acl and user_xattr options required for acl to work on the mounted lfs partition are built into the ext4 driver that my host kernel (3.10.17) uses and do not need to be set explicitly. When I do set them, they are accepted silently but don't show up in /proc/mounts, whereas noacl and nouser_xattr do. I attach an edited log file containing the actual test errors. I need to know if they are important and, if so, how to get rid of them. You do not say that you have mounted your filesystem with acl and user_xattr. Those options must be specified when mounting the lfs partition, possibly in the fstab... Distributions usually do not do that by default. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] ACL check errors: are they important?
Le 21/04/2014 18:13, Hazel Russman a écrit : I am building a 7.5 LFS with systemd and currently working through chapter 6. Having successfully installed coreutils, I rebuilt acl and ran the test suite. Initially I got 47 errors! According to BLFS, the acl test suite requires a daemon user who is also in the bin group (currently section 6.6 of LFS-systemd does not include this user in /etc/passwd). Adding it reduced the number of errors from 47 to 10. However I have not been able to reduce them any further. BLFS also recommends giving bin and daemon proper home directories (I used /bin and /sbin respectively) and a shell, but this had no effect in my case. As far as I know, the acl and user_xattr options required for acl to work on the mounted lfs partition are built into the ext4 driver that my host kernel (3.10.17) uses and do not need to be set explicitly. When I do set them, they are accepted silently but don't show up in /proc/mounts, whereas noacl and nouser_xattr do. I attach an edited log file containing the actual test errors. I need to know if they are important and, if so, how to get rid of them. Looking more closely at your log, it seems that acl's are enabled, because the line beginning with [95]: 'getfacl --omit-header f' correctly returns acl entries: user::rw- user:bin:rw- user:daemon:r-- Actually, the line beginning with [91], which returns the first error, seems to choke on g:users:rw. Do you have a users group in /etc:group? Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] ACL check errors: are they important?
Le 21/04/2014 19:25, Pierre Labastie a écrit : Le 21/04/2014 18:13, Hazel Russman a écrit : I am building a 7.5 LFS with systemd and currently working through chapter 6. Having successfully installed coreutils, I rebuilt acl and ran the test suite. Initially I got 47 errors! According to BLFS, the acl test suite requires a daemon user who is also in the bin group (currently section 6.6 of LFS-systemd does not include this user in /etc/passwd). Adding it reduced the number of errors from 47 to 10. However I have not been able to reduce them any further. BLFS also recommends giving bin and daemon proper home directories (I used /bin and /sbin respectively) and a shell, but this had no effect in my case. As far as I know, the acl and user_xattr options required for acl to work on the mounted lfs partition are built into the ext4 driver that my host kernel (3.10.17) uses and do not need to be set explicitly. When I do set them, they are accepted silently but don't show up in /proc/mounts, whereas noacl and nouser_xattr do. I attach an edited log file containing the actual test errors. I need to know if they are important and, if so, how to get rid of them. Looking more closely at your log, it seems that acl's are enabled, because the line beginning with [95]: 'getfacl --omit-header f' correctly returns acl entries: user::rw- user:bin:rw- user:daemon:r-- Actually, the line beginning with [91], which returns the first error, seems to choke on g:users:rw. Do you have a users group in /etc:group? Pierre s@/etc:group@/etc/group@ sorry. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] kmod-17
Le 21/04/2014 19:01, TheOldFellow a écrit : Pierre Indeed this is where the problem lies. ls -l /usr/lib/liblzma.so lrwxrwxrwx 1 root root 10 Apr 21 16:19 /usr/lib/liblzma.so - ../../lib/ However the real problem is in the last line of the xz installation, as you rightly say, because: $(readlink /usr/lib/liblzma.so) returns ../../lib/ but it is bash-script that is beyond me. Yes If the link is wrong, readlink returne a wrong link. Sometimes computers are coherent... With Xz-5.0.5, the link should be to ../../lib/liblzma.so.5.0.5 Creating it should save you an xz reinstall. I do not know whether the packages between Xz and kmod should be recompiled, though. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] error when trying to cross compile glibc-2.19
Le 19/04/2014 07:42, mar...@byteanywhere.com a écrit : I have a symlink between: ls -ld /tools lrwxrwxrwx 1 root root 47 Apr 17 08:08 /tools - /home/marian/crosstool/x86_64-unknown-linux-gnu/ export PREFIX=/home/marian/crosstool/x86_64-unknown-linux-gnu export TARGET=x86_64-unknown-linux-gnu export SYSROOT=/home/marian/crosstool/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sys-root export PATH=/tools/bin:/bin:/usr/bin I think there are at least 2 problems in the above: 1) TARGET=x86_64-unknown-linux-gnu: you have not told what your host is, but I assume it is a 64 bit PC running linux. In this case, the host is already x86_64-unknown-linux-gnu, so the build systems of binutils and gcc do not understand that you want to create a cross compiler. As explained in LFS page 5.2, you need to slightly deviate from that by changing the vendor name from unknown to something else. Of course, if your host is not a 64 bit PC, the preceding does not apply. 2) SYSROOT=/home/marian/crosstool/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sys-root SYSROOT is the _root_ of the new system disk image, where the linker will look for the target libraries. Using --with-sysroot=$SYSROOT --with-lib-path=/tools/lib below means that the linker will look into $SYSROOT/tools/lib for target libraries. Clearly, those directories do not exist. What I would recommend is to use the LFS section 4.4 setup. If you do not want to do that, you should at least have: PREFIX=/whatever/tools SYSROOT=/whatever ln -s /whatever/tools / 1. Binutils ../binutils-2.24/configure --prefix=/tools --with-sysroot=$SYSROOT --with-lib-path=/tools/lib --target=$TARGET --disable-nls --disable-werror binutils compiles fine. no errors. 2. Kernel headers make headers_check make INSTALL_HDR_PATH=dest headers_install cp -rv dest/include/* /tools/include 3. From some other docs i saw they install the glibc headers as well here. I have tried this, but the same error is happening when building gcc or glibc. System glibc headers mkdir glibc-build cd glibc-build ../glibc-2.19/configure --prefix=/tools --host=$TARGET --build=$(../glibc-2.19/scripts/config.guess) --disable-profile --enable-kernel=2.6.32 --with-headers=/tools/include libc_cv_forced_unwind=yes libc_cv_ctors_header=yes libc_cv_c_cleanup=yes --without-selinux make -k install-headers install_root=/ That's a very bad idea, you have overwritten your host headers, unless you did not run this command as user root, in which case you have done nothing... You should have seen errors, though. This step is not needed anyway. 4. GCC stage 1 ../gcc-4.8.2/configure --target=$TARGET --prefix=/tools --with-sysroot=$SYSROOT --with-newlib --without-headers --with-local-prefix=/tools --with-native-system-header-dir=/tools/include --disable-nls --disable-shared --disable-multilib --disable-decimal-float --disable-threads --disable-libatomic --disable-libgomp --disable-libitm --disable-libmudflap --disable-libquadmath --disable-libsanitizer --disable-libssp --disable-libstdc++-v3 --enable-languages=c,c++ --with-mpfr-include=$(pwd)/../gcc-4.8.2/mpfr/src --with-mpfr-lib=$(pwd)/mpfr/src/.libs Did you run the for file in [...] done part? Here if i use make, i get the same error, that compiler can not create executables. From config log, the error is that cross gcc is not able to find a couple of libs (which seems generated by glibc) crt1.o, crti.o, crtn.o and libc.so Those are not found by the linker because it looks for them in $SYSROOT/tools/lib/somepath, which does not exist. Also, the compiler thinks it is a native compiler if the TARGET is not different from the host, and the algorithm to find the files is different. Thus from other docs i have seen these being used, so i have tried to continue using them: make all-gcc make all-target-libgcc make install-gcc make install-target-libgcc You should be able to run just make. 5. building glibc fails building in sunrpc folder, for some rpc_* files, with the same same error, saying that those libs can not be found. See what happens when you correct the errors above (TARGET and SYSROOT, I think). Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Brand new and confused. Mostly about the 7.5 book.
Le 30/03/2014 23:05, Al Szymanski a écrit : I am just trying to figure out the overall smallest size of hard drive space needed for all of the partitions. My sums from the 7.5 book come to 80 Gig plus whatever space I want for /home . [ suggested partition sizes: root LFS 10Gig/usr/src 30-50Gig /opt 5-10Gig /usr 5Gig /tmp 5Gig swap 2xRAM /boot 100Meg =~81Gig ] The online version of the book says, A minimal system requires a partition of around 2.8 gigabytes (GB). in 2.2 . I've 30Gig available on the host system, and have a 30 Gig drive that I was planning on using to start my LFS system, but now think that I can not get what's needed on a small drive. So... how small a drive can I do LFS with? Thanks and I hope to not be a bother in the future. Al If you just want to build LFS: 100 Mb /boot 10 Gb / (actually 5-6 Gb could be enough) (or you may split this into several partitions, but the overall size si largely enough) 4 Gb swap (almost never used if you have more than 2 Gb of memory) So 30 Gb is more than enough. If you want to build the whole of BLFS: maybe / (if you use only one partition) should be closer to 20 Gb. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Qca-2.0.3 Qca-2.0.3
Le 28/03/2014 17:31, Bruce Dubbs a écrit : Fernando de Oliveira wrote: Em 28-03-2014 02:56, m...@pc-networking-services.com escreveu: Hello again, same thing in qca: ./configure --prefix=$QTDIR should be: ./configure --prefix=$QT4DIR \ Fixed in svn at r12901. Thanks. This, I changed in Qt4 page in the last days of the package freeze, IIRC, but did not really knew there was an entity in general.ent that needed to be modified. This fixes all other you reported and some more. Perhaps an entry in the errata for BLFS-7.5 would be necessary, Bruce or Pierre? OK, I'll take care of it. -- Bruce I think I've seen a couple of other things, which could go the the errata: - gtk+3 as a dependency of openjdk should be gtk+2 - tell either that nss is recommended for openjdk, or to suppress the --enable-nss switch (we chose the first in the development book) - (minor) tell that the rm command in xorg-fonts should begin with as_root Regards, Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] lsmod return nothing
Le 22/03/2014 01:23, 包乾 a écrit : hi all! Its been alot of effort and I finally got my LFS 7.4 successfully boot on my thinkpad X40. The first problem I encountered was that during the boot process it displayed face eth0 doesn't exist. Well its a typical error msg with driver problem. So I went back to host system, figured out which kernel module my NIC use( I found it was e1000.ko, a intel NIC driver). Then I go back into LFS, re-configure and re-make the kernel, re-install all thing include modules. And weird thing happened. I tried to modprobe e1000, it return nothing, just like successfully loaded. But when I double-check lsmod, there is actually NOTHING there-no module was loaded. I wonder if I screwed sth. up during the build process or there is other problem... Plz help! Did you build e1000 as a module or in the kernel? In the latter case, it is normal that modprobe says nothing and that you cannot see e1000 as a loaded module. You can check with: grep E1000= /boot/config-... (the config file saved in /boot after building the kernel). If you get: CONFIG_E1000=y, it is not built as module, but embedded in the kernel. CONFIG_E1000=m, it is built as module. CONFIG_E1000=n, it is not built at all. Now, coming to the issue you have, it may also be that eth0 is renamed to something else. What does 'ip link list' return on the booted system? Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] How can I fix the following errors which happen after extracting linux 3.10.10 package (chapter 8)
Le 27/02/2014 08:14, Bruce Dubbs a écrit : Yonas Zed wrote: i follow the instraction on LFS 7.4 to build my own distro using ubuntu 12.4,32 bits ...i run the ubuntu on vmware 9 by allocationg 42GB space for storage and 2GB memory ...core-i7 2.20GHz processor...is there a different installation process for 32 and 64 bit? or different linux 3.10.10 for 32 and 64 bits?.. You seem to be hijacking the thread. Your comments don't match the subject. That said, if you use a 32-bit host, you will get a 32-bit LFS. If you use a 64-bit host, you get a 64-bit LFS. Running in vmware does not make a lot of difference outside of the kernel configuration. Coming to the kernel configuration, There could be an explanation. I understand you used an Unbuntu 32 bit distribution on a virtual machine with 64 bit CPU. Doing that, as Bruce says, you get a 32 bit LFS. But the kernel configuration system may have seen the 64 bit CPU, and I think that is the source of the problem (from your original post): - kernel/bounds.c:1:0: sorry, unimplemented: 64-bit mode not compiled in make[1]: *** [kernel/bounds.s] Error 1 make: *** [prepare0] Error 2 - Can you check that 64-bit kernel is not ticked when making the configuration of the kernel? Also, if you have run make defconfig, try instead make i386_defconfig. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] How can I fix the following errors which happen after extracting linux 3.10.10 package (chapter 8)
Le 26/02/2014 08:33, Yonas Zed a écrit : root:/sources/linux-3.10.10# make make modules_install HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_64.h SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_x32.h SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_32.h SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_32_ia32.h SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_64_x32.h SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_64.h HOSTCC arch/x86/tools/relocs_32.o HOSTCC arch/x86/tools/relocs_64.o HOSTCC arch/x86/tools/relocs_common.o HOSTLD arch/x86/tools/relocs WRAParch/x86/include/generated/asm/clkdev.h CHK include/generated/uapi/linux/version.h UPD include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h UPD include/generated/utsrelease.h CC kernel/bounds.s kernel/bounds.c:1:0: error: code model 'kernel' not supported in the 32 bit mode /* ^ kernel/bounds.c:1:0: sorry, unimplemented: 64-bit mode not compiled in make[1]: *** [kernel/bounds.s] Error 1 make: *** [prepare0] Error 2 You do not say anything about configuring the kernel. What did you do for that? Also, what is your hardware (processor type)? Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] creating binutils-build again
Le 23/02/2014 09:26, Waitman Gobble a écrit : Hi, Version 7.5-rc1 In 5.5. GCC-4.8.2 - Pass 1, the book reads mkdir -v ../binutils-build, then in 5.9. Binutils-2.24 - Pass 2, the book reads Create a separate build directory again: mkdir -v ../binutils-build. There is confusion about whether the binutils-build directory created in pass 1 should be removed before pass 2, or if it's OK to do pass 2 with the existing binutils-build from pass 1. Thank you, Hmm, You should delete the extracted source directory and any package-build directories, as written on page 5.3 General Compilation Instructions, last item... Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] DHCPCD not starting when booting up
Le 20/02/2014 18:04, Oshadha Gunawardena a écrit : root:/# cat /etc/inittab # Begin /etc/inittab id:3:initdefault: si::sysinit:/etc/rc.d/init.d/rc S l0:0:wait:/etc/rc.d/init.d/rc 0 l1:S1:wait:/etc/rc.d/init.d/rc 1 l2:2:wait:/etc/rc.d/init.d/rc 2 l3:3:wait:/etc/rc.d/init.d/rc 3 l4:4:wait:/etc/rc.d/init.d/rc 4 l5:5:wait:/etc/rc.d/init.d/rc 5 l6:6:wait:/etc/rc.d/init.d/rc 6 ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now su:S016:once:/sbin/sulogin 1:2345:respawn:/sbin/agetty 2:2345:respawn:/sbin/agetty 3:2345:respawn:/sbin/agetty 4:2345:respawn:/sbin/agetty 5:2345:respawn:/sbin/agetty 6:2345:respawn:/sbin/agetty --noclear tty1 9600 tty2 9600 tty3 9600 tty4 9600 tty5 9600 tty6 9600 # End /etc/inittab It may happen that the mailer has broken lines, but the end of the above file is weird. It should be: 1:2345:respawn:/sbin/agetty --noclear tty1 9600 2:2345:respawn:/sbin/agetty tty2 9600 3:2345:respawn:/sbin/agetty tty3 9600 4:2345:respawn:/sbin/agetty tty4 9600 5:2345:respawn:/sbin/agetty tty5 9600 6:2345:respawn:/sbin/agetty tty6 9600 Do not know exactly how it would interact with the boot process. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] DHCPCD not starting when booting up
Le 19/02/2014 04:38, Oshadha Gunawardena a écrit : @Bruce It's strange I checked the address and it's correct. Furthermore all the other files are seems to be in place. But then why the dhcpcd isn't starting automatically? I'm thinking of writing a start-up script to solve this issue. Sorry forgot to tell: Yesterday, I built dhcpcd and installed the scripts (on a virtual machine). Everything worked. I know that it works for me is not very helpful, but it shows that the scripts and the current build instructions produce a working installation in some cases. Do you have changed the runlevel with respect to what is in the book? I think network is not started in single runlevel, and maybe in others. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] DHCPCD not starting when booting up
Le 18/02/2014 16:26, Oshadha Gunawardena a écrit : Hi again all, I have completed my LFS build. And I wanted to install dhcpcd. So as in the BLFS I have followed every step and it seems everything went well *make install-service-dhcpcd* install -d -m 755 /lib/services install -m 754 blfs/services/dhcpcd /lib/services *cat /etc/sysconfig/ifconfig.eth0 * ONBOOT=yes IFACE=eth0 SERVICE=dhcpcd DHCP_START=-b -q DHCP_STOP=-k Once I boot in to the system it does not starting up automatically. I always has to run the dhcpcd to get it up. So I'm wondering what maybe the issue. Just guessing here. Do you have any other file beginning with ifconfig in /etc/sysconfig? If there is one, does it have ONBOOT=no? Now coming to dhcpcd. Does it start when running: --- ifup eth0 --- instead of dhcpcd? Regards Pierre -- 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 building problems
Le 11/02/2014 10:59, jer...@yahoo.com a écrit : And by source you mean the dirs containing the unpacked packages? Is this information missing in the book or have I missed it? See for example 5.3 General Compilation Instructions last item. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error while configuring File-5.14
Le 23/01/2014 07:30, Sneha Joshi a écrit : I am refering LFS 7.4 on centos6.3 (i686) ERRROR : checking for gcc... gcc checking whether the C compiler works... no configure: error: in `/mnt/lfs/sources/file-5.14': configure: error: C compiler cannot create executables See `config.log' for more details In Config.log i am getting following error : configure:3824: gccconftest.c 5 /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/4.8.1/../../../../ i686-pc-linux-gnu/bin/ld: cannot find -lgcc_s collect2: error: ld returned 1 exit status please help me asap. Please could you tell us what page you are building? If you are building 'file' in chapter 5, it means you have been building a lot of other packages before, and that error did not show up, although the test checking whether the C compiler works is pretty standard. So, I think you exited the lfs user environment and forgot to set it back. What does the command env return? Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 5.8 Libstdc++-4.8.1
Le 17/01/2014 19:37, Louis Rine a écrit : I ran the build again after fixing /bin/sh to be a link to /bin/bash. I formatted the lfs partition and re-downloaded the sources before running the build again, but it occurred to me after the fact that I didn't delete the lfs programs from /tools/bin. So maybe that was dumb. ??? /tools is a link to $LFS/tools. If you formatted the partition, you deleted all files. If you still have files in /tools/bin, it may indicate you did not set the link properly. See page 4.2 of the book. The second instruction on this page is really important. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] GCC-$.8.1 Configure fatal errors
Le 16/01/2014 16:49, William Darryl Jackson a écrit : On 01/16/2014 10:46 AM, William Darryl Jackson wrote: Greetings, back in GCC-4.8.1 again section 5.5.1 - after re-reading everything I decided to do as suggested to try to find out why I am having so much difficulty with this 'make'. In the config.log I found the following fatal errors: Thread model: posix gcc version 4.7.2 (Debian 4.7.2-5) configure:4212: $? = 0 configure:4201: gcc -V 5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:4212: $? = 4 configure:4201: gcc -qversion 5 gcc: error: unrecognized command line option '-qversion' gcc: fatal error: no input files compilation terminated. It is also failing while checking for versions .10 and .11 of ISL: conftest.c:10:25: fatal error: isl/version.h: No such file or directory. After the the configure appears to complete successfully. Should I be concerned about either of these two failures? Hello William, The configure script tries a lot of things to guess the capabilities of the system. Sometimes, an error contains some informations that are usefull to determine those capabilities. For example, to test if a header file (say xxx.h) can be accessed, it runs gcc on a small C program, which contains a line: #include xxx.h Then, if gcc ends with an error, configure interprets it as xxx.h being not acessible, and may stop or not, depending whether xxx.h is required or not. Meanwhile, you'll see the error message of gcc, somthing like: cannot find xxx.h or whatever. It does not mean that configure found an error. So the outpur you see is not configure errors, but negative tests. You do not have to be worried about that. So, go ahead, and run make. Cross fingers Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Gcc-4.8.1 Section 5.5.1 - libmpfr
Le 16/01/2014 22:15, William Darryl Jackson a écrit : Greetings, My first pass of make produced the following error: checking for MPFR... no configure: error: libmpfr not found or uses a different ABI (including static vs shared). make[1]: *** [configure-mpc] Error 1 make[1]: Leaving directory `/mnt/lfs/sources/gcc-build' make: *** [all] Error 2 I have triple-checked my configure syntax. It seems you already reported that error on January 11th... Have you extracted and renamed gmp, mpfr and mpc to the source directory (/mnt/lfs/sources/gcc-4.8.1)? Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Glibc
Le 12/01/2014 22:37, William Darryl Jackson a écrit : Never mind, I just answered my own question. I remember Debian did not show Glibc as a package, and I loaded eglibc-source, but apparently it is not sufficient. Need to find Glibc-2.5.1 - maybe from another Debian repository, or compile and install it from elsewhere. This pertains to the 'make' error I just emailed in GCC-4.8.1. I will work it out. Take care, William You can use any version of glibc above 2.5.1, and 2.17 or 2.13 are OK. On debian, I have libc-dev-bin and libc6-dev, which should pull the needed dependencies. eglibc-source is useless for building LFS. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] GCC-4.8.1 Pass1 C++
Le 11/01/2014 09:35, William Darryl Jackson a écrit : Greetings: Having rebuilt from scratch, and being certain all steps were followed accurately - in the proper folder and environment; GCC 'make' is still giving me the following error: configure: error: C++ compiler missing or inoperational make[1]: *** [configure-libcpp] Error 1 make[1]: Leaving directory `/mnt/lfs/sources/gcc-build' make: *** [all] Error 2 Again, Binutils installed correctly. Any assistance would be greatly appreciated. William Hi William, Do you have C++ installed on the host? Maybe you could have a look at the vii. Host System requirements page in the preface. If you have some doubt, you may post the output of the version-check.sh script here. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] folder permissions
Le 11/01/2014 16:33, William Darryl Jackson a écrit : Now I find-out that g++ is not on my system, and thus c++. I install the program and decide to remove the ../gcc-build folder to reconfigure gcc from that point forward. I have switched back to the $lfs user but when I: mkdir -v ../gcc-build I find that I now do not have permission; permission denied. I checked the folder permissions - the owner is lfs, but the group is root. If I am the owner, why no permission? This is what got me turned around previously. This time I thought I would ask, why this occurs. Before I start making changes. Yes, I am doing an 'echo $LFS', regularly. What is the exact output of ls -ld $LFS/sources? I have: drwxrwxrwt 5 root root 36864 janv. 5 22:17 /mnt/lfs/sources So user lfs is not even the owner, but everybody has right to write, and there is the sticky bit (last t), which just means that a file belonging to some user cannot be removed or modified by another user. Now, there may be other reasons. Your system may use acl (access control lists), or selinux, which further restrict permissions. What is your host distribution? regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error in section 5.5.1 Cross GCC
Le 10/01/2014 22:40, William Darryl Jackson a écrit :
Greetings:
First I would like to state that I was able to successfully compile Binutils.
[...]
So I thought to put it in a script:
#!/bin/sh
for file in \
$(find gcc/config -name linux64.h -o -name linux.h -o -name sysv4.h)
do
cp -uv $file{,.orig}
sed -e 's@/lib\(64\)\?\(32\)\?/ld@/tools@g' \
-e 's@/usr@/tools@g,$file.orig $file
The comma in the line above should be replaced by a single quote ' followed by
a space.
echo '
[...]
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Berkeley-DB required to build a kernel
Le 31/12/2013 14:25, Pierre M.R. a écrit : Pierre M.R. wrote: Pierre Labastie wrote: I only see this error when I tick Build Adapter Firmware with kernel Build, but the help for this option says: This option should be enabled if you are modifying the firmware source of the aic7xxx driver and wish to have the generated firmware include files updated during a normal kenel build. The assembler for the firmware requires lex and yacc or their equivalent, as well as the db v1 library[...] Are you sure you need this option? Why not ? It's a comfort to have the firmwares you need (e100 and radeon in my case) installed together with the modules. Pierre Sorry, going through menuconfig again, I see this this option ticked under SCSI low-level drivers. Indeed, I don't need it. Pierre Yeah, forgot to say that it was inside the aic7xxx menu... Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Kernel file not found
Le 22/12/2013 09:02, Cliff McDiarmid a écrit :
- Original Message -
From: cont...@igor-zivkovic.from.hr
Sent: 12/21/13 09:05 PM
To: lfs-support@linuxfromscratch.org
Subject: Re: [lfs-support] Kernel file not found
On 12/21/2013 09:35 PM, Cliff McDiarmid wrote:
Hi
I've built LFS six times and never had this issue. After rebooting I'm
getting an error saying 'file /boot/lfskernel-3.12.5 not found'
My 'grub.cfg' file from the host system(also LFS)reads:
# Begin /boot/grub/grub.cfg
set default=0
set timeout=20
set root=(hd0,7)
menuentry LFS6, Linux 3.12.1-lfs-7.2 {
linux /boot/lfskernel-3.12.1 root=/dev/sda7 ro
}
menuentry LFS7, Linux 3.12.5-lfs-7.4 {
linux /boot/lfskernel-3.12.5 root=/dev/sda6 ro
}
How is this? Spelling is all correct in /boot. The host 'LFS6' boots fine.
You're missing set root=(hd0,6) for in the LFS7 menu entry.
--
Igor Živković
http://www.slashtime.net/
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Yes thanks that boots the new system okay but leaves lfs6unbootable . I.e no
file found. There must be some kind of syntax error here somewher.
Cliff
The set root instructions should be inside the brace:
menuentry LFS6, Linux 3.12.1-lfs-7.2 {
set root=(hd0,7)
linux /boot/lfskernel-3.12.1 root=/dev/sda7 ro
}
and same for the second one, replacing 7 with 6. Note that the root set by
set root does not need to be the same as the root= kernel parameter.
For example, you could have all the kernel files on the first partition and
have something like:
set root=(hd0,1)
linux /lfskernel-3.12.1 root=/dev/sda7 ro
(notice that /boot is suppressed in the last line). Then you could mount
/dev/sda1 on /boot with /etc/fstab.
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] 7.4 / 5.7. Glibc-2.18 / configure warning: autoconf not working
Le 02/12/2013 05:41, Ron Hartikka a écrit : Hi Group, I am just hoping for a confirmation that I'm doing ok here. I think I'm not supposed to need autoconf in chapter 5. But I'm being conservative (since I have failed to build LFS 5 times so far). Details below. Most important first. Go ahead, autoconf is not needed, and your host conf looks fine. Always make sure that .bashrc is run when you log in as user lfs. You might want to type: env before beginning to work, and check that LFS, LFS_TGT c, are set and have consistent values. Regards, Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Ethernet Card Not Found
Le 28/11/2013 10:48, akhiezer a écrit : I think the _prime_ example actually would be Slackware, in this and many other instances. Any prime example on an LFS mail list is LFS ;-) Sorry, couldn't refrain... Pierre -- 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 7.4 / Chapter 5.7 glibc compilation error
Le 26/11/2013 20:32, frozen tuesday a écrit : OK, my fault. I neglected to notice that 3 packages had not been installed: bison yacc m4 I have installed them and my version check script shows everything is installed. I am ready to try again. Can I simply issue the make command again or do I need to do something special to undo stuff that was done during the first run. I suggest you get back to the beginning (binutils). Missing those three packages completely changes the behavior of configure, so a lot of things can have gone wrong. I guess you do not need to install linux headers again, but definitely binutils, gcc and glibc. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Ethernet Card Not Found
Le 24/11/2013 19:24, David Kredba a écrit : Do you have pciutils installed? If not install it (you can use liveCD or what you used to do first installation and chroot inside your current system or download it and copy in if you have USB storage working etc.). Then start in single mode and post output of lspci -v. David 2013/11/24 Alan Feuerbacher alan...@comcast.net: On 11/24/2013 10:33 AM, Bruce Dubbs wrote: Alan Feuerbacher wrote: On 11/24/2013 12:19 AM, Bruce Dubbs wrote: Per Ken's suggestion, I added the ethernet driver for my Realtek ethernet device, recompiled the kernel, reinstalled systemd/udev from scratch. Still no luck. When linux starts, I see a message: Bringing up the eth0 interface... skipped When I try to bring up the network with ifup I get this: ifup eth0 ### Bringing up the eth0 interface... Adding IPv4 address 10.0.1.1 to the eth0 interface...Cannot find device eth0 * *face eth0 doesn't exist. ### Ok, then I must have missed something when building the system. What do I look for in the LFS book to build the right ethernet driver? Bring up a working system and run lsmod. I get this: lsmod ## Module SizeUsed by x86_pkg_temp_thermal45110 ## I think Bruce was talking about a working distribution (the one you used to build LFS for example). Boot it and run lsmod. The information you get there could indicate the right driver for the kernel. Before that and if you are still on LFS: ip link list If you see only lo and sit0, it means you do not have the good device driver in the kernel. If you see something like enp0s2, it means something is wrong with the udev files, but at least you can try to bring that interface up. Also, I see: Adding IPv4 address 10.0.1.1 to the eth0 interface Are you sure you want 10.0.1.1? Usually, the .1 address is that of the ethernet hub which connects your local network to the outside world. I'd try 10.0.1.9 (unless you have many computers on your local network, that address should be free...) Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error: invalid file name When Booting For the First Time
Le 23/11/2013 03:39, Alan Feuerbacher a écrit :
Having had no success this past week in getting an LFS system running under
UEFI booting with LVM volume management and GPT partitioning, I decided to
install a fresh copy of LFS on a new hard drive. I did my best to follow the
LFS book (development version) exactly, and this evening was able to try to
boot the new system. No success yet. I got this error message when Grub
came up:
error: invalid file name 'vmlinuz-3.12-lfs-SVN-20131105'
I don't know where things have gone south, so perhaps someone else can help
figure it out.
I have three 2TB hard drives running right now:
/dev/sda contains Fedora19
/dev/sdb contains the new LFS system
/dev/sdc contains the UEFI LFS system from last week
I installed Grub to /dev/sdb with this:
grub-install /dev/sdb
/boot is mounted on /dev/sdb1
Below are some listings of (I hope) all the relevant disk and boot
information.
Contents of /boot/grub/grub.cfg:
##
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd1,1)
menuentry GNU/Linux, Linux 3.12-lfs-SVN-20131105 {
linux vmlinuz-3.12-lfs-SVN-20131105 root=/dev/sdb1 ro
}
##
I was not sure whether the linux line should be:
linux vmlinuz-3.12-lfs-SVN-20131105 root=/dev/sdb1 ro
or this:
linux /vmlinuz-3.12-lfs-SVN-20131105 root=/dev/sdb1 ro
I tried both, and got the same invalid file name error.
Listing of /boot:
##
-rw-r--r-- 1 root root 86838 Nov 20 22:10 config-3.12
drwxr-xr-x 4 root root 4096 Nov 22 20:43 grub
drwx-- 2 root root 16384 Nov 18 05:27 lost+found
-rw--- 1 root root 881184 Nov 22 20:38 shellx64.efi
-rw--- 1 root root 881184 Nov 22 20:38 Shellx64.efi
-rw-r--r-- 1 root root 3166833 Nov 20 22:10 System.map-3.12
-rw-r--r-- 1 root root 6341328 Nov 22 20:39 vmlinuz-3.12
-rw-r--r-- 1 root root 6341328 Nov 22 20:39 vmlinuz-3.12-lfs
-rw-r--r-- 1 root root 6341328 Nov 20 22:09 vmlinuz-3.12-lfs-SVN-20131119
-rw-r--r-- 1 root root 6341328 Nov 22 20:40 vmlinuz-3.12-lfs.x86_64
##
Listing of /boot/grub:
##
-rw-r--r-- 1 root root 206 Nov 22 20:43 grub.cfg
-rw-r--r-- 1 root root 1024 Nov 22 19:20 grubenv
drwxr-xr-x 2 root root 12288 Nov 22 19:20 i386-pc
drwxr-xr-x 2 root root 4096 Nov 22 19:20 locale
##
My disks according to lsblk:
##
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 500M 0 part
└─sda2 8:2 0 1.8T 0 part
├─fedora-root 253:0 0 50G 0 lvm
├─fedora-swap 253:1 0 7.7G 0 lvm [SWAP]
└─fedora-home 253:5 0 1.8T 0 lvm /fedorahome
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 1G 0 part /boot
├─sdb2 8:18 0 16G 0 part [SWAP]
├─sdb3 8:19 0 100G 0 part /
├─sdb4 8:20 0 1K 0 part
├─sdb5 8:21 0 200G 0 part /home
└─sdb6 8:22 0 195G 0 part /opt
sdc 8:32 0 1.8T 0 disk
├─sdc1 8:33 0 1G 0 part
└─sdc2 8:34 0 500G 0 part
├─vglfs-swap 253:2 0 16G 0 lvm
├─vglfs-root 253:3 0 100G 0 lvm /lfsefiroot
└─vglfs-home 253:4 0 384G 0 lvm /lfsefihome
sr0 11:0 1 1024M 0 rom
##
Fdisk's listing of /dev/sdb :
##
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 2099199 1048576 83 Linux
/dev/sdb2 2099200 35653631 16777216 82 Linux swap / Solaris
/dev/sdb3 35653632 245368831 104857600 83 Linux
/dev/sdb4 245368832 1084229631 419430400 5 Extended
/dev/sdb5 245370880 664801279 209715200 83 Linux
/dev/sdb6 664803328 1073747967 204472320 83 Linux
##
Filesystem table:
##
# Begin /etc/fstab
# file system mount-point type options dump fsck
# order
/dev/sdb1 /boot ext4 defaults 1 2
/dev/sdb2 swap swap defaults 0 0
/dev/sdb3 / ext4 defaults 1 1
/dev/sdb5 /home ext4 defaults 1 2
/dev/sdb6 /opt ext4 defaults 1 2
proc /proc proc nosuid,noexec,nodev 0 0
sysfs /sys sysfs nosuid,noexec,nodev 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /run tmpfs defaults 0 0
devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
# End /etc/fstab
##
As always, any help is appreciated.
Alan
Hi Alan,
I do not see vmlinuz-3.12-lfs-SVN-20131105 (as mentioned in
/boot/grub/grub.cfg) in the listing of the /boot directory...
I think the line in grub.cfg could be:
linux /vmlinuz-3.12-lfs-SVN-20131119 root=/dev/sdb3 ro
with 3 changes:
vmlinuz - /vmlinuz
20131105 - 20131119
/dev/sdb1 - /dev/sdb3
The last one is because your root filesystem is on /dev/sdb3. root=... tells
the kernel where / is.
Regards
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Error: invalid file name When Booting For the First Time
Le 23/11/2013 20:32, Alan Feuerbacher a écrit : [...] In grub.cfg, why is the root in the line set root=(hd1,1) different from the root in the line linux /vmlinuz-3.12-lfs-SVN-20131119 root=/dev/sdb3 ro? In other terms I have: /dev/sdb1 - /boot /dev/sdb3 - / I'm really fuzzy about this stuff. For grub, root is where it looks for files if not prefixed with (hdx,mdosy) things. That is, grub can list the content of the first partition on disk b either with: ls (hd1, msdos1)/ or with: set root=(hd1,msdos1) ls / For the kernel, root is where / is (that is, /dev/sdb3 with your configuration) At any rate, I recompiled the kernel and reinstalled the grub stuff. I'm still getting an error: error: file '/vmlinuz-3.12-lfs-SVN-20131119' not found. I invoked the grub command line to see what I could see: ls = (hd0) ... (hd1) (hd1,msdos2) (hd1,msdos1) (hd2) So grub apparently sees my disk /dev/sdb as (hd1). Next I tried: ls (hd1) = Device hd1: No known filesystem detected - Total size 3907029168 sectors Try: ls (hd1,msdos1)/ If it does not work, I would guess that the filesystem is not recognized by grub. What is the filesystem on that partition? Maybe you need: insmod filesystem for example: insmod reiserfs I also tried this with (hd0) and (hd2). Same response: no filesystem detected. So for whatever reason, grub is not recognizing the disks. Having tried the same thing with the two other disks, /dev/sda and /dev/sdc, which grub lists above as (hd0) and (hd2), I'm at a loss. All three of these disks are in operation, since when I fire up Fedora19 on /dev/sda, I can write to and read from all of the disks. In grub, ls (hd0) does not specify a partition, so it cannot find a filesystem. ls (hd0,1) will give you the filesystem type on the first partition, ans ls (hd0,1)/ should list the files on that partition. regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Step 5.4.1 Installation of Cross Binutils errors
Le 16/11/2013 00:46, Ken Moffat a écrit : On Fri, Nov 15, 2013 at 01:20:06PM +, Vasco Almeida wrote: OK, I did as instructed in your recommendations above, and tried to be as extra careful as ignorance allows. So I am attaching the four logs collected during the 5.4.1 step, for your kind inspection. But when I invoked make install, I got a raft of This is not dpkg install-info anymore, but GNU install-info See the man page for ginstall-info for command line arguments [...] which are perhaps not that surprising. They are certainly surprising to _me_, and I don't see them in any of the gzipped logs you attached. [...] I do have them in my logs. Debian's install-info is a wrapper to GNU's install-info, for backward compatibility with another install-info they used to ship with dpkg. Those warnings are sent to stderr, that the OP did not capture in the logs. Those warnings are normal on a Debian system (although maybe in this case, the Debian system is not totally normal). Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Step 5.4.1 Installation of Cross Binutils errors
Le 13/11/2013 02:53, Ken Moffat a écrit : On Tue, Nov 12, 2013 at 07:57:30PM -0500, Baho Utot wrote: If you are using bash 4.0 or greater ../path/to/binutils-source/./configure ... | tee myconflog 21 becomes ../path/to/binutils-source/./configure ... | tee myconflog I would change 'becomes' to 'can be changed to' - there is no *requirement* to change a following '21' to a preceding ''. but 21 should be before the `|' anyway : it does not work the same as `'. If you type the command as above, it sends the tee errors to stdout, not the configure errors... Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] SOLVED: lfs 7.4 section 5.9.1. Installation of Binutils error: Cannot run C compiled programs
Le 13/11/2013 04:27, Ron Hartikka a écrit : This looks like virgo's problem at... http://www.mail-archive.com/lfs-support@linuxfromscratch.org/msg20545.html I was pasting from the 7.4 online book into a terminal window. I got to this point (5.9.1): *CC=$LFS_TGT-gcc\ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib \ ../binutils-2.23.2/configure \ --prefix=/tools\ --disable-nls \ --with-lib-path=/tools/lib \ --with-sysroot* I selected all of that at once, middle-mouse-pasted it into my terminal, and hit return. I had entered many multilined commands this way and all seemed to work. But this time, like Virgo, I got this error: *Cannot run C compiled programs* I repeated all of chapter 5 up to there with the same result. I studied the situation and found that echo $CC produced a blank line. So CC was not set. Nor, as I recall, were AR and RANLIB. Neither CC, nor AR or RANLIB should be set. So echo $CC *should* produce a blank line.The way the command above is done allows to set those variables temporarily during the executionof configure. A more relevant test could be echo $LFS_TGT-gcc, or $LFS_TGT-gcc --version. Typing one line at a time without the backslashes does not work the way it is intended to, because the variables CC, etc are not passed to configure! Unless you exported those variables to the environment, you have built binutils pass 2 with the host compiler, not the one you built during gcc pass1. Normally, if you have carefully followed the steps in chapter 4, you may log in and out and back to the lfs user, and always get the same environment. If you get garbbled pasting from the html book (I doubt it, because in this case, it would have shown up during the preceding steps), you may try akh suggestions. But I suspect some environment problem (LFS_TGT or othervariablesnot set or not exported). So please check it. Regards, Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Chapter 6.7.1 header file search verification failure
Le 08/11/2013 20:41, Sandy Widianto a écrit : On Wed, 6 Nov 2013 14:19:18 -0600, William Harrington kb0...@berzerkula.org wrote: On Nov 6, 2013, at 1:24 PM, Sandy Widianto wrote: I'm sure there will be always another top-posting from new members, so I think about top-posting should be mentioned on LFS web. [ Sandy Widianto ] We have pointers to proper posting: Go to the Mailing Lists link at http://www.linuxfromscratch.org Then go to the link described in the sentence Information on how to post messages through Gmane is available on theposting messages page which links to Posting messages http://gmane.org/post.php Sincerely, William Harrington -- I'm sorry about my late to reply, I got problem with my email filter. Almost 3 years I play with LFS I never click on that link until now I just did. Please correct me if I'm wrong, I think the page on that link doesn't mention anything about top posting. Thank you for your attention Mr. William. [ Sandy Widianto ] http://www.linuxfromscratch.org/faq/#netiquette has everything... Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Chapter 6.7.1 header file search verification failure
Le 06/11/2013 03:04, Douglas R. Reno a écrit : Douglas R. Reno renodr2002 at gmail.com writes: Hello, I am having a completely different output than the book says when running grep -B4 '^ / usr/include' dummy.log, I get the following output: ignoring nonexistent directory /tools/ lib/gcc/i686-pc-linux-gnu/4.7.1/../../../../ i686-pc-linux- gnu/include ignoring duplicate directory /usr/ include #include ... search starts here: #include ... search starts here: /usr/include And that is all the output I get. I am using OpenSUSE 12.1 as a host. Can you please tell me what I did wrong and how to fix it? I would also like to bring up that my output from grep -o '/usr/lib.*/ crt[1in].*succeeded' dummy.log reads: /usr/lib/crt1.o succeeded /usr/lib/crti.o succeeded /usr/lib/crtn.o succeeded Also, i am using GCC 4.7.1 instead of 4.7.2, if that helps any. I have built several other systems with that same version. Do you mean you build GCC 4.7.1 or that GCC 4.7.1 is on the host? If you are building GCC 4.7,x you do not have the latest version of the book, do you? What about the SEARCH_DIR outputs? Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Check-0.9.10 can't find subunit/child.h - LFS 7.4
Le 04/11/2013 01:36, Bernard Hurley a écrit : Hi all, On my machine, the output from `ls /usr/include/subunit' is: SubunitTestProgressListener.h child.h However when I try to make Check-0.9.10 (section 5.14.1 page 56,) it fails with the error: ==snip== libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -pthread -g -O2 -Wall -ansi -pedantic -Wextra -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -Wno-variadic-macros -MT check_msg.lo -MD -MP -MF .deps/check_msg.Tpo -c check_msg.c -fPIC -DPIC -o .libs/check_msg.o check_log.c:27:27: fatal error: subunit/child.h: No such file or directory #include subunit/child.h ^ compilation terminated. make[2]: *** [check_log.lo] Error 1 make[2]: *** Waiting for unfinished jobs libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -pthread -g -O2 -Wall -ansi -pedantic -Wextra -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -Wno-variadic-macros -MT check_msg.lo -MD -MP -MF .deps/check_msg.Tpo -c check_msg.c -o check_msg.o /dev/null 21 mv -f .deps/check_msg.Tpo .deps/check_msg.Plo make[2]: Leaving directory `/mnt/lfs/sources/check-0.9.10/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/mnt/lfs/sources/check-0.9.10' make: *** [all] Error 2 ==snip== If I configure it with: ./configure --prefix=/tools --enable-subunit=no then `make' runs OK, for obvious reasons. The default for `--enable-subunit' is `autodetect' but it obiously is not autodetected. I am wondering if subunit support is needed. If not then this solution is OK, and maybe it should be added to the book. If not, then what can I do about it? I am running Debian Wheezy. I have tried purging all the packages that mention subunit and re-installing them, all to no avail. Try just removing libsubunit-dev. That is the package which installs the include files. I think this is the case where configure finds an optional dependency because it has harcoded paths to /usr/include and the such, while the LFS toolchain only searchs into /tools. Whether --disable-subunit should be in the book, I do not know. Regards, Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Check-0.9.10 can't find subunit/child.h - LFS 7.4
Le 04/11/2013 11:01, Bernard Hurley a écrit : On Mon, Nov 04, 2013 at 10:48:41AM +0100, Pierre Labastie wrote: Try just removing libsubunit-dev. That is the package which installs the include files. Thanks, I can build the software if I do that too. I take it from your reply that subunit isn't needed in any case. I test LFS very regularly, and I've never installed subunit. I am on Debian Jessie/sid, but was on wheezy before. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Using wpa_supplicant [Was: ifup--a really uninformed question]
Le 02/11/2013 21:57, Dan McGhee a écrit :
On 11/02/2013 02:50 PM, Bruce Dubbs wrote:
Dan McGhee wrote:
(Received complaints about /run/var/bootlog all through the process.
They were right, it doesn't exist yet.)
Do you have /run/var?
I just discovered. No I don't. Nor do I have /run/lock. I looked in the
book Sections 6.5 and 6.6 to see where and how I missed these. I didn't
see their creation in either section. Would you please tell me where in
the book they get created? I've got to see if I missed anything else.
When I create them, just to double check, make sure the permissions are
0755?
/run is mounted form fstab
tmpfs/run tmpfs defaults 0 0
in the very first boot boot script (mountvirtfs):
# Make sure /run/var is available before logging any messages
if ! mountpoint /run /dev/null; then
mount /run || failed=1
fi
mkdir -p /run/var /run/lock /run/shm
...
The scripts all use so the only reason that you would get this error
is iv /run is not mounted. Actually, even then the writing would be to
a standard directory so the issue would be permissions. These scripts
need to be run as root.
That's great info. Thanks. Referencing the paragraph above, the
directories /run/{var,lock} get created the first time the system boots?
Since /run is mounted on a tmpfs, everything on it is lost once you reboot. So
actually /run/{var,lock,shm} get created at each boot.
I do have /run/shm. It got created in Section 6.2.
That static /run/shm will disappear once you mount /run.
Since I'm operating in chroot, I need to mount /run. Again, to double
check, is the following command the one to use?
mount -v -t tmpfs tmpfs /run
Seems OK.
If the bootscripts are exiting, then it's no wonder that my efforts are
failing. I consider this one of the simple things that I miss. My
knowledge of the bootscripts is slowly coming back. I knew them well six
years ago. :)
Before I forget. Once I get the directory thing straightened out, should
I, as root, touch /run/var/bootlog?
I think it is not needed. You need to mkdir /run/var (see script above)
Thanks, Bruce,
Dan
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Some BLFS Packages Before Making LFS-7.4 Bootable
Le 01/11/2013 00:07, Dan McGhee a écrit : I forgot about wget, thanks for reminding me. gdm is a good idea too, if you want to copy-paste, as long as X is not installed. It builds fine in a chroot environment. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] e2fsprogs -- undefined reference to `uuid_unparse'
Le 29/10/2013 21:00, Bruce Dubbs a écrit : Viola Zoltán wrote: Hi, I have problem - to this chapter - 6.26.1 - I resolved the problems, but now cannot, sorry... /sources/e2fsprogs-1.42.8/build/e2fsck/../../e2fsck/journal.c:1072: undefined reference to `blkid_get_devname' dirinfo.o: In function `setup_tdb': /sources/e2fsprogs-1.42.8/build/e2fsck/../../e2fsck/dirinfo.c:63: undefined reference to `uuid_unparse' collect2: error: ld returned 1 exit status uuid and blkid are defined in util-linux. Did you install that? Specifically the blkid definitions are in /usr/include/blkid/blkid.h. -- Bruce Could you retry with make V=1 instead of just make? You'd get more verbose output, and see the actual command for linking e2fsck. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] glibc test failures. Acceptable?
Le 28/10/2013 14:07, Richard a écrit : [...] Any advice would be welcome. I cannot tell you much about what the tests. Are you sure they did not run to completion? I am also assuming that glibc is one of the packages that can safely be installed to a fake root - then tarballed 'slackware style'? (i.e: I am intending that my next step would be make DESTDIR=dest install), rather then installing directly. glibc does not use DESTDIR= but install_root= (unless it changed for recent versions). -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Newbie need help - bus error in 5.5. GCC-4.8.1 - Pass 1
Le 22/10/2013 23:31, Viola Zoltán a écrit : lfs@Csiszilla ~ $ cat .bashrc set +h umask 022 LFS=/Mount/Simplicity LC_ALL=POSIX LFS_TGT=$(uname -m)-pc-linux-gnu Should be : |LFS_TGT=$(uname -m)-lfs-linux-gnu See section 4.4 and 5.2 for why. | PATH=/tools/bin:/bin:/usr/bin export LFS LC_ALL LFS_TGT PATH alias mc='. /usr/libexec/mc/mc-wrapper.sh' The last line is not from the book. I do not think it is related to the described failure, though, but who knows? If you are really a newbie, try to follow exactly the book. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Using 'find' to Help Make Package Users Simpler
Le 16/10/2013 20:43, Dan McGhee a écrit :
[...]
Here's the find statement:
find / -xdev -type d -gid $(id -g packageuser name) \! -path /usr/src
\! -path /tools -print
This statement achieves all the parameters stated above with the
addition that it ignores /tools also. Now I would like to change group
ownership and permissions and redirect the output to installdirs.lst. I
know I could do that using an intermediate file:
find tmpfile
chown $(cat tmpfile)
chmod $(cat tmpfile)
tmpfile installdirs.lst
rm tmpfile
But, and here's the real question of this post, can I do this with one
statement? Here's my first idea:
'find' | 'chown' | 'chmod' installdirs.lst
I do not know if chown can read standard input. If it would, the first pipe
would work. But
the second will never work, since it takes the output off the chown command,
not that of find...
Or, can I use more than one -exec option in 'find'? The statement would
look something like this
find (stuff) -exec chown :install {} \; -exec chmod ug=rwx, o=rxt {} \;
installdirs.lst
The reason I'm asking this question is that one of my references says
[-exec] will execute the program once per file while xargs can handle
several files with each process. I've never been successful with xargs
and I don't know if 'find' will, then ignore the second -exec. I
haven't been able to glean anymore from wandering around on the internet
and wading through man pages.
I have piped the output of find only once many times, but I don't know
if the output would survive two pipes.
I guess that it's just one question after all. Can I use chained
pipes or -execs before I redirect?
I've never tried two -exec directives in find, sorry. What I know is that xargs
is more flexible,
and I recommand that you insist on having it work.
It could be something similar to:
find... -print| xargs -I xxx sh -c 'chmod xxx; chown xxx; echo xxx
installdirs.lst'
more robust:
find... -print0 | xargs -0 -I xxx sh -c 'chmod xxx; chown xxx; echo xxx
installdirs.lst'
Good luck
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] 6.17. GCC-4.8.1 - Linker search paths
Le 01/10/2013 05:41, Craig Magee a écrit : http://www.linuxfromscratch.org/lfs/view/stable/chapter06/gcc.html It definitely states the block of text I quoted. Would the expected output listed for i686 systems also be incorrect? SEARCH_DIR(/usr/i686-pc-linux-gnu/lib) SEARCH_DIR(/usr/local/lib) SEARCH_DIR(/lib) SEARCH_DIR(/usr/lib); try: grep 'SEARCH.*lib.*' dummy.log |sed 's|; |\n|g' If, for some reason, the SEARCH* line in dummy.log has been split into different lines, it should give the expected result. Actually, even grep 'SEARCH' dummy.log |sed 's|; |\n|g' is enough. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFSv7.4 stuck at section 6.9.1
Le 24/09/2013 11:25, Kodali Sivakiran a écrit :
Hi everyone,
[description of the failure]
In the upper section of config.log we can see that:
configure:2725: gcc --version 5
../glibc-2.18/configure: line 2727: /tools/bin/gcc: No such file or
directory
configure:2736: $? = 127
...
not only gcc ,later i've checked with some of the binaries under
/tools/bin, they say the same thing when i try to use them...No such
file or directory
WHAT MIGHT BE THE REASON??
gcc is a program which mainly runs other executables (cpp for
preprocessing, cc1 for compiling, etc). So even if /tools/bin/gcc is
there, it could be somehow unable to find one ore all of those
executables, which would explain the 'no such file...' diagnostic.
In an attempt to understand the problem, i did this outside the chroot
environment:
shiva@shiva-desktop:/$ ldd /tools/bin/gcc
linux-gate.so.1 = (0xb77dd000)
libc.so.6 = /lib/i386-linux-gnu/libc.so.6 (0xb761b000)
/lib/ld-linux.so.2 (0xb77de000)
so, does it mean that my /tools/bin/gcc got linked with the host
libraries rather than my /tools/lib ???
No it doesn't. When outside the chroot environment, you are using the
host libraries. You have to enter the chroot environment to do that test.
SUGGEST ME SOMETHING ON THIS, SO, THAT I CAN PROCEED FURTHER...
Try:
Enter the chroot environment again and type:
echo 'main(){}' | gcc -x c -v -
You might get some information on where it fails to find files.
If it works, add -Wl,-verbose before the last dash to the above command.
You'll get information on whrer le linker looks for files.
Another possibility is that you forgot to mount the virtual files. Type:
ls /dev (inside the chroot environment).
regards
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] 6.27. Coreutils-8.21 error
Le 24/07/2013 20:03, emel a écrit : Pierre Labastie pierre.labastie at neuf.fr writes: Le 01/05/2013 15:03, سید احمد حسینی a écrit : root:/sources/coreutils-8.21/src# ldd ./expr linux-vdso.so.1 (0x7fffad9a9000) *libgmp.so.10 = not found* how can i fix it ? I'd like to have something to tell you, but I do not understand how it is possible that libgmp.so.10 is found by cc1 and not by expr... What I would try is the following: Start over again (remove the directory coreutils-8.21, tar xf coreutils-8.21.tar.xz, cd, patch, configure). Then: # make V=1 | tee coreutils.log Then: in coreutils.log, look for the lines where expr is compiled. Please send us those lines. Pierre EHLO guys I am having the same issue, i did execute: # make V=1 | tee coreutils.log and this is what i got at coreutils.log: gcc -std=gnu99 -g -O2 -Wl,--as-needed -o src/expand src/expand.o src/libver.a lib/libcoreutils.a lib/libcoreutils.a depbase=`echo src/expr.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ gcc -std=gnu99 -I. -I./lib -Ilib -I./lib -Isrc -I./src-g -O2 -MT src/expr.o -MD -MP -MF $depbase.Tpo -c -o src/expr.o src/expr.c \ mv -f $depbase.Tpo $depbase.Po gcc -std=gnu99 -g -O2 -Wl,--as-needed -o src/expr src/expr.o src/libver.a lib/libcoreutils.a lib/libcoreutils.a -lgmp depbase=`echo src/factor.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ Another thing to notice is, the make command stop because of an error help2man: can't get '--help' info from man/expr.td/ what i did was touch the files man/factor.1 and man/expr.1 and the make ends happyly. But after the instalation expr and bzip. Any helps? Is coreutils.log so short ? Aren't there lines containing the word expr ? And also what do you mean with `after the instalation expr and bzip` ? Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Migrate bc to lfs?
Le 17/07/2013 09:51, loki a écrit : [...] But this brings the question, should bc be migrated from BLFS to LFS since sometimes it is needed for the kernel compilation in Chapter 8.3. Regards, Daniel It has been already migrated, see SVN revision 10258. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Warning about autoconf while configuring glibc-2.17
Le 10/07/2013 14:17, Armin K. a écrit : On 07/10/2013 02:14 PM, Dave Wagler wrote: Do you mean: 'dpkg-reconfigure _bash_' No, he said what he meant. Correct command is dpkg reconfigure *dash* with a dash character : dpkg-reconfigure ;-) -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Segmentation fault compiling gcc-4.7.2 - Pass 1
Le 08/07/2013 16:56, Dave Wagler a écrit : This error occurs while compiling gcc-4.7.2: ../../../gcc-4.7.2/libgcc/libgcc2.c: In function '__multi3': ../../../gcc-4.7.2/libgcc/libgcc2.c:559:1: internal compiler error: Segmentation fault LFS book 7.3, chapter 5.5 Host: Korora 19 KDE amd64 (this installation is dedicated to this LFS sysgen) CPU: Intel(R) Core(TM) i5-3550 with 4 processors Memory: 16GB with 32GB swap available The list of version numbers of critical development tools is in the attached console log. The log was recorded with the script command, so it has that funny formatting. There were no known significant deviations from the book. There were various problems (confusions?) with permissions and ownerships that required use of sudo in places not mentioned in the book, but the actual commands were not changed. Specifying 'make' or 'make -j2' instead of 'make -j4' doesn't change anything. I did a web search for the error message, but there are many different problems that cause segmentation faults. The only thing I saw that looked significant suggested using lower optimization levels. I have been using various linux distros for several years, so I am fairly familiar with how to use the basic system. However, this is the first time I have tried anything like this sysgen, so I know very little about the make process. For example, I don't know how to run make with a different optimization level in the compiles. Any help will be appreciated. The only thing I see in your log, which could lead to an error is: /usr/bin/yacc - /usr/bin/yacc Normally, 'yacc' should be a link to 'bison' or a script which executes 'bison'. You have to test that (type 'file /usr/bin/yacc'). If it is not a script, uninstall yacc. Another thing I see is that the host has gcc 4.8.1 and you are trying to install gcc 4.7.2. I am not sure that configuration has been tested. What you can try is to install a gcc-4.7 package from your distro (not sure how to do that on your host, since I use Debian) and try again. As of the optimization level for gcc, you should keep the default (which is -g -O2), as that is the recommended way from the gcc developpers. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Ch 5.13: Check fails to build
Le 04/07/2013 16:14, hans kaper a écrit : I am building LFS 7.3, copy-pasting from the book into scriptfiles. I restarted with ch.5 about five times, but I get no further then ch. 5.13, building Check 0.9.9. I have not seen any conspicuous errors building from the earlier paragraphs and certainly no FAILURES. The end of the make-log is: /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld: check_thread_stress-check_thread_stress.o: undefined reference to symbol 'pthread_create@@GLIBC_2.1' /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld: note: 'pthread_create@@GLIBC_2.1' is defined in DSO /tools/lib/libpthread.so.0 so try adding it to the linker command line /tools/lib/libpthread.so.0: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status make[2]: *** [check_thread_stress] Error 1 make[2]: Leaving directory `/mnt/lfs/sources/check-0.9.9/tests' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/mnt/lfs/sources/check-0.9.9' make: *** [all] Error 2 FAILED! libpthread.so.0 is a link to libpthread-2.17.so. Anyone any ideas? Or can I just carry on, because it is a failure in a test? Have you applied the errata : --- from Errata for the 7.3 Version of the LFS Book Changes to some distros cause the build of *check-0.9.9* to fail in Chapter 5. The proper fix is to add --with-sysroot to the end of the configure line in *Binutils-2.23.1 - Pass 2*. --- It might address your error too. Regards Pierre -- 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-7.3: USB mouse repeatedly disconnecting and reconnecting
Le 01/07/2013 17:28, William K Helbig Jr a écrit : Hello all, I have followed the book all the way to the end, and now have a working system, sort of. I am able to boot and log into LFS-7.3. It is of course a bare, minimal system but it does seem to be functional. There is one problem however. Approximately every 60 seconds the mouse is disconnected then immediately reconnected. A sample of the console log is: [...] usb 1-8.2.2.2: USB disconnect, device number 25 [...] usb 1-8.2.2.2: new low-speed USB device number 26 using ehci-pci [...] usb 1-8.2.2.2: New USB device found, idVendor=046D, isProduct=c05a [...] usb 1-8.2.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber-0 [...] usb 1-8.2.2.2: Product: USB Optical Mouse [...] usb 1-8.2.2.2: Manufacurer: Logiech [...] usb 1-8.2.2.2: Input: Logiech USB Optical Mouse as /devices/pci:00/:00:1d.7/usb1/1-8/1-8.2/1-8.2.2/1-8.2.2.2/1-8.2.2.2:1.0/input/input32 [...] usb 1-8.2.2.2: Hid-generic 0003:046D:C05A.001A: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-:00:1d.7-8.2.2.2/input0 This occurs both before and after I login. What I have noticed is the device number and Hid-generic value increments by 1 each time. The next iteration of the above is ... USB disconnect, device number 26 ... new low-speed USB device number 27 using ehci-pci ... ... usb 1-8.2.2.2: Hid-generic 0003:046D:C05A.001B: ... /input0 The hardware is a Dell Latitude D620 laptop in a docking station with both the mouse and (USB) keyboard connected to the docking station. The keyboard appears to be functioning correctly. Skip H I have had the same issue with an HP mouse connected to a USB port on a desktop machine, while there is no such thing with a microsoft mouse. So, seems mouse-dependent. If you have a spre mouse, then give it a try. Pierre -- 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-7.3: USB mouse repeatedly disconnecting and reconnecting
Le 01/07/2013 17:28, Pierre Labastie a écrit : Le 01/07/2013 17:28, William K Helbig Jr a écrit : Hello all, I have followed the book all the way to the end, and now have a working system, sort of. I am able to boot and log into LFS-7.3. It is of course a bare, minimal system but it does seem to be functional. There is one problem however. Approximately every 60 seconds the mouse is disconnected then immediately reconnected. A sample of the console log is: [...] usb 1-8.2.2.2: USB disconnect, device number 25 [...] usb 1-8.2.2.2: new low-speed USB device number 26 using ehci-pci [...] usb 1-8.2.2.2: New USB device found, idVendor=046D, isProduct=c05a [...] usb 1-8.2.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber-0 [...] usb 1-8.2.2.2: Product: USB Optical Mouse [...] usb 1-8.2.2.2: Manufacurer: Logiech [...] usb 1-8.2.2.2: Input: Logiech USB Optical Mouse as /devices/pci:00/:00:1d.7/usb1/1-8/1-8.2/1-8.2.2/1-8.2.2.2/1-8.2.2.2:1.0/input/input32 [...] usb 1-8.2.2.2: Hid-generic 0003:046D:C05A.001A: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-:00:1d.7-8.2.2.2/input0 This occurs both before and after I login. What I have noticed is the device number and Hid-generic value increments by 1 each time. The next iteration of the above is ... USB disconnect, device number 26 ... new low-speed USB device number 27 using ehci-pci ... ... usb 1-8.2.2.2: Hid-generic 0003:046D:C05A.001B: ... /input0 The hardware is a Dell Latitude D620 laptop in a docking station with both the mouse and (USB) keyboard connected to the docking station. The keyboard appears to be functioning correctly. Skip H I have had the same issue with an HP mouse connected to a USB port on a desktop machine, while there is no such thing with a microsoft mouse. So, seems mouse-dependent. If you have a spre mouse, then give it a try. Pierre Of course, read spare instead of spre... -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Can't set up my timezone correctly
Le 24/06/2013 20:14, Molly Jakić a écrit : On 24 June 2013 19:01, Sergey Shidlovsky sshidlov...@gmail.com mailto:sshidlov...@gmail.com wrote: Greetings to all LFS builders! Now I'm at the beginning of chapter 6. [...] Therefore TZ='Europe/Kiev' will be used. Local time is now: Mon Jun 24 23:48:23 EEST 2013. Universal Time is now: Mon Jun 24 20:48:23 UTC 2013. --- The problem is that correct time where I live (Kiev, Ukraine) is that which mentioned as Universal Time, but not Local time. As I can understand, Universal Time is the same as Greenwich Meantime. But in my country all clocks is set at +2 hours to it. Can I fix this issue somehow? Hi. Look in /etc/sysconfig/clock. My system clock is set to local time, so i write UTC=0. If I understand rightly, your system clock is set to UTC, so you should write UTC=1 and then the system will adjust appropriately. Regards, Molly I think /etc/sysconfig/clock is an LFS file. When you are at chapter 6, the system you use is still the host. So /etc/sysconfig/clock might be useless. Actually, what is output at the end of the tzselect script assumes that the host clock is set up to UTC (see 'man date' for details), which might not be true. So you should not bother much about that output, and wait until chapter 7.9 configuring the setclock script to set up the clock properly for the LFS system. Right now, you just have to configure the /etc/localtime file. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] First LFS login/boot
Le 18/06/2013 11:47, John Black a écrit : I took a picture from my cellphone and type it to this email. 1. Adding IPv4 address 192.168.1.1 to the eth0 interface...Cannot find device eth0 2. -bash-4.2$_ - 1. How to fix it? 2. whay bash not root, it's something wrong? Any help please GET FREE SMILEYS FOR YOUR IM EMAIL - Learn more at http://www.inbox.com/smileys Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails If I understand correctly, you first see the caanot find device eth0 during boot, then you log in as root, and get the prompt shown on the 2. line. I think that prompt is OK. To make sure you are root, type whoami (should return `root'). Now, to address the first error, type ip link show. It should return the list of network devices, with their current state. lo0 is the localhost interface, any other (you might get enp0s3 for example) is the name given by the kernel to the interface. There is also a possibility that you see no other interface if it has not been enabled in the kernel configuration. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Kernel configuration
Le 17/06/2013 14:02, John Black a écrit : I'm so very late to reply, because I just found the problem. I missed the mentioned note! - Note Due to recent changes in udev, be sure to select: Device Drivers --- Generic Driver Options --- Maintain a devtmpfs filesystem to mount at /dev - I'm really sorry about that. If I want to re-compile linux-3.8.1 directory, should I do -- 'make mrproper again? if yess I think it means I have to start again from beginning for kernel configuration. Save the file .config (notice the dot at the beginning) at some safe place (usually /sources). Erase the build directory, untar linux again, change to the build directory, make mrproper, then copy back .config and make menuconfig. That should start from the current configuration. Pierre -- 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-7.3: Error while building package Check0.9.9
On 15/06/2013 13:38, Vasudeo Bidve wrote: Hi, Here is the detailed information: 1. LFS version: 7.3 2. Host dist: Linux Mint 13 3. Host system configuration: Attached in host-system.txt 4. Package under problem: Check-0.9.9 (Section 5.13 in the LFS book 7.3) 5. Exact error: Error produced during make process. Some of the last relevant section output of Make is copied in a log file check0.9.9-error.log and attached herewith. I also tried looking at lfs-faq and search-list. But didn't find suitable/related answer, so posting on Support. Please help. Thanks and Regards Vasudeo K. Bidve Have you applied the erratum : http://www.linuxfromscratch.org/lfs/errata/stable/ ? Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] About errors
Le 06/06/2013 14:50, Philippe Delavalade a écrit :
Hi :-)
I prefer a second message for another problem.
On my debian host system, in files .bashrc, i use the following lines to be
informed from errors in a command :
if [ $PS1 ]; then
_prompt_command()
{
local status=$?;
if [ $status != 0 ]; then
echo -n $status 12;
fi
}
PROMPT_COMMAND=_prompt_command
fi
So, the exit code is printed before the prompt in case of an error.
I'd like to do so in chapter 6 of LFS but, as there is no .bashrc, I wonder
where I could append this lines.
Thanks for advice.
I haven't tried, but I would say that it could go in .bashlogin in
/root. Then if you use the chroot command of 6.4, .bashlogin is sourced.
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] About errors
Le 06/06/2013 17:49, Philippe Delavalade a écrit :
Le jeudi 06 juin à 15:48, Pierre Labastie a écrit :
Le 06/06/2013 14:50, Philippe Delavalade a écrit :
_prompt_command()
{
local status=$?;
if [ $status != 0 ]; then
echo -n $status 12;
fi
}
PROMPT_COMMAND=_prompt_command
I haven't tried, but I would say that it could go in .bashlogin in
/root. Then if you use the chroot command of 6.4, .bashlogin is sourced.
Pierre
Thanks but I have just .bash_history in /root.
Did I missed something ?
Sorry, I meant, put the lines from _prompt_command() to
PROMPT_COMMAND=...
into $LFS/root/.bashlogin (using copy/paste or an editor), and then
chroot using the command on page 6.4.
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Q: re. LFS 7.3 errata
Le 19/05/2013 15:31, Jeremy Henty a écrit : Sorry, I am confused. Do you mean I will be OK ignoring the erratum or I will be OK if I follow it? And does add --with-sysroot mean literally to add --with-sysroot rather than --with-sysroot=$LFS (as in pass 1). It is --with-sysroot and nothing more. That changes the behavior of ld in some circumstances, which are met when building 'check'. You may want to read http://article.gmane.org/gmane.linux.lfs.devel/13809 and http://article.gmane.org/gmane.linux.lfs.devel/13812, where I tried to explain the use of that switch. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] why does LFS need that number of patches
Le 16/05/2013 20:22, Fernando a écrit : I have sent this in the morning, about 7 hours ago, it never appeared. Actually, I got it at 12:38 (western European time), while the one where you added the above sentence arrived at 20:22. Both are on gmane too... Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 6.27. Coreutils-8.21 error
Le 01/05/2013 11:50, سید احمد حسینی a écrit : ./expr --help is : root:/sources/coreutils-8.21# cd src/ root:/sources/coreutils-8.21/src# ./expr --help ./expr: error while loading shared libraries: libgmp.so.10: On my system, libgmp.so.10 is in /usr/lib. It is a symlink to libgmp.so.10.1.1. Since it is in /usr/lib, it should be found. It is amazing that you have not had a problem before, because libgmp.so.10 is required by the gcc compiler, too... Could you try (while being chrooted): # find /usr -name cc1 That should return a path to cc1. Then type # ldd path_to_cc1 where path_to_cc1 is the path returned above. Compare with the output of (while being in the src directory): # ldd ./expr Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 6.27. Coreutils-8.21 error
Le 01/05/2013 15:03, سید احمد حسینی a écrit : root:/sources/coreutils-8.21/src# ldd ./expr linux-vdso.so.1 (0x7fffad9a9000) *libgmp.so.10 = not found* how can i fix it ? I'd like to have something to tell you, but I do not understand how it is possible that libgmp.so.10 is found by cc1 and not by expr... What I would try is the following: Start over again (remove the directory coreutils-8.21, tar xf coreutils-8.21.tar.xz, cd, patch, configure). Then: # make V=1 | tee coreutils.log Then: in coreutils.log, look for the lines where expr is compiled. Please send us those lines. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 6.27. Coreutils-8.21 error
Le 30/04/2013 15:50, سید احمد حسینی a écrit : Please help me I'm really stuck here. From: ahmad...@outlook.com To: lfs-support@linuxfromscratch.org Date: Mon, 29 Apr 2013 17:39:47 +0430 Subject: Re: [lfs-support] 6.27. Coreutils-8.21 error This parameter does not work: root:/sources/coreutils-8.21# make -j1 make all-recursive [...] GEN man/expand.1 GEN man/expr.1 help2man: can't get '--help' info from man/expr.td/expr make[2]: *** [man/expr.1] Error 127 make[2]: Leaving directory `/sources/coreutils-8.21' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/sources/coreutils-8.21' make: *** [all] Error 2 Hi, Have you tried to delete the current coreutils-8.21 directory, to untar it again, and to start building again (patch, configure, and make -j1)? Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Coreutils 8.21 test failure - many-dir-entries-vs-oom
Le 30/04/2013 18:23, Bruce Dubbs a écrit : Steve Crosby wrote: Just an FYI - This test fails for me (and looking at the archives at least one other recently), and looking at the logs, it's because it's attempting to create 200,000 small files - that exceeds the inode count on the seperate 2GB ext3 filesystem I created for sources. e.g. + expensive_ + test yes '!=' yes + mkdir d + cd d + seq 20 + xargs touch touch: cannot touch '125627': No space left on device touch: cannot touch '125628': No space left on device root@slax:~# tune2fs -l /dev/sdb1 | grep Inode Inode count: 131072 Inodes per group: 8192 Inode blocks per group:512 Inode size: 256 Perhaps a note to check the inode count before running this test might be in order, or a note that it might fail? IMO, this is an extreme case. We suggest a minimum 10G partition that includes sources as well as the base files. Trying to cover every situation where customizations can go wrong isn't reasonable. I'm willing to listen to other opinions though. -- Bruce Well, At least a note telling that a couple of tests may fail. The 'stty-pairs' test fails in a virtual console for example. I think I once got a failure in the same test as the OP, too. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 6.27. Coreutils-8.21 error
Le 30/04/2013 18:46, Ken Moffat a écrit : On Tue, Apr 30, 2013 at 08:00:25PM +0430, سید احمد حسینی wrote: thank youI doI also use the parameter xBut again, I encounter this error From: ahmad...@outlook.com To: lfs-support@linuxfromscratch.org Date: Mon, 29 Apr 2013 17:39:47 +0430 Subject: Re: [lfs-support] 6.27. Coreutils-8.21 error This parameter does not work: root:/sources/coreutils-8.21# make -j1 make all-recursive [...] GEN man/expand.1 GEN man/expr.1 help2man: can't get '--help' info from man/expr.td/expr make[2]: *** [man/expr.1] Error 127 make[2]: Leaving directory `/sources/coreutils-8.21' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/sources/coreutils-8.21' make: *** [all] Error 2 That is a really weird error - in a normal LFS build, help2man is a parameter for the build-aux/missing script. If I'm reading that part correctly, it *either* just touches the existing output file, *or* it reports help2man is required to generate this page when the file is missing. In a normal LFS build the help2man program doesn't exist, and the pages are already there. But this output seems to be invoking a *real* help2man program from within chroot. help2man is in the `man' directory in the coreutils-8.21 tree. I think it is really used in that case (could be checked with `make V=1'). The only other possibility I can think of is a problem with the LANG or LC_ALL variable being set to something different from C or POSIX, since help2man uses the output of `command --help'. But this should not happen in the chroot environement. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 6.27. Coreutils-8.21 error
Le 30/04/2013 21:21, Ken Moffat a écrit : On Tue, Apr 30, 2013 at 06:58:12PM +0200, Pierre Labastie wrote: help2man is in the `man' directory in the coreutils-8.21 tree. I think it is really used in that case (could be checked with `make V=1'). Thanks, I'd overlooked that. I've learned something :) Ahmad, please ignore my previous response. man/help2man is a perl script, invoked from man/local.mk : ## Graceful degradation for systems lacking perl. if HAVE_PERL run_help2man = $(PERL) -- $(srcdir)/man/help2man else run_help2man = $(SHELL) $(srcdir)/man/dummy-man endif AFAICS, it runs against the compiled program (expr in this case) passing a flag of --help. The normal output [ GEN man/expr.1 ] hides that, which is why I don't see it in my logs. And because it was run, we know that some of perl is installed - actually, we know there is at least enough perl to get through the glibc build. The only other possibility I can think of is a problem with the LANG or LC_ALL variable being set to something different from C or POSIX, since help2man uses the output of `command --help'. But this should not happen in the chroot environement. Pierre Possible. Looking at all of the *.po files in coreutils' po/ directory, I don't see any languages which look likely - Ahmad appears to be in a locale which uses an arabic script, none of the .po files seem appropriate. Either way, I'm still surprised that it gets to 'expr' before it fails - there are about 26 man pages before tht which apparently didn't cause a problem. ĸen You are right : that rules out locale problems, and also anything related to perl installation. Maybe it could be a good idea to try to run expr --help, and see what the output is. try : cd src ./expr --help Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 6.7. Linux-3.8.1 API Headers /mnt/lfs not mounted
Le 22/04/2013 08:59, سید احمد حسینی a écrit : Hi in The Chapter 6. Installing Basic System Software section I do not know exactly what to do When /mnt/lfs not mounted How do I install linux headers(6.7. Linux-3.8.1 API Headers http://www.linuxfromscratch.org/lfs/view/stable/chapter06/linux-headers.html)? What do you mean /mnt/lfs not mounted? In chapter 6, you are chrooted to /mnt/lfs, so everything which was previously /mnt/lfs/somedir is now accessed at /somedir. Therefore, if you downloaded the tarballs to /mnt/lfs/sources in chapter 3, they should now be found into /sources. So my guess is: change dir to /sources, and unpack: - cd /sources tar xvf linux-3.8.1.tar.xz - then: cd linux-3.8.1 and follow the book. regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Automated build of LFS 7.3
Le 10/04/2013 15:51, Thanos Baloukas a écrit : On 04/10/2013 04:37 PM, Baho Utot wrote: On 04/10/2013 09:33 AM, Anthony Wright wrote: I'm an old LFS user who originally worked with LFS 6.1, and more recently 6.8. To build these two systems automatically I used jhalfs. I'd like to upgrade to LFS 7.3, but I can't get jhalfs 2.3.2 (the latest version of the recommended ALFS build tool) to work. Is ALFS still active - nothing seems to have changed with it since July 2009? Is there another way to build LFS 7.3 automatically? thanks, Anthony Wright I have some scripts at: https://github.com/baho-utot You can get some ideas there. You can use the development version of jhalfs. It worked for me lately. On alfs page says how to fetch it via svn. The wiki page of alfs has been recently updated to reflect the current state of jhalfs. Updating the site page may take some more time, by lack of manpower... Regards, Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Changing the ownership
Le 08/04/2013 18:10, Prabhu a écrit : Hi, I'm working on LFS-7.2, I successfully compiled the packages until XZ-5.0.4 and I did stripping, then in Changing the ownership I checked the permissions of tools directory as lfs user and host user then I switched back to the root user and I executed this command *sudo chown -R root:root $LFS/tools*, but after executing it the permission remains same. I would like to know the exact permission of the tools directory. Could someone assist me in this. With Regards... PRABHU :) check LFS: echo $LFS -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Binutils First compilation.
Le 06/04/2013 23:50, Ken Moffat a écrit : googling for 'powers of e' suggests e*8 is 2,980.9579870409 so the file was approx 8346 seconds in the future, or about 2 hours 20 in coarse figures. Not very important, but I would think that 2.8e+08 is the C notation for floating point real, that is +08 is a power of 10. This would mean that the date was wrong by about 10 years (1 day is ~100,000 s, one year is roughly 30,000,000, so 280,000,000 is around ten years plus or minus one or two years...). Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Problems in Binutils Pass 2
Le 05/04/2013 12:22, Alex Stefan Kaye a écrit : Thanks for the reply. I definitely set them last night, and I just tried again this morning, checking them before configuring: lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ CC=$LFS_TGT-gcc lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ AR=$LFS_TGT-ar lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ RANLIB=$LFS_TGT-ranlib lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ echo $CC $AR $RANLIB x86_64-lfs-linux-gnu-gcc x86_64-lfs-linux-gnu-ar x86_64-lfs-linux-gnu-ranlib When you enter: Variable-name=something `Variable_name' is defined locally in the shell you are running. It is not _exported_ (to any command you launch). So, when you do like that, `configure' ignores the values you have set for CC, AR and RANLIB. You can do: export CC=... But then, CC is exported for any command in that shell, which is not what you want after building gcc. To export variables to only one command, you type: Variable_name=something command Then the value of Variable_name is set for the execution of command. That is the approach in the book: CC=$LFS_TGT-gcc \ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib \ ../binutils-2.23.2/configure \ --prefix=/tools \ --disable-nls \ --with-lib-path=/tools/lib \ --with-sysroot Notice the \ at the end of each line (the \ must be immediately followed by return, no space), which means it is equivalent to: CC=$LFS_TGT-gcc AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib ../binutils-2.23.2/configure --prefix=/tools... Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Problems in Binutils Pass 2
Le 04/04/2013 23:05, Alex Stefan Kaye a écrit : Hi all, I've just started my LFS journey, and I've hit upon a problem when running configure during binutils pass 2. I've not deviated from the book at all (discounting any mistakes I've not noticed - it's late here, but I've been careful). The error: checking for C compiler default output file name... configure: error: in `/mnt/lfs/sources/binutils-build': configure: error: C compiler cannot create executables From your config.log: configure:3767: checking for gcc configure:3783: found /usr/bin/gcc configure should find x86_64-lfs-linux-gnu-gcc! Have you typed the three lines: CC=$LFS_TGT-gcc\ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib \ before configure? Or Maybe $LFS_TGT is not set correctly. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 5.8. Binutils-2.23.1 - Pass 2 configure: error: C compiler cannot create executables
Le 31/03/2013 14:20, سید احمد حسینی a écrit :
hi
in
http://www.linuxfromscratch.org/lfs/view/7.3/chapter05/binutils-pass2.html
[...]
configure:4063: checking for C compiler default output file name
configure:4085: x86_64-lfs-linux-gnu-gcc conftest.c 5
/mnt/lfs/tools/bin/../lib/gcc/x86_64-lfs-linux-gnu/4.7.2/../../../../x86_64-lfs-linux-gnu/bin/ld:
cannot find crt1.o: No such file or directory
/mnt/lfs/tools/bin/../lib/gcc/x86_64-lfs-linux-gnu/4.7.2/../../../../x86_64-lfs-linux-gnu/bin/ld:
cannot find crti.o: No such file or directory
/mnt/lfs/tools/bin/../lib/gcc/x86_64-lfs-linux-gnu/4.7.2/../../../../x86_64-lfs-linux-gnu/bin/ld:
cannot find -lc
/mnt/lfs/tools/bin/../lib/gcc/x86_64-lfs-linux-gnu/4.7.2/../../../../x86_64-lfs-linux-gnu/bin/ld:
cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
configure:4089: $? = 1
[...]
configure: exit 77
It looks like Glibc is not installed in /tools.
Have you tried the test at the end of the Glibc page?
If the test is OK,
Try:
echo 'main(){}' dummy.c
$LFS_TGT-gcc -v -Wl,-verbose dummy.c | tee gcc-log
grep crt1 gcc-log
If one of the above commands give an error try to recompile Glibc.
Regards
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] eth0 issue NO SUCH DEVICE
Le 20/03/2013 07:41, xinglp a écrit : 2013/3/20 Rubin Saifirubinsa...@live.com: /run/var/bootlog : no such file or directory /etc/sysconfig/ifconfig.eth0 - well configured /etc/sysconfig/network - well configured ifup eth0 - no device eth0 i am done with the LFS book and the LFSBox is up and running but before the root login it shows that no interface eth0 , no such device etc,.. what should be done to get eth0 up and working What's in /sys/class/net ? Also, you can try 'ip link list'. It should give you the name of the network interface (together with some other information). Modern udev tends to rename network interface to names like enpXsY where X and Y are numbers. It is also possible that you did not enable your specific network card in the kernel configuration. If you find some enpXsY either by doing ip link list or by listing /sys/class/net, try replacing the line 'IFACE=eth0' by IFACE='enpXsY' in /etc/sysconfig/ifconfig.eth0 (renaming the file is not mandatory, although it is cleaner IMHO). Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Getting error in coreutils
Le 14/03/2013 12:26, Rubin Saifi a écrit : Getting error in coreutils critical cmd :su nobody -s /bin/bash -c PATH=$PATH make RUN_EXPENSIVE_TESTS=yes -k check || true OUTPUT : snipped ,.. Testsuite summary for GNU coreutils 8.19 # TOTAL: 315 # PASS: 278 # SKIP: 37 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 make[6]: Leaving directory `/sources/coreutils-8.19/gnulib-tests' make[5]: Leaving directory `/sources/coreutils-8.19/gnulib-tests' make[4]: Leaving directory `/sources/coreutils-8.19/gnulib-tests' make[3]: Leaving directory `/sources/coreutils-8.19/gnulib-tests' make[2]: Leaving directory `/sources/coreutils-8.19/gnulib-tests' make[2]: Entering directory `/sources/coreutils-8.19' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/sources/coreutils-8.19' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/sources/coreutils-8.19' make: *** [check] Error 2 If the command ends with || true, it means it is expected to fail... I think the latest coreutils version (8.21) has no error in the tests, but do not know for sure about 8.19. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] M4-1.4.16 : libgmp.so.10 error
Le 14/03/2013 13:13, Rubin Saifi a écrit : M4-1.4.16 ./configure --prefix=/usr output error while loading llibgmp.so.10 no such file or directory found Section 6.28 LFS 7.2 It is very amazing that this error appears first with m4: libgmp is used by gcc, which has been used several times before building m4. There is nothing about gmp being directly needed by m4. Have you changed your PATH or anything in your environment between the preceding package and m4? Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] make error in Coreutils
Le 13/03/2013 18:50, spiky a écrit :
On 13/03/13 17:47, Rubin Saifi wrote:
here is the error
--
root:/sources/coreutils-8.19# make
CDPATH=${ZSH_VERSION+.}: cd . /bin/sh
/sources/coreutils-8.19/build-aux/missing aclocal-1.12a -I m4
/sources/coreutils-8.19/build-aux/missing: line 81: aclocal-1.12a:
command not found
WARNING: 'aclocal-1.12a' is missing on your system.
You should only need it if you modified 'acinclude.m4' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'aclocal' program is part of the GNU Automake package:
http://www.gnu.org/software/automake
It also requires GNU Autoconf, GNU m4 and Perl in order to run:
http://www.gnu.org/software/autoconf
http://www.gnu.org/software/m4/
http://www.perl.org/
make: *** [aclocal.m4] Error 127
any help plz.
Do you have m4 installed on host maybe post the output of the
version-script
You may want to have a look at this thread :
http://article.gmane.org/gmane.linux.lfs.support/36437
The error is the same. It was found that that happens when you copy the
build tree instead of untarring it.
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] help, i hosed my windows partition
Le 10/03/2013 10:33, tilmanbregler a écrit : Hi, so this is a bit emberassing, and I appreciate if you say this is nothing to do with you. I have this dual boot Ubuntu 12.04/Windows 7 setup. And to make room for th LFS partitions i decided to shrink the Windows 7 partition. [...] This is how my partition table looks, atm: sudo fdisk -l Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x05b005af Device Boot Start End Blocks Id System /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT /dev/sda3 206848 1465147391 732470272 5 Extended /dev/sda5 1024004096 1449783295 212889600 83 Linux /dev/sda6 1449785344 1465147391 7681024 82 Linux swap / Solaris Well, so which is your Ubuntu partition: /dev/sda5? It seems that there is a NTFS partition at /dev/sda1. What is it? I thought Windows needed only one partition, but maybe it is not true. Anyway, you could try two things: 1) Shrink the first partition by one sector (this involves shrinking first the filesystem), then remove the extended partition and recreate it starting at 206847 (this involves removing first /dev/sda5-6 and recreating them afterwards, at the same sectors of course, see 2) below for something slightly more detailed). Then recreate the Windows partition starting at 206848. 2) Remove first the extended partition /dev/sda3. This involves removing /dev/sda5 and 6, too, so you might loose your linux systems if something goes wrong. Of course, keep a track of the sectors of those partitions... -Create a primary partition (/dev/sda2) for the NTFS system starting at 206848 and with a size enough to contain your Windows system. -Recreate the extended partition starting just after /dev/sda2 and extending to the end of the disk. -Recreate logical partitions /dev/sda5 and 6 with the same sectors as before. -Cross fingers and write the table to disk (well, instead of crossing fingers, think long before you do, print the partition table and double check everything. As long as you do not type 'w', you cannot screw things more than they are...) Remember, all of this may fail for just one typo! Regards and good luck Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Ubuntu 12.10 install
Juan Alberto Regalado Galván 00jarg at gmail.com writes: Keith: The first ln command that Bruce provided you, works just fine if you're under the /bin directory. Then he corrected himself by giving you a flawless command which works, no matter where you stand on your file system. The intention of the list is to help users with LFS, not to prove their expertise under linux. Your comment is totally unnecessary and out of place. Please keep in touch if you encounter more problems. Greetings, Juan Alberto. It's a pity that this thread went this way. The sh-bash link is one of the mildest requirement of the hostreqs. I have built LFS a lot of times with /bin/sh-dash on Debian. What I think the original poster is missing is a bunch of libxxx-dev packages, because a normal Unbuntu installation does not have them. But since he did not send the error he was getting, it is hard to help more. I have built LFS on Ubuntu 12.10, but I am sorry I have not taken a note of what I had to install. At least libc6-dev, libncuses5-dev, and surely others. The hostreqs page do not test their presence (actually, those packages contain mainly the headerfiles *.h). Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Slightly different output from gcc test in chapter 6.17.1
Le 02/03/2013 18:56, Niels Terp a écrit : Hi, I’m doing the newly released version 7.3 on a OpenSuSE 12.3 host (32 bit). In this chapter I get some of the output right, but in the wrong sequence: The command*grep -B4 '^ /usr/include' dummy.log* Should give this output: #include ... search starts here: /usr/local/include /usr/lib/gcc/i686-pc-linux-gnu/4.7.2/include /usr/lib/gcc/i686-pc-linux-gnu/4.7.2/include-fixed /usr/include But in my case I get: root:/sources/gcc-build# grep -B4 '^ /usr/include' dummy.log #include ... search starts here: /usr/lib/gcc/i686-pc-linux-gnu/4.7.2/include /usr/local/include /usr/lib/gcc/i686-pc-linux-gnu/4.7.2/include-fixed /usr/include root:/sources/gcc-build# Does this mean anything ? I do not think it means so much. I have the same as you, both with LFS 7.2 and 7.3. Looks like the output has not been edited for a few years in the book. I guess older versions of gcc had the output reversed. Anyway, I think you can go ahead and not worry. Regards Pierre -- 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-support Digest, Vol 2787, Issue 1
Le 04/02/2013 09:04, Andi Blacktigerbro a écrit : I got unresolved error with LFS 7.2. Now I'm trying with LFS 7.0, probably it will more smoothly give less errors for Debian Squeeze. Thank you for your kind words and support. Hi Andi, I am not sure about what you did. If you get errors on Debian Squeeze with LFS 7.2, it might be an indication that you miss some required tools, which are not installed in a default Debian installation. Have you checked the host requirements, as on page vii of the preface? After a standard installation, you need to run (as root, or using sudo): apt-get install binutils apt-get install bison apt-get install bzip2 apt-get install gawk apt-get install gcc (installs also glibc-dev) apt-get install make - If you miss any of those packages, you will run into trouble at some point, whatever the LFS version. Good luck, Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] The easiest Linux From Scratch version to be builded under Debian Squeeze?
Le 04/02/2013 04:53, Andi Blacktigerbro a écrit : What is the easiest Linux From Scratch version to be builded under Debian Squeeze (i386), because Debian packages always outdated? I think you can use any recent version of LFS. I have been able to build the LFS svn version on debian squeeze i386 about two days ago. It went smoothly. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] booting don't work with UUIDs
Le 31/01/2013 16:48, Sven Bartscher a écrit :
Am 30.01.2013 17:21, schrieb Pierre Labastie:
Le 30/01/2013 15:55, Sven Bartscher a écrit :
Am 29.01.2013 22:02, schrieb Pierre Labastie:
Le 29/01/2013 13:42, Sven Bartscher a écrit :
Am 23.01.2013 18:03, schrieb Bruce Dubbs:
Sven Bartscher wrote:
hey guys!
I didn't installed GRUB in the chapter 8 and configured my already
installed GRUB
That's OK.
with writing the following text in the /boot/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,msdos4) #i tried it with set root=(hd0,4) too
menuentry GNU/Linux, Linux 3.5.2-lfs-7.2 {
linux /boot/vmlinuz-3.5.2-lfs-7.2
root=UUID=4f9f6834-c55b-492e-a70c-4e3bca952f5b ro
}
The kernel doesn't understand UUIDs. You need an initrd. See BLFS
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/initramfs.html
-- Bruce
I can't use the /dev/sdxy partition names because i have two hard
drives
(IDE and SATA) and the names are after rebooting randomly mixed.
So i
can't be sure which is the right /dev/sdxy file.
I try to boot my new lfs system and it don't work instead i get this
message (a little bit more but i think this is the important part):
VFS: Cannot open root device
UUID=4f9f6834-c55b-492e-a70c-4e3bca952f5b
or unknown-block(0,0): error -6
Please append a correct root= boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
I don't use an extra /boot partition so i have two /boot folders
one on
my Ubuntu(containing GRUB and the Ubuntu kernel) partition and one
on my
LFS (containing the LFS kernel) partition can this work?
Can i even use UUIDs for lfs?
Did i anything else wrong?
my host system: Ubuntu 12.10
my lfs version 7.2
I have created an initramfs. Here the log:
root:/# mkinitramfs
Creating initrd.img-no-kmods... cp: Aufruf von stat f�r
�/etc/udev/udev.conf� nicht m�glich: Datei oder Verzeichnis nicht
gefunden
install: Aufruf von stat f�r �/usr/share/mkinitramfs/init.in� nicht
m�glich: Datei oder Verzeichnis nicht gefunden
done.
root:/#
I do not understand german, but I have played a lot with mkinitramfs,
So I think you got 2 file not found errors.
The first one (/etc/udev/udev.conf) is harmless, and always occurs
with modern udev.
The second one might be the explanation to your problem:
init.in is renamed to init in the initramfs, and is the heart of the
initramfs system.
If it is not there, nothing can work.
Haven't you overlooked the second part of the mkinitramfs installation
(cat /usr/share/mkinitramfs/init.in EOF)?
Also, if you compiled the kernel with module support, you'd better
type mkinitramfs VERSION, where VERSION is the name of the modules
directory in /lib/modules.
Actually, the text in the BLFS page is somewhat misleading: When not
specifying VERSION, you do not include
the kernel modules in the initramfs at all, so chances are that it
does not work if your kernel has modules.
I don't have any kernel modules. I need the initramfs only for the UUIDs
I didn't created the the init.in. Didn't see that part. Here my new log
from mkinitramfs:
root:/# mkinitramfs
Creating initrd.img-no-kmods... cp: Aufruf von stat f�r
�/etc/udev/udev.conf� nicht m�glich: Datei oder Verzeichnis nicht
gefunden
done.
root:/#
I still get the same error. (WHY?!) Regards Sven
Well,
You shouldn't...
Have you copied the new initrd to /boot ?
One thing is sure. If /init is found and executed in the initramfs,
then an error could still occur, but should be different.
One possibility is:
Something got wrong when creating the initrd (including not copying it),
and the kernel rejects it because it is malformed.
In this case, the kernel continues without the initrd
and fails as before. You may see an error message
about the initrd if you are able
to scroll back the console with shift-PgUp.
Regards
Pierre
I really copied it, see:
root:/# mkinitramfs
Creating initrd.img-no-kmods... cp: Aufruf von stat f�r
�/etc/udev/udev.conf� nicht m�glich: Datei oder Verzeichnis nicht gefunden
done.
root:/# rm /boot/initrd.img-no-kmods #delete the old initramfs
root:/# mv initrd.img-no-kmods /boot/
root:/# ls /boot/
config-3.5.2 initrd.img-no-kmods System.map-3.5.2 vmlinuz-3.5.2-lfs-7.2
root:/#
and the worst i can't scroll back.
Regards
Sven
One thing you could try for debugging, but you have to get the mapping
between the german and the US keyboard: when the grub menu appears type
c. You are dropped to the grub shell, which allows to type commands
manually. You can use command completion (TAB lists the possibilities
you have)
Try:
set root=(hd0,mosdos4)
linux /boot/vmlinuz-3.5.2-lfs-7.2
root=UUID=4f9f6834-c55b-492e-a70c-4e3bca952f5b ro
initrd /boot/initrd.img-no-kmods
boot
If you have no error so far, it means you have a well formed initrd and
kernel. If it still does not boot, then it means you are missing some
Re: [lfs-support] booting don't work with UUIDs
Le 30/01/2013 15:55, Sven Bartscher a écrit :
Am 29.01.2013 22:02, schrieb Pierre Labastie:
Le 29/01/2013 13:42, Sven Bartscher a écrit :
Am 23.01.2013 18:03, schrieb Bruce Dubbs:
Sven Bartscher wrote:
hey guys!
I didn't installed GRUB in the chapter 8 and configured my already
installed GRUB
That's OK.
with writing the following text in the /boot/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,msdos4) #i tried it with set root=(hd0,4) too
menuentry GNU/Linux, Linux 3.5.2-lfs-7.2 {
linux /boot/vmlinuz-3.5.2-lfs-7.2
root=UUID=4f9f6834-c55b-492e-a70c-4e3bca952f5b ro
}
The kernel doesn't understand UUIDs. You need an initrd. See BLFS
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/initramfs.html
-- Bruce
I can't use the /dev/sdxy partition names because i have two hard
drives
(IDE and SATA) and the names are after rebooting randomly mixed. So i
can't be sure which is the right /dev/sdxy file.
I try to boot my new lfs system and it don't work instead i get this
message (a little bit more but i think this is the important part):
VFS: Cannot open root device
UUID=4f9f6834-c55b-492e-a70c-4e3bca952f5b
or unknown-block(0,0): error -6
Please append a correct root= boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
I don't use an extra /boot partition so i have two /boot folders
one on
my Ubuntu(containing GRUB and the Ubuntu kernel) partition and one
on my
LFS (containing the LFS kernel) partition can this work?
Can i even use UUIDs for lfs?
Did i anything else wrong?
my host system: Ubuntu 12.10
my lfs version 7.2
I have created an initramfs. Here the log:
root:/# mkinitramfs
Creating initrd.img-no-kmods... cp: Aufruf von stat f�r
�/etc/udev/udev.conf� nicht m�glich: Datei oder Verzeichnis nicht
gefunden
install: Aufruf von stat f�r �/usr/share/mkinitramfs/init.in� nicht
m�glich: Datei oder Verzeichnis nicht gefunden
done.
root:/#
I do not understand german, but I have played a lot with mkinitramfs,
So I think you got 2 file not found errors.
The first one (/etc/udev/udev.conf) is harmless, and always occurs
with modern udev.
The second one might be the explanation to your problem:
init.in is renamed to init in the initramfs, and is the heart of the
initramfs system.
If it is not there, nothing can work.
Haven't you overlooked the second part of the mkinitramfs installation
(cat /usr/share/mkinitramfs/init.in EOF)?
Also, if you compiled the kernel with module support, you'd better
type mkinitramfs VERSION, where VERSION is the name of the modules
directory in /lib/modules.
Actually, the text in the BLFS page is somewhat misleading: When not
specifying VERSION, you do not include
the kernel modules in the initramfs at all, so chances are that it
does not work if your kernel has modules.
I don't have any kernel modules. I need the initramfs only for the UUIDs
I didn't created the the init.in. Didn't see that part. Here my new log
from mkinitramfs:
root:/# mkinitramfs
Creating initrd.img-no-kmods... cp: Aufruf von stat f�r
�/etc/udev/udev.conf� nicht m�glich: Datei oder Verzeichnis nicht gefunden
done.
root:/#
I still get the same error. (WHY?!) Regards Sven
Well,
You shouldn't...
Have you copied the new initrd to /boot ?
One thing is sure. If /init is found and executed in the initramfs,
then an error could still occur, but should be different.
One possibility is:
Something got wrong when creating the initrd (including not copying it),
and the kernel rejects it because it is malformed.
In this case, the kernel continues without the initrd
and fails as before. You may see an error message
about the initrd if you are able
to scroll back the console with shift-PgUp.
Regards
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] booting don't work with UUIDs
Le 29/01/2013 13:42, Sven Bartscher a écrit :
Am 23.01.2013 18:03, schrieb Bruce Dubbs:
Sven Bartscher wrote:
hey guys!
I didn't installed GRUB in the chapter 8 and configured my already
installed GRUB
That's OK.
with writing the following text in the /boot/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,msdos4) #i tried it with set root=(hd0,4) too
menuentry GNU/Linux, Linux 3.5.2-lfs-7.2 {
linux /boot/vmlinuz-3.5.2-lfs-7.2
root=UUID=4f9f6834-c55b-492e-a70c-4e3bca952f5b ro
}
The kernel doesn't understand UUIDs. You need an initrd. See BLFS
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/initramfs.html
-- Bruce
I can't use the /dev/sdxy partition names because i have two hard drives
(IDE and SATA) and the names are after rebooting randomly mixed. So i
can't be sure which is the right /dev/sdxy file.
I try to boot my new lfs system and it don't work instead i get this
message (a little bit more but i think this is the important part):
VFS: Cannot open root device UUID=4f9f6834-c55b-492e-a70c-4e3bca952f5b
or unknown-block(0,0): error -6
Please append a correct root= boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
I don't use an extra /boot partition so i have two /boot folders one on
my Ubuntu(containing GRUB and the Ubuntu kernel) partition and one on my
LFS (containing the LFS kernel) partition can this work?
Can i even use UUIDs for lfs?
Did i anything else wrong?
my host system: Ubuntu 12.10
my lfs version 7.2
I have created an initramfs. Here the log:
root:/# mkinitramfs
Creating initrd.img-no-kmods... cp: Aufruf von stat f�r
�/etc/udev/udev.conf� nicht m�glich: Datei oder Verzeichnis nicht gefunden
install: Aufruf von stat f�r �/usr/share/mkinitramfs/init.in� nicht
m�glich: Datei oder Verzeichnis nicht gefunden
done.
root:/#
I do not understand german, but I have played a lot with mkinitramfs,
So I think you got 2 file not found errors.
The first one (/etc/udev/udev.conf) is harmless, and always occurs with
modern udev.
The second one might be the explanation to your problem:
init.in is renamed to init in the initramfs, and is the heart of the
initramfs system.
If it is not there, nothing can work.
Haven't you overlooked the second part of the mkinitramfs installation
(cat /usr/share/mkinitramfs/init.in EOF)?
Also, if you compiled the kernel with module support, you'd better type
mkinitramfs VERSION, where VERSION is the name of the modules directory
in /lib/modules.
Actually, the text in the BLFS page is somewhat misleading: When not
specifying VERSION, you do not include
the kernel modules in the initramfs at all, so chances are that it does
not work if your kernel has modules.
and installed cpio. Here my new grub.cfg menuentry for LFS:
menuentry GNU/Linux, Linux 3.5.2-lfs-7.2 {
insmod ext2
insmod part_msdos #Is this necessary? I have an msdos partition table
set root=(hd0,msdos4)
linux /boot/vmlinuz-3.5.2-lfs-7.2
root=UUID=4f9f6834-c55b-492e-a70c-4e3bca952f5b ro
initrd /boot/initrd.img-no-kmods
}
I get still the same Error.
I guess your mailer inserted a newline: of course the root= must be on
the same line as linux /boot...
Regards
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Unable to build File-5.11
Le 19/01/2013 09:04, Rabi Shanker Guha a écrit : Yes I Ctrl+C'ed it but thats because it got stuck after checking for gzopen in -lz... yes and it remained in that state for almost 30 mins and I can confirm there wasnt any config.status generated. Have you tried again (after untarring a fresh build directory)? If it still gets stuck (normally, the config.status lines appear almost immediatly), stop it again, and check whether you have the file configcache, which is an intermediate file. If you do not, it might be that somehow, you do not have right to create files in the build directory, although I doubt that it is a permission problem, since configure creates a lot of temporary conftest files. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Unable to build File-5.11
Le 19/01/2013 11:40, Rabi Shanker Guha a écrit : I've tried again: rm -rf file-5.11 tar xvf file-5.11.tar.gz cd file-5.11 ./configure --prefix=/usr Gets stuck again. And yes the confcache file is there. I guess its the same as configcache right? Yes, you are right, sorry. I would try first what WIlliam told you. If that fails, there might be some indication where it stops in the confcache file. Sincerely Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Sanity checks in 6.10
Le 18/01/2013 10:21, Philippe Delavalade a écrit : Hi. I have a new problem in the svn-10094 build, When performing sanity checks in 6.10. The command grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g' gives as output SEARCH_DIR(/usr/lib) SEARCH_DIR(/lib); The book, says I should have these lines but also the line SEARCH_DIR(/tools/i686-pc-linux-gnu/lib) What is going round ? I had a problem in chapter 5 with check-0.9.9 due to a problem with glibc and debian/testing that Pierre Labastie help me to resolve. Maybe some consequence of this ? Thanks for help. I too do not have /tools/... On x86_64, I have:SEARCH_DIR(/usr/x86_64-unknown-linux-gnu/lib64) SEARCH_DIR(/usr/local/lib64) SEARCH_DIR(/lib64) SEARCH_DIR(/usr/lib64) SEARCH_DIR(/usr/x86_64-unknown-linux-gnu/lib) SEARCH_DIR(/usr/local/lib) SEARCH_DIR(/lib) SEARCH_DIR(/usr/lib); I can tell you it is enough. I have built a KDE desktop with this configuration. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Unable to build File-5.11
Le 18/01/2013 20:55, Rabi Shanker Guha a écrit : Hello, Im building the LFS system. However I seem to be stuck on section 6.12 (Installing File 5.11) When I run ./configure --prefix=/usr, the configure script stops after the following lines: checking for strlcpy... no checking for strlcat... no checking for getline... yes checking for gzopen in -lz... yes Those are normally the last line of the checking part. Then should come the config.status part: configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating magic/Makefile config.status: creating tests/Makefile config.status: creating doc/Makefile config.status: creating python/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands and that's it... According to config.log, you had to interrupt the script (signal 2), hadn't you? Or did you inadvertently type Ctrl-C? Another possibility is that you typed Ctrl-S (this stops output). I have no idea why configure would stop before creating config.status. Regards pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Psmisc-22.19 section 6.23 problem
Le 17/01/2013 09:53, Israel Silberg a écrit : Hi all, I'm working on LFS 7.2 and in section 6.23 in the ./configure of Psmisc-22.19 I got the following error [...] checking for tgetent in -lncurses... no checking for tgetent in -ltermcap... no configure: error: Cannot find tinfo, ncurses or termcap libraries ncurses was compiled and installed without any errors. How can I solve the problem? Israel Hi, I have checking for tgetent in -ltinfo... no checking for tgetent in -lncurses... yes. SO it seems that something got wrong during the installation of ncurses. There are a bunch of instructions at the end of ncurses installation, which move libraries around and create some links. If you do not automate the build, it is very easy to forget one of those instructions. Usually the kind of error you are seeing comes from one of the ncurses links or libraries not being at the right place. Another possibility is that you exited chroot and forgot to reenter. What are the results of ls -l /lib/*curses* and ls -l /usr/lib/*curses* (in chroot)? Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Psmisc-22.19 section 6.23 problem
Le 17/01/2013 13:50, Israel Silberg a écrit : lrwxrwxrwx 1 root root 17 Jan 17 08:42 /usr/lib/libncurses.so.5 - libncurses.so.5.9 -rwxr-xr-x 1 root root 328441 Jan 17 08:42 /usr/lib/libncurses.so.5.9 Those should not be in /usr/lib, only in /lib. They have been removed by the command: mv -v /usr/lib/libncursesw.so.5* /lib I do not know whether that explains the error, though. If removing the files does not help, you could try digging into the config.log file. Sometimes, the error messages are more explicit. Also, try cat /usr/lib/libncurses.so (should give INPUT(-lncursesw)) cat /usr/lib/libcursesw.so (should give INPUT(-lncursesw)) Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Psmisc-22.19 section 6.23 problem
Le 17/01/2013 13:50, Israel Silberg a écrit :
root:/sources/psmisc-22.19# ls -l /lib/*curses*
lrwxrwxrwx 1 root root 18 Jan 17 08:31 /lib/libncursesw.so.5 -
libncursesw.so.5.9
-rwxr-xr-x 1 root root 394184 Jan 17 08:31 /lib/libncursesw.so.5.9
root:/sources/psmisc-22.19# ls -l /usr/lib/*curses*
lrwxrwxrwx 1 root root 12 Jan 17 08:39 /usr/lib/libcurses.a -
libncurses.a
lrwxrwxrwx 1 root root 13 Jan 17 08:38 /usr/lib/libcurses.so -
libncurses.so
lrwxrwxrwx 1 root root 13 Jan 17 08:38 /usr/lib/libcursesw.a -
libncursesw.a
-rw-r--r-- 1 root root 18 Jan 17 08:37 /usr/lib/libcursesw.so
lrwxrwxrwx 1 root root 15 Jan 17 08:35 /usr/lib/libncurses++.a -
libncurses++w.a
-rw-r--r-- 1 root root 131800 Jan 17 08:31 /usr/lib/libncurses++w.a
lrwxrwxrwx 1 root root 13 Jan 17 08:35 /usr/lib/libncurses.a -
libncursesw.a
-rw-r--r-- 1 root root 17 Jan 17 08:35 /usr/lib/libncurses.so
lrwxrwxrwx 1 root root 17 Jan 17 08:42 /usr/lib/libncurses.so.5 -
libncurses.so.5.9
-rwxr-xr-x 1 root root 328441 Jan 17 08:42 /usr/lib/libncurses.so.5.9
-rw-r--r-- 1 root root 554100 Jan 17 08:31 /usr/lib/libncursesw.a
lrwxrwxrwx 1 root root 26 Jan 17 08:32 /usr/lib/libncursesw.so -
../../lib/libncursesw.so.5
Adding to my previous message:
It seems that the libraries in /lib are older than the same libraries in
/usr/lib. It looks like you rebuilt the package or you typed make
install again after finishing the files moving and linking.
I am not sure what the consequences may be, but I would try something like
rm /lib/*curses* /usr/lib/{*curses*, libform*, libpanel*, libmenu*}
and build ncurses again.
Good luck
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Psmisc-22.19 section 6.23 problem
Le 17/01/2013 19:26, Israel Silberg a écrit :
On Thu, Jan 17, 2013 at 3:31 PM, Pierre Labastie
pierre.labas...@neuf.fr mailto:pierre.labas...@neuf.fr wrote:
Le 17/01/2013 13:50, Israel Silberg a écrit :
root:/sources/psmisc-22.19# ls -l /lib/*curses*
lrwxrwxrwx 1 root root 18 Jan 17 08:31 /lib/libncursesw.so.5 -
libncursesw.so.5.9
-rwxr-xr-x 1 root root 394184 Jan 17 08:31 /lib/libncursesw.so.5.9
root:/sources/psmisc-22.19# ls -l /usr/lib/*curses*
lrwxrwxrwx 1 root root 12 Jan 17 08:39 /usr/lib/libcurses.a -
libncurses.a
lrwxrwxrwx 1 root root 13 Jan 17 08:38 /usr/lib/libcurses.so -
libncurses.so
lrwxrwxrwx 1 root root 13 Jan 17 08:38 /usr/lib/libcursesw.a -
libncursesw.a
-rw-r--r-- 1 root root 18 Jan 17 08:37 /usr/lib/libcursesw.so
lrwxrwxrwx 1 root root 15 Jan 17 08:35
/usr/lib/libncurses++.a -
libncurses++w.a
-rw-r--r-- 1 root root 131800 Jan 17 08:31 /usr/lib/libncurses++w.a
lrwxrwxrwx 1 root root 13 Jan 17 08:35 /usr/lib/libncurses.a -
libncursesw.a
-rw-r--r-- 1 root root 17 Jan 17 08:35 /usr/lib/libncurses.so
lrwxrwxrwx 1 root root 17 Jan 17 08:42
/usr/lib/libncurses.so.5 -
libncurses.so.5.9
-rwxr-xr-x 1 root root 328441 Jan 17 08:42
/usr/lib/libncurses.so.5.9
-rw-r--r-- 1 root root 554100 Jan 17 08:31 /usr/lib/libncursesw.a
lrwxrwxrwx 1 root root 26 Jan 17 08:32
/usr/lib/libncursesw.so -
../../lib/libncursesw.so.5
Adding to my previous message:
It seems that the libraries in /lib are older than the same
libraries in
/usr/lib. It looks like you rebuilt the package or you typed make
install again after finishing the files moving and linking.
I am not sure what the consequences may be, but I would try
something like
rm /lib/*curses* /usr/lib/{*curses*, libform*, libpanel*, libmenu*}
and build ncurses again.
Good luck
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Hi Pierre,
I did the cat from the first answer, and got for the second file a
reply that looks like a binary file.
That shouldn't happen. The binary is removed by:
rm -vf /usr/lib/libcursesw.so
and then replaced by a text file:
echo INPUT(-lncursesw) /usr/lib/libcursesw.so
notice that there is no n in the name of that file.
Aout the timing of the files, I complied the package at 8:31 and the
rest are around 8:40-42 because I'm doing the LFS beside other things
so it takes me a few minutes to see that a step is finished and to
proceed to the next step.
Actually, I just realize that I made a mistake about the filenames
(that's easy, with all the variations). The files installed at 8:42 have
no w at the end.
But I think they shouldn't be there. I do not have them. You can try to
remove them and configure psmisc again. But something is wrong with
ncurses and I advise you to rebuild it from the beginning. Then
util-linux too, because it might have been linked to the wrong library.
Regards
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Psmisc-22.19 section 6.23 problem
Le 17/01/2013 21:35, Pierre Labastie a écrit : Aout the timing of the files, I complied the package at 8:31 and the rest are around 8:40-42 because I'm doing the LFS beside other things so it takes me a few minutes to see that a step is finished and to proceed to the next step. Actually, I just realize that I made a mistake about the filenames (that's easy, with all the variations). The files installed at 8:42 have no w at the end. But I think they shouldn't be there. I do not have them. You can try to remove them and configure psmisc again. But something is wrong with ncurses and I advise you to rebuild it from the beginning. Then util-linux too, because it might have been linked to the wrong library. Please forget that last part of my message. You built the non wide character library, as per the note at the bottom of the page. I think this has not been tested for a while, because it is not needed. I'll test if it explains psmisc failure. Please try removing or renaming the 2 files (if you do not want to erase them): libncurses.so.5 and libncurses.so.5.9 (without w, but with a n). And try psmisc again. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Psmisc-22.19 section 6.23 problem
Le 17/01/2013 21:47, Pierre Labastie a écrit : Le 17/01/2013 21:35, Pierre Labastie a écrit : Aout the timing of the files, I complied the package at 8:31 and the rest are around 8:40-42 because I'm doing the LFS beside other things so it takes me a few minutes to see that a step is finished and to proceed to the next step. Actually, I just realize that I made a mistake about the filenames (that's easy, with all the variations). The files installed at 8:42 have no w at the end. But I think they shouldn't be there. I do not have them. You can try to remove them and configure psmisc again. But something is wrong with ncurses and I advise you to rebuild it from the beginning. Then util-linux too, because it might have been linked to the wrong library. Please forget that last part of my message. You built the non wide character library, as per the note at the bottom of the page. I think this has not been tested for a while, because it is not needed. I'll test if it explains psmisc failure. Just checked. No it doesn't... If you have still the psmisc build dir, could you look at config.log where it says checking for tgetent in -lncurses There should be an error message just after the next command (gcc -o conftest -g -O2 conftest.c -lncurses 5). What does it say? Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
