Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
At last I reached chapter 8.4 of LFS 7.3-rc1...Up to this there is no error at all. But as per the book suggestion
"In order for the procedure below to work, you need to jump ahead to BLFS and install xorriso from the libisoburn package."
I got "libisoburn-1.2.6" package and when I tried to configure and install inside Chroot environment I got error
root:/sources/libisoburn-1.2.6# ./configure --prefix=/usr --disable-static &&
> make
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGE_FILES value needed for large files... no
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for fseeko... yes
checking for fseeko... (cached) yes
checking for iconv() in separate -liconv ... no
checking for libiconv in -liconv... no
checking for const qualifier with iconv() ... no
checking for a sed that does not truncate output... /bin/sed
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for a BSD-compatible install... /usr/bin/install -c
checking target operating system... linux
checking for overridden pkgconfig directory path... no
checking for desired functions in libreadline... yes
checking sys/acl.h usability... no
checking sys/acl.h presence... no
checking for sys/acl.h... no
checking attr/xattr.h usability... no
checking attr/xattr.h presence... no
checking for attr/xattr.h... no
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for compressBound in -lz... yes
checking libjte/libjte.h usability... no
checking libjte/libjte.h presence... no
checking for libjte/libjte.h... no
enabled xorriso external filter programs
disabled xorriso external filter programs under setuid
enabled xorriso command -launch_frontend
disabled xorriso command -launch_frontend under setuid
disabled xorriso write size default 64 KB on DVD and BD
enabled strict symbol encapsulation
checking libburn/libburn.h usability... no
checking libburn/libburn.h presence... no
checking for libburn/libburn.h... no
checking libisofs/libisofs.h usability... no
checking libisofs/libisofs.h presence... no
checking for libisofs/libisofs.h... no
checking for LIBBURN... skipped, no --enable-pkg-check-modules
checking for LIBISOFS... skipped, no --enable-pkg-check-modules
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/doxygen.conf
config.status: creating version.h
config.status: creating libisoburn-1.pc
config.status: executing depfiles commands
depbase=`echo libisoburn/burn_wrap.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`; \
if /bin/sh ./libtool --silent --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"libisoburn\" -DPACKAGE_TARNAME=\"libisoburn\" -DPACKAGE_VERSION=\"1.2.6\" -DPACKAGE_STRING=\"libisoburn\ 1.2.6\" -DPACKAGE_BUGREPORT=\"http://libburnia-project.org\" -DPACKAGE=\"libisoburn\" -DVERSION=\"1.2.6\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D_FILE_OFFSET_BITS=64 -DHAVE_FSEEKO=1 -DICONV_CONST= -DHAVE_DLFCN_H=1 -DHAVE_LIBZ=1 -I. -I. -DXorriso_with_readlinE -DXorriso_allow_external_filterS -DXorriso_allow_launch_frontenD -DLibisofs_with_zliB -DDEBUG -g -pedantic -Wall -Wextra -Wno-unused-parameter -g -O2 -MT libisoburn/burn_wrap.lo -MD -MP -MF "$depbase.Tpo" -c -o libisoburn/burn_wrap.lo libisoburn/burn_wrap.c; \
then mv -f "$depbase.Tpo" "$depbase.Plo"; else rm -f "$depbase.Tpo"; exit 1; fi
libisoburn/burn_wrap.c:36:29: fatal error: libburn/libburn.h: No such file or directory
compilation terminated.
make: *** [libisoburn/burn_wrap.lo] Error 1
but as per the earlier procedure I log out from root account and I tried the same procedure by normal lfs user, unfortunately I got error again
lfs@boss:/media/LinuxFromScratch/sources$ tar -xf libisoburn-1.2.6.tar.gz
lfs@boss:/media/LinuxFromScratch/sources$ cd libisoburn-1.2.6
lfs@boss:/media/LinuxFromScratch/sources/libisoburn-1.2.6$ ls
AUTHORS INSTALL acinclude.m4 config.sub frontend missing xorriso
CONTRIBUTORS Makefile.am aclocal.m4 configure install-sh releng
COPYING Makefile.in bootstrap configure.ac libisoburn test
COPYRIGHT README compile depcomp libisoburn-1.pc.in texinfo.tex
ChangeLog TODO config.guess doc ltmain.sh version.h.in
lfs@boss:/media/LinuxFromScratch/sources/libisoburn-1.2.6$ ./configure --prefix=/usr --disable-static &&
> make
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /tools/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
I can't understand both errors, Please Help me in this...
Is that mandatory to install this package before configuring GRUB????
No it,s not mandatory that is if you cant boot your lfs from grub.
If you can get back into lfs from a live cd that will do,
If you were to overwrite your host bootloader that is what you would use.
Hi
I have never used this as I have live cd around so I can boot into the systems from it, I would of thought your host came on a cd which is proberly a live cd
FYI the version check is more needed at the begining of the build you way past that but thks for noticing.
And FYI I am not using any live cd...I just building a LFS in seperate partition.
First, most of us here are well aware of what the book says regarding installing libisoburn and creating a boot disk before installing GRUB. But what spiky0011 meant (I believe) is that one alternative to doing that step in the book is to create one of the well-known live CDs already in existence and available for download (such as Knoppix, System Rescue CD, or one of the distro live CDs, etc.). In other words, the libisoburn step is only there to provide a way to boot your computer in case you bust its boot loader installing GRUB in your LFS system (it happens all the time), and there are other ways to obtain a boot disk without diverting your efforts to libisoburn at this time. Of course do what you think is best, but I never do that boot disk step in the LFS book because I already possess about dozen disks that are capable of emergency booting my computer.
Tell me precautions step, to take before doing all the stuff..
FYI, my laptop holds MS Windows 7, with LINUX (kernels 2.6.32, 2.6.36, 3.7.8) and I builded all LFS system in a new partition of my hard drive.
I will approciate if any one direct (suggest) me to take correct decision.
Even this lines are horrible to me
" Warning
The following command will overwrite the current boot loader. Do not run the command if this is not desired, for example, if using a third party boot manager to manage the Master Boot Record (MBR).
Yes what you have put will overwrite the grub which is installed by your host.
What you need to do is boot back into your host system CAN YOU LET US WHICH HOST, Then you will have to update grub from there. The host grub should identify lfs.
As per your advice I updated my grub from there but it is not detecting my LFS there, It is normally updating with the earlier settings.
see this
cot@boss:~$ sudo update-grub
Generating grub.cfg ...
Found background image: boss-grub.png
Found linux image: /boot/vmlinuz-3.7.8-pimpi3
Found initrd image: /boot/initrd.img-3.7.8-pimpi3
Found linux image: /boot/vmlinuz-3.7.8-pimpi3.old
Found initrd image: /boot/initrd.img-3.7.8-pimpi3
Found linux image: /boot/vmlinuz-2.6.39-bpo.2-686-pae
Found initrd image: /boot/initrd.img-2.6.39-bpo.2-686-pae
Found linux image: /boot/vmlinuz-2.6.32-5-686
Found initrd image: /boot/initrd.img-2.6.32-5-686
done
even I created a script at /etc/grub.d/ inside my LFS partition, but none works for me
FYI, my laptop is dual boot, which holds windows 7, and linux (with more than one kernel), I builded LFS at seperate partition(which can be mounted in my system).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.