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.
The 2nd you stopped the make -k check before it finished "Why"
because, in procces make -k check take a long long time, and in my screen terminal full of FAIL. so, I stoped before finish.
I don't want to waiting procces.
There isn't much information present that can help in pinpointing the problem.
I did notice that the problem arrises from the very first test that is run (quote is from the gcc test.log):
Code:
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /tools/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /tools/share/dejagnu/config/unix.exp as generic interface file for target.
Using /sources/gcc-4.7.2/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /sources/gcc-4.7.2/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
This clearly indicates a problem. The reason might be a mistake in the gcc chapter, but could also indicate an earlier problem.
You might want to start with re-doing the gcc chapter (do fully remove the gcc-4.7.2 and gcc-build directory first!). Once the ../gcc-4.7.2/configure --prefix=/usr ..... step finishes make sure it was executed successfully and have a look at the config.log that was created.
If you are sure the config step was executed successfully, run the make step and also check if this runs smoothly.
You can check here (LFS test log) to see if the output generated by the make -k check step is the same as yours.
If you do post any information please include the command itself as well, just dumping (part of?) the output created by a command doesn't help.
Also post the lines just before the error appears (posting all the FAIL: gcc.c-torture/comp lines is great but what about the first few lines before the first FAIL lines).
Quote:
Originally Posted by potterius
because, in procces make -k check take a long long time, and in my screen terminal full of FAIL. so, I stoped before finish. I don't want to waiting procces.
Yes, it does take a long time. 53.5 SBU's to be exact, which makes this the package with the longest build time. You do need to be patient.
I've mentioned this in one of your other threads already, but it might be worth repeating: After the earlier problems you've had in chapter 6 You might want to consider removing all, restoring the backup made in chapter 5.34 and start fresh with chapter 6.
There isn't much information present that can help in pinpointing the problem.
I did notice that the problem arrises from the very first test that is run (quote is from the gcc test.log):
Code:
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /tools/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /tools/share/dejagnu/config/unix.exp as generic interface file for target.
Using /sources/gcc-4.7.2/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /sources/gcc-4.7.2/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
This clearly indicates a problem. The reason might be a mistake in the gcc chapter, but could also indicate an earlier problem.
You might want to start with re-doing the gcc chapter (do fully remove the gcc-4.7.2 and gcc-build directory first!). Once the ../gcc-4.7.2/configure --prefix=/usr ..... step finishes make sure it was executed successfully and have a look at the config.log that was created.
If you are sure the config step was executed successfully, run the make step and also check if this runs smoothly.
You can check here (LFS test log) to see if the output generated by the make -k check step is the same as yours.
If you do post any information please include the command itself as well, just dumping (part of?) the output created by a command doesn't help.
Also post the lines just before the error appears (posting all the FAIL: gcc.c-torture/comp lines is great but what about the first few lines before the first FAIL lines).
Yes, it does take a long time. 53.5 SBU's to be exact, which makes this the package with the longest build time. You do need to be patient.
I've mentioned this in one of your other threads already, but it might be worth repeating: After the earlier problems you've had in chapter 6 You might want to consider removing all, restoring the backup made in chapter 5.34 and start fresh with chapter 6.
this is a output make -k check before line FAIL.
Code:
root:/sources/gcc-build# make -k check
make[1]: Entering directory `/sources/gcc-build'
make[2]: Entering directory `/sources/gcc-build/fixincludes'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/sources/gcc-build/fixincludes'
make[2]: Entering directory `/sources/gcc-build/gcc'
Making a new config file...
echo "set tmpdir /sources/gcc-build/gcc/testsuite" >> ./site.tmp
make[3]: Entering directory `/sources/gcc-build/gcc'
test -d plugin || mkdir plugin
test -d testsuite || mkdir testsuite
test -d testsuite/gcc || mkdir testsuite/gcc
(rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd ../../gcc-4.7.2/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
cd testsuite/gcc; \
rm -f tmp-site.exp; \
sed '/set tmpdir/ s|testsuite$|testsuite/gcc|' \
< ../../site.exp > tmp-site.exp; \
/bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
EXPECT=`if [ -f ${rootme}/../expect/expect ] ; then echo ${rootme}/../expect/expect ; else echo expect ; fi` ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ; \
export TCL_LIBRARY ; fi ; \
runtestflags= ; \
if [ -n "" ] ; then \
runtestflags=""; \
elif [ -n "" ] ; then \
parts="`echo ' ' \
| sed 's/=[^ ]* / /g'`"; \
for part in `find $srcdir/testsuite/gcc* -name \*.exp` ; do \
part=`basename $part` ; \
case " $parts $runtestflags " in \
*" $part "*) ;; \
*) runtestflags="$runtestflags $part" ;; \
esac ; \
done ; \
fi ; \
`if [ -f ${srcdir}/../dejagnu/runtest ] ; then echo ${srcdir}/../dejagnu/runtest ; else echo runtest; fi` --tool gcc $runtestflags)
WARNING: Couldn't find the global config file.
Test Run By root on Wed May 8 09:33:02 2013
Native configuration is i686-pc-linux-gnu
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /tools/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /tools/share/dejagnu/config/unix.exp as generic interface file for target.
Using /sources/gcc-4.7.2/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /sources/gcc-4.7.2/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
FAIL: gcc.c-torture/compile/20000105-1.c -O0 (test for excess errors)
FAIL: gcc.c-torture/compile/20000105-1.c -O1 (test for excess errors)
FAIL: gcc.c-torture/compile/20000105-1.c -O2 (test for excess errors)
so, I should back to begining of chapter 6 right???
The most honest answer would be: Stop working on LFS and first get familiar with Linux (the command line, not the GUI).
I'm getting the impression that you don't really understand what is going on during the build and due to that all is reduced to a copy->paste routine. This will frustrate in the long run and you probably won't learn that much from the build.
root@rahmatariefhidayat:/home/potterius# bash version-check.sh
bash, version 4.2.37(1)-release
/bin/sh -> /bin/bash
Binutils: (GNU Binutils) 2.23.1
.
.
Texinfo: makeinfo (GNU texinfo) 4.13
xz (XZ Utils) 5.1.0alpha
/usr/bin/ld: this linker was not configured to use sysroots
collect2: error: ld returned 1 exit status
gcc compilation failed
I'm not sure why you post this at this point. Once you enter the chrooted environment in chapter 6, the build depends on the temporary environment build in chapter 5 and not the host.
The output shown isn't correct and I wonder why you were able to build chapter 5........
The most honest answer would be: Stop working on LFS and first get familiar with Linux (the command line, not the GUI).
I'm getting the impression that you don't really understand what is going on during the build and due to that all is reduced to a copy->paste routine. This will frustrate in the long run and you probably won't learn that much from the build.
I'm not sure why you post this at this point. Once you enter the chrooted environment in chapter 6, the build depends on the temporary environment build in chapter 5 and not the host.
The output shown isn't correct and I wonder why you were able to build chapter 5........
if I could, I would stop building LFS. but I could not. because this is a task was given to my lecturer. if I do not do this, I will get a E score.
when I start to build lfs, everythings gonna be fine. before I starting. I check bash version-check.sh and the result is ok.
Code:
bash, version 4.2.37(1)-release
/bin/sh -> /bin/dash
Binutils: (GNU Binutils for Ubuntu) 2.22.90.20120924
bison (GNU Bison) 2.5
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2, Version 1.0.6, 6-Sept-2010.
Coreutils: 8.13
diff (GNU diffutils) 3.2
find (GNU findutils) 4.4.2
GNU Awk 4.0.1
/usr/bin/awk -> /usr/bin/gawk
gcc (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2
(Ubuntu EGLIBC 2.15-0ubuntu20.1) 2.15
grep (GNU grep) 2.12
gzip 1.5
Linux version 3.5.0-28-generic (buildd@aatxe) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) ) #48-Ubuntu SMP Tue Apr 23 23:05:48 UTC 2013
m4 (GNU M4) 1.4.16
GNU Make 3.81
patch 2.6.1
Perl version='5.14.2';
GNU sed version 4.2.1
tar (GNU tar) 1.26
Texinfo: makeinfo (GNU texinfo) 4.13
xz (XZ Utils) 5.1.0alpha
gcc compilation OK
until on chapter 6.17 gcc, when error, I check bash version-check, and the result is gcc compilation failed
if I could, I would stop building LFS. but I could not. because this is a task was given to my lecturer. if I do not do this, I will get a E score.
That would suggest you should have the basic skills to build LFS (assuming you paid attention during the lectures ).
With the above in mind I would start from scratch if I were you. By now you should have a rough idea about how things are done which would make your second attempt somewhat easier. It also makes sure that earlier problems that might or might not have been fully resolved aren't an issue.
Quote:
until on chapter 6.17 gcc, when error, I check bash version-check, and the result is gcc compilation failed
very very confused...
You are confusing yourself. It doesn't say anywhere that the version check script is valid in chapter 6. It is provided to check your host and _not_ the (progress of the) LFS build.
Follow the book from page one, don't deviate and try to understand what is going to be done before you execute the command(s). If something doesn't work try to figure out why (check for typo's, check the generated output and the log files, is anything mentioned in the book, re-read the parts you might have misunderstood, etc).
That would suggest you should have the basic skills to build LFS (assuming you paid attention during the lectures ).
With the above in mind I would start from scratch if I were you. By now you should have a rough idea about how things are done which would make your second attempt somewhat easier. It also makes sure that earlier problems that might or might not have been fully resolved aren't an issue.
You are confusing yourself. It doesn't say anywhere that the version check script is valid in chapter 6. It is provided to check your host and _not_ the (progress of the) LFS build.
Follow the book from page one, don't deviate and try to understand what is going to be done before you execute the command(s). If something doesn't work try to figure out why (check for typo's, check the generated output and the log files, is anything mentioned in the book, re-read the parts you might have misunderstood, etc).
allright druuna, now I'm really-really sure to start again from beginning.
can you tell me how to remove all my partition from lfs?
because I was try to remove lfs directori on /mnt/lfs with rm -R lfs. cannot remove lfs directory. but directory on inside lfs directory succesful deleted.
can you tell me how to remove all my partition from lfs?
because I was try to remove lfs directori on /mnt/lfs with rm -R lfs. cannot remove lfs directory. but directory on inside lfs directory succesful deleted.
To remove the content of $LFS you need to do the following as root user:
Code:
rm -rf $LFS/
# or if you prefer and assuming LFS holds /mnt/lfs
rm -rf /mnt/lfs/
BTW: If this hasn't been part of the lectures you wrote about then you need to have a talk with your instructor. Your level of Linux experience isn't good enough to start a project like LFS at this point.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
).
