gmane.linux.lfs.support

Chapter 6.9 Glibc - glibc-2.17-fhs-1 patch

2013-05-23T14:11:54

The Systemd branch (snapshot SYSTEMD-20130504) of the book makes use of
glibc-2.17-fhs-1.patch to avoid a non FHS compliant directory.
Do you intend to use it in the main branch (SVN) too?

Klaus Wulff

passwd not waiting for prompt

Geoff Swan — 2013-05-23T00:04:17

An interesting problem appeared during an LFS 7.3 build after the build
and installation of shadow.
Everything appeared successful, however when trying to set the root
passwd it fails to prompt for the new passwd.
It simply shows the lines below (as if a CR was hit) and returns to the
prompt.

root:/sources# passwd root
Changing password for root
Enter the new password (minimum of 5 characters)
Please use a combination of upper and lower case letters and numbers.
Bad password: too short.
Warning: weak password (enter it again to use it anyway).
passwd: password changed.
root:/sources#

Any clues to further investigate this would be appreciated.

- Geoff

8.2. Creating the /etc/fstab File

Baho Utot — 2013-05-21T16:02:55

I found this error in the book....

It is possible to make the ext3 filesystem reliable across power 
failures for some hard disk types. To do this, add the barrier=1 mount 
option to the appropriate entry in /etc/fstab. To check if the disk 
drive supports this option, run hdparm on the applicable disk drive. For 
example, if:


The ext3 should be ext4 if this is the default for LFS should it not?

LFS-SVN ext4 partition

Baho Utot — 2013-05-19T21:22:45

I have always in the past used a ext3 partition on my LFS systems. I 
have changed to ext4 and on boot I get errors that are saying than it 
had problems mounting the partition due to unsupported  options, it has 
EXT3-fs in the first two error messages, the third message says it uses 
EXT4-fs and it then mounts without error.
I belive  it is coming from the kernel as it has a kernal time of [ 
1.568232].

Is this normal for the boot to try mount the root partition with EXT3-fs 
twice before then using EXT4-fs?

LFS7.3: zlib-1.2.7 download link is not availableanymore

Chunmeng Zhou — 2013-05-18T02:41:39

