Hi,
I'm hesitant to post on this issue for a couple of reasons; systemd seems a
little sensitive in the LFS world at the moment and, I'm going to be accused
of not following the book. My excuse for the latter is that the book changed
while I was building, without me noticing.
My first attempt at 20141104-systemd was done largely with scripts, without
me paying too much attention to test logs; everything compiled and installed.
On booting, the kernel appeared to load, systemd reported failures with network,
resolver etc and then just stopped, without a login prompt. The system seems to
be running to some extent; switching an external drive on and off produced the
usual disconnecting / remounting messages. The only response I could elicit
from the keyboard was with 'ctrl-alt-del'.
I changed the systemd default.target to 'basic' which produced a few less
errors on boot
but the same result, reporting target.basic reached but no login.
I rebuilt everything from Chapter 5 but got the same result. All test errors
are listed below.
I'm inclined to give up on systemd ( I don't want, like or need more
complexity) but I
worry that sooner or later there will be no choise unless you can write your
own boot
scripts.
So, on the off chance that someone can spot an obvious problem --.
Glibc-2.20
FAIL: posix/tst-getaddrinfo4
FAIL: rt/tst-cpuclock2
Gcc-4.9.2
WARNING: program timed out.
FAIL: gcc.dg/atomic/c11-atomic-exec-5.c -O2 execution test
These didn't worry me too much, perhaps they should have. Not long ago there was
a small volume of 'possibly expected failures' from these two.
Libtool-2.4.3 produced the 5 expected errors which did indeed go away when
re-run later.
Autoconf-2.69
501: Libtool FAILED (foreign.at:61)
Googling this found a comment from Bruce that it related to libtool-2.4.3 and a
suggestion from the local guru to patch the test, not the program, so I guess
its
not a problem.
Systemd-216
./build-aux/test-driver: line 95: 9395 Aborted "$@" >
$log_file 2>&1
FAIL: test-bus-creds
No one else seems to have had this failure and I notice the development book has
moved to 217 and added another patch. Is this a problem?
Man-db-2.7.0.2
FAIL: man-6
Can't remember ever having a problem here before.
Util-linux-2.25.2
Don't have a log for this because the tests hang on the last line
libmount: lock ... OK
The final line
script: race conditions ... OK
never happens.
ps The link to the build logs at the end of Chapter 4 seems to be broken.
--
Ian Macdonald <[email protected]>
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