The zlib 1.2.7 download link (http://www.zlib.net/zlib-1.2.7.tar.bz2) is not
available anymore.

You can download it from sourceforge:
wget http://prdownloads.sourceforge.net/libpng/zlib-1.2.7.tar.bz2

It seems the developer released the latest zlib on Aprial 28th and moved all
the previous version to sourceforge.



Chun

Rename everything lfs/LFS -> unim/UNIM - chapter6.61. Udev-197, LFS 7.3

Sandy Widianto — 2013-05-17T20:03:51

Because of my project and my learning purpose, I renamed everything lfs/LFS
to unim/UNIM.
user/group:
lfs -> unim
on commands for everything, examples:
---------------
mkdir -v $UNIM/sources
chmod -v a+wt $UNIM/sources
mkdir -v $UNIM/tools
ln -sv $UNIM/tools /
groupadd unim
useradd -s /bin/bash -g unim -m -k /dev/null unim
passwd unim
chown -v unim $UNIM/tools
chown -v unim $UNIM/sources

cat > ~/.bashrc << "EOF"
set +h
umask 022
UNIM=/mnt/unim
LC_ALL=POSIX
UNIM_TGT=$(uname -m)-unim-linux-gnu
PATH=/tools/bin:/bin:/usr/bin
export UNIM LC_ALL UNIM_TGT PATH
EOF
-------------
mkdir -v $UNIM/{dev,proc,sys}
mknod -m 600 $UNIM/dev/console c 5 1
mknod -m 666 $UNIM/dev/null c 1 3
mount -v --bind /dev $UNIM/dev
mount -vt devpts devpts $UNIM/dev/pts
mount -vt proc proc $UNIM/proc
mount -vt sysfs sysfs $UNIM/sys

if [ -h $UNIM/dev/shm ]; then
  link=$(readlink $UNIM/dev/shm)
  mkdir -p $UNIM/$link
  mount -vt tmpfs shm $UNIM/$link
  unset link
else
  mount -vt tmpfs shm $UNIM/dev/shm
fi

-------------
chroot "$UNIM" /tools/bin/env -i \
    HOME=/root                  \
    TERM="$TERM"                \
    PS1='\u:\w\$ '              \
    PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
    /tools/bin/bash --login +h
----------------
Everything was went smoothly and now I'm at chapter 6.61. Udev-197
(Extracted from systemd-197) - LFS 7.3.
I think udev-lfs-197-2.tar.bz2 is special package for LFS, so should I
rename evrything inside the package to continue it?

I'm looking forward for support and thank you for your attention.

- Sandy Widianto -

why does LFS need that number of patches

alex lupu — 2013-05-16T21:08:08

Hi Aleksandar,

You wrote (excerpt):
I just went back to analyze the bug report and your fix that you
reported in the mail, and the only logical explanation is that your (or
any LFS') copy of db2html did something different than the developers
copy of db2html. If db2html is generated during the build procedure
(and it is apparently, since I seem to not have it my $PATH), then this
may be much more convoluted than just a simple version mismatch.
Bottom line: this is probably because you don't have something that the
developer has.

This is my (alex) reply:

Here is just a key excerpt of my original post:
<<
In desperation, I created a little note for myself to use on any
subsequent compilation (BLFS style) of a new GTK+ 2 version on
2011-03-08 (i.e., more than two years ago) which reads (FWIW):

# After untarring the package (_before_ configure)
sed -i "s/db2html gtk-faq.sgml/db2html \
 gtk-faq.sgml -o gtk-faq/" docs/faq/Makefile.in ; echo $?
sed -i "s/db2html gtk-tut.sgml/db2html \
 gtk-tut.sgml -o gtk-tut/" docs/tutorial/Makefile.in ; echo $?

Now, it so happens the BLFS instructions for GTK+-2.24.17 state
(as [late as] 2013-05-09):

Install GTK+ 2 by running the following commands:
sed -i 's#l \(gtk-.*\).sgml#& -o \1#' docs/{faq,tutorial}/Makefile.in
 ...

(sounds eerily similar to my Oct. 2010 beef, don't it?)

UNLESS I'm wrong (I didn't have time and energy to thoroughly compare
my original "patch" to BLFS's latest - and long standing - "patch",
so I MAY easily be wrong),
it appears that both me (as early as 2011-03-08) and the BLFS _world_
have hit the same problem in compiling any GTK+ 2 version (up to this day),
i.e., the original core of my post (presented in a little convoluted way, I
admit),
still stands:

How come there is such a technical difference between so many people
(me and all the BLFS aficionados) and the "developer" (or anybody in
that organization, for that matter)?

Why is that difference so critical and so our fault that we've just
taken it lying down all these years?

Thanks for your comments,

why does LFS need that number of patches

alex lupu — 2013-05-16T16:37:21

Am 16.5.2013 03:03, schrieb Stefan & Rebekka Wetter:

Good questions (as they say).  While trying to stay on topic,
I'll take the liberty and rephrase them to
 Why are patches needed at all?
for my post and try to answer/comment.

First, I agree with the previous respondents (patches are just needed,
some address the unique(?) configurations of (B)LFS, what would the
world be without them, just live with them etc.)

Now that so many celebrities have come out on this, I've decided
to finally break my own silence on this subject that had been obsessing
me for years.  I'll use a particular example but it's more general
(and possibly ugly, cover-up, sloppiness?, etc.) in nature.
For me, it all started on a dark and stormy night, while trying to
compile GTK+ 2.22.0 and failing.  It culminated in
Bug 631910 of 2010-10-11:
 https://bugzilla.gnome.org/show_bug.cgi?id=631910 (for the curious)

In case you're there, please observe (and absorb) the Comment #1
(and only) which quickly closed this "non" issue.
True or incompetence or cover-up, etc.?  I've obsessed on this ever since.

In desperation, I created a little note for myself to use on any
subsequent compilation (BLFS style) of a new GTK+ 2 version on
2011-03-08 (i.e., more than two years ago) which reads (FWIW):

# After untarring the package (_before_ configure)
sed -i "s/db2html gtk-faq.sgml/db2html \
 gtk-faq.sgml -o gtk-faq/" docs/faq/Makefile.in ; echo $?
sed -i "s/db2html gtk-tut.sgml/db2html \
 gtk-tut.sgml -o gtk-tut/" docs/tutorial/Makefile.in ; echo $?

Now, it so happens the BLFS instructions for GTK+-2.24.17 state
(as of 2013-05-09):

Install GTK+ 2 by running the following commands:
sed -i 's#l \(gtk-.*\).sgml#& -o \1#' docs/{faq,tutorial}/Makefile.in
 ...

(sounds eerily similar to my Oct. 2010 beef, don't it?)

So on this particular example (but much more widespread, as I said)
my obsessive question was (and still is):

How do some other people compile their package, and in what
configurations so that they are obviously NOT in need of an
LFS/BLFS style "patch"?
How? How?


I'd like to thank the issuers (husband and wife?) of and commentators
on this thread.  You really helped me lift a heavy burden off my chest,
a burden I had to keep inside for so many years.

Still obsessed and puzzled (evidently), but at peace with myself now,

why does LFS need that number of patches

Stefan & Rebekka Wetter — 2013-05-16T07:03:51

Hi,

in the lfs-book you need some patches. I wonder, why these patches are 
needed? Are the upstream-sources not able to be compiled without?

Thanks!

Best Regards
Stefan

LFS Stable errata gcc 4.8 hosts

William Harrington — 2013-05-15T21:54:11

Greetings,

Gcc stable is using gcc 4.7.2 and multiple users have encountered  
issues when using hosts with gcc 4.8 to build gcc 4.7.2 for LFS  
stable. I've hinted them to this bug: http://gcc.gnu.org/< at >/bugzilla/show_bug.cgi?id=56927

gcc 4.7.3 came out recently and fixes the issue.

Errata may be required. Users have replied with success after I"ve  
told them to update to gcc 4.7.3 during the LFS build.

That is only one bug url for that issue. There are more. This has  
cropped up multiple times and I'm giving a heads up on the issue.

Sincerely,

William Harrington

Specific Kernel configuration - LFS 7.3

Mic Ky — 2013-05-15T21:10:33

I'm building my LFS 7.3 with main purposes:
1. Live CD Xfce
2. English and Korean language interfaces
is there any specific kernel configuration for it?

Thank you for your attention.
       -- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Problem with xzless

Fernando — 2013-05-15T20:47:58

Apologies for sending to the wrong list.

# cat /etc/lfs-release
SVN-20130512
64bit, built with jhalfs

I am worried about this:

Either as normal user or as root:
env LANG=C xzless
/home/fernando/Downloads/blfs/links-2.7-2013.05.15-17h21m20s.log.xz

error message:
/usr/bin/xzless: line 49: test: 458 (POSIX regular expressions): integer
expression expected

(used env in order to get English message, but it appears in my locale
LANG too.)

Line 49 of xzless is:

if test "$(less -V | { read ver && echo ${ver#less }; })" -ge 429; then

I am thinking in reinstalling xz, but before, please, can someone give
me some advice?

Q: re. LFS 7.3 errata

Jeremy Henty — 2013-05-15T19:02:54

Quote:

    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.

Is it *always* safe to add --with-sysroot , no matter what your host
distro?  (My host is LFS-6.8 .)

Regards,

Jeremy Henty

remount commands after take a break

Mic Ky — 2013-05-12T07:13:53

I can't build LFS 7.3 at a time, I need to take a break and continue it at next day, so this is my commands to remount

-----------
mount -v --bind /dev $LFS/dev
mount -vt devpts devpts $LFS/dev/pts
mount -vt proc proc $LFS/proc
mount -vt sysfs sysfs $LFS/sys

if [ -h $LFS/dev/shm ]; then
  link=$(readlink $LFS/dev/shm)
  mkdir -p $LFS/$link
  mount -vt tmpfs shm $LFS/$link
  unset link
else
  mount -vt tmpfs shm $LFS/dev/shm
fi
-----------
Am I correct or there is more suitable command?
Thank you for you attention and support!
       -- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Adjusting the Toolchain - LFS 7.3

Mic Ky — 2013-05-11T22:49:55

hello I got problem on Chapter 6.10. Adjusting the Toolchain - LFS 7.3

according to the LFS 7.3 book, the result of this command
----------------------------
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
---------------------------
should be
---------------------
SEARCH_DIR("/tools/i686-pc-linux-gnu/lib")
SEARCH_DIR("/usr/lib")
SEARCH_DIR("/lib");
---------------------

but my result only 2 lines
----------
root:/# grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
SEARCH_DIR("/usr/lib")
SEARCH_DIR("/lib");
-----------
it is okay, or how to fix it?

Thank you for your attention and help!


       -- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS in pdf

Jean-Philippe MENGUAL — 2013-05-11T22:10:57

Hi,

I try to set an environment to generate pdf files for lfs. I installed
fop, jai and openjdk. I've not installed the dependencies of openjdk, and
not JUnit. make says:

Generating PDF file...
make: *** [pdf] Error 1

How can I have more verbose info? Do some dep are mandatory so build a pdf (I
mean openjdk's dep)? Is JUnit mandatory?

Thanks for your help

Regards

Glibc-2.17 errors at LFS 7.3

stud dent — 2013-05-10T17:58:19

Linux From Scratch - Version 7.3 Chapter 6. Installing Basic System Software - 6.9. Glibc-2.17 at Ubuntu LTS 12.04

Based on this words on LFS 7.3 Book
(Generally a few tests do not pass, but you can generally ignore any of the test failures listed below. Now test the build results:)
can I ignore this errors?

-------------------
/sources/glibc-build/begin-end-check.out
make[1]: Target `check' not remade because of errors.
make[1]: Leaving directory `/sources/glibc-2.17'
make: *** [check] Error 2
root:/sources/glibc-build# grep Error glibc-check-log
make[2]: *** [/sources/glibc-build/stdio-common/bug22.out] Error 1
make[1]: *** [stdio-common/tests] Error 2
make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored)
make[2]: [/sources/glibc-build/conform/run-conformtest.out] Error 1 (ignored)
make: *** [check] Error 2
root:/sources/glibc-build#
----------------------

By the way thank you for previous supports!
Best regard
       -- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

GCC tests error

Antony Vincent — 2013-05-10T15:52:22

Hi,

I tried to install gcc at the chapter 6. After the command: make -k check, I got this error:

=== libitm Summary ===

# of expected passes        26
# of expected failures        3
# of unsupported tests        1
make[4]: Leaving directory `/sources/gcc-build/x86_64-unknown-linux-gnu/libitm/testsuite'
make[3]: Leaving directory `/sources/gcc-build/x86_64-unknown-linux-gnu/libitm/testsuite'
make[3]: Entering directory `/sources/gcc-build/x86_64-unknown-linux-gnu/libitm'
true  DO=all multi-do # make
make[3]: Leaving directory `/sources/gcc-build/x86_64-unknown-linux-gnu/libitm'
make[2]: Leaving directory `/sources/gcc-build/x86_64-unknown-linux-gnu/libitm'
make[1]: Target `check-target' not remade because of errors.
make[1]: Leaving directory `/sources/gcc-build'
make: *** [do-check] Error 2
make: Target `check' not remade because of errors.

The results of the command ../gcc-4.7.2/contrib/test_summary are attached to this message.
I read the book version 7.3
 
Thanks!
Antony
       cat <<'EOF' |
LAST_UPDATED: Obtained from SVN: tags/gcc_4_7_2_release revision 191558

Native configuration is x86_64-unknown-linux-gnu

=== g++ tests ===


Running target unix
ERROR: g++.dg/abi/mangle33.C -std=c++98: error executing dg-final: couldn't compile regular expression pattern: out of memory
UNRESOLVED: g++.dg/abi/mangle33.C -std=c++98: error executing dg-final: couldn't compile regular expression pattern: out of memory
ERROR: g++.dg/abi/mangle33.C -std=c++11: error executing dg-final: couldn't compile regular expression pattern: out of memory
UNRESOLVED: g++.dg/abi/mangle33.C -std=c++11: error executing dg-final: couldn't compile regular expression pattern: out of memory

=== g++ Summary ===

# of expected passes48482
# of expected failures286
# of unresolved testcases2
# of unsupported tests555
/sources/gcc-build/gcc/testsuite/g++/../../g++  version 4.7.2 (GCC) 

=== gcc tests ===


Running target unix
XPASS: gcc.dg/inline_3.c (test for excess errors)
XPASS: gcc.dg/inline_4.c (test for excess errors)
XPASS: gcc.dg/unroll_2.c (test for excess errors)
XPASS: gcc.dg/unroll_3.c (test for excess errors)
XPASS: gcc.dg/unroll_4.c (test for excess errors)

=== gcc Summary ===

# of expected passes85669
# of unexpected successes5
# of expected failures258
# of unsupported tests1241
/sources/gcc-build/gcc/xgcc  version 4.7.2 (GCC) 

=== libgomp tests ===


Running target unix

=== libgomp Summary ===

# of expected passes1241
=== libitm tests ===


Running target unix

=== libitm Summary ===

# of expected passes26
# of expected failures3
# of unsupported tests1
=== libmudflap tests ===


Running target unix
FAIL: libmudflap.c++/pass55-frag.cxx ( -O) execution test
ERROR: tcl error sourcing /sources/gcc-4.7.2/libmudflap/testsuite/libmudflap.cth/cthfrags.exp.
ERROR: couldn't compile regular expression pattern: out of memory

=== libmudflap Summary ===

# of expected passes1255
# of unexpected failures1
=== libstdc++ tests ===


Running target unix
FAIL: 22_locale/time_get/get_weekday/char/38081-1.cc execution test
FAIL: 22_locale/time_get/get_weekday/char/38081-2.cc execution test

=== libstdc++ Summary ===

# of expected passes8888
# of unexpected failures2
# of expected failures43
# of unsupported tests153

Compiler version: 4.7.2 (GCC) 
Platform: x86_64-unknown-linux-gnu
configure flags: --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++ --disable-multilib --disable-bootstrap --with-system-zlib
EOF
Mail -s "Results for 4.7.2 (GCC) testsuite on x86_64-unknown-linux-gnu" gcc-testresults< at >gcc.gnu.org &&
mv /sources/gcc-build/./gcc/testsuite/g++/g++.sum /sources/gcc-build/./gcc/testsuite/g++/g++.sum.sent &&
mv /sources/gcc-build/./gcc/testsuite/gcc/gcc.sum /sources/gcc-build/./gcc/testsuite/gcc/gcc.sum.sent &&
mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.sum /sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.sum.sent &&
mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.sum /sources/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.sum.sent &&
mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.sum /sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.sum.sent &&
mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.sum /sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.sum.sent &&
mv /sources/gcc-build/./gcc/testsuite/g++/g++.log /sources/gcc-build/./gcc/testsuite/g++/g++.log.sent &&
mv /sources/gcc-build/./gcc/testsuite/gcc/gcc.log /sources/gcc-build/./gcc/testsuite/gcc/gcc.log.sent &&
mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.log /sources/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.log.sent &&
mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.log /sources/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.log.sent &&
mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.log /sources/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.log.sent &&
mv /sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.log /sources/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.log.sent &&
true

Binutils tests problem

Antony Vincent — 2013-05-09T00:28:20

Hi! I have a problem with the binutils tests in chapter 6. After the command make -k check, I got this: 

./test-expandargvPASS: test-expandargv-0.PASS: test-expandargv-1.PASS: test-expandargv-2.PASS: test-expandargv-3.PASS: test-expandargv-4.PASS: test-expandargv-5.PASS: test-expandargv-6.make[3]: Leaving directory `/sources/binutils-build/libiberty/testsuite'make[2]: Leaving directory `/sources/binutils-build/libiberty'make[1]: Target `check-host' not remade because of errors.make[1]: Nothing to be done for `check-target'.make[1]: Leaving directory `/sources/binutils-build'make: *** [do-check] Error 2make: Target `check' not remade because of errors.

I looked on google and others persons have the same problem, but there were no real answers...

I follow the book version 7.3. 

Thanks

       -- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

undefined reference to symbol'pthread_create< at >< at >GLIBC_2.1' in check-0.9.9

William K Helbig Jr — 2013-05-08T17:34:35

Greetings to all,

I am attempting to build the LFS system following the current instructions
from the LFS 7.3 book. When building check-0.9.9 I get the above error. I
believe the relative part of the build log is:

/bin/sh ../libtool --tag=CC   --mode=link gcc  -g -O2 -Wall -ansi 
-pedantic -Wextra -Wstrict-prototypes -Wmissing-prototypes 
-Wwrite-strings -Wno-variadic-macros   -o check_thread_stress 
check_thread_stress-check_thread_stress.o ../src/libcheck.la 
../lib/libcompat.la  -lrt
libtool: link: gcc -g -O2 -Wall -ansi -pedantic -Wextra 
-Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings 
-Wno-variadic-macros -o .libs/check_thread_stress 
check_thread_stress-check_thread_stress.o ../src/.libs/libcheck.so 
../lib/.libs/libcompat.a -lrt -Wl,-rpath -Wl,/tools/lib
/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< at >< at >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< at >< at >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

When I compare my log to the one at
http://www.linuxfromscratch.org/lfs/build-logs/7.3/core2duo/logs/041-check
I see the -pthread parameter is not specified anywhere in my build.

At this point I am stumped. What do I need to check or do next?

Skip H

Can not find device "eth0"

Niels Terp — 2013-05-08T07:01:02

Hi there,

I have build LFS several times now, and I thought I would give the latest
kernel 3.9 a try.

The installation boots without problems, but in the end of the boot it can
not find my NIC.

Error message:

Adding IPv4 address 192.168.0.100 to the eth0 interface...Cannot find device
"eth0"      [FAIL]
*****
*****face eth0 doesn't exist.
[FAIL]

The "face" in above line it not a typo, that is actualy what is written on
my screen.

When I log in as root and type "ifup" I get:

Bringing up the interface...    /etc/sysconfig/ifconfig. Is missing or
cannot be accessed.                 [FAIL]

But "ls -ali /etc/sysconfig/ifconfig* shows:

3008808 -rw-r--r-- 1 root root 113  7 maj 20:55
/etc/sysconfig/ifconfig.eth0

So the file is there, and can be accessed - and its content is just as it
usualy is, which has been working before.

I hope somebody can help me to get in contact with my machine ! 

Niels