LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Linux From Scratch
User Name
Password
Linux From Scratch This 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


Reply
  Search this Thread
Old 08-22-2019, 03:02 PM   #1
melvyniandrag
LQ Newbie
 
Registered: Aug 2019
Posts: 4

Rep: Reputation: Disabled
Chapter 6 Glibc make check failures


Ran through procedures. First time did 'make -j4'. Then 'make check' wouldn't even run. Backtracked, deleted the build dir and started over from there. Then did 'make' and 'make check'. This time it completed, but I got 141 failures and 2 xpass that aren't all listed in the notes regarding expected failures.

Toying with proceeding boldly on and going back and trying the process again. I'll update when I make a decision, working on something else right now. Just dropping a line in case someone has some brilliant wisdom to simplify the decision making process.


Code:
FAIL: assert/tst-assert-c++
FAIL: assert/tst-assert-g++
FAIL: debug/tst-backtrace2
FAIL: debug/tst-backtrace3
FAIL: debug/tst-backtrace4
FAIL: debug/tst-backtrace5
FAIL: debug/tst-backtrace6
FAIL: debug/tst-chk4
FAIL: debug/tst-chk5
FAIL: debug/tst-chk6
FAIL: debug/tst-lfschk4
FAIL: debug/tst-lfschk5
FAIL: debug/tst-lfschk6
FAIL: dlfcn/bug-atexit3
UNSUPPORTED: elf/tst-audit10
UNSUPPORTED: elf/tst-audit4
UNSUPPORTED: elf/tst-avx
UNSUPPORTED: elf/tst-avx512
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
FAIL: elf/tst-unwind-main
FAIL: iconv/tst-iconv-mt
FAIL: inet/tst-idna_name_classify
FAIL: malloc/tst-malloc-stats-cancellation
UNSUPPORTED: math/test-double-libmvec-alias-avx
UNSUPPORTED: math/test-double-libmvec-alias-avx-main
UNSUPPORTED: math/test-double-libmvec-alias-avx2
UNSUPPORTED: math/test-double-libmvec-alias-avx2-main
UNSUPPORTED: math/test-double-libmvec-alias-avx512
UNSUPPORTED: math/test-double-libmvec-alias-avx512-main
UNSUPPORTED: math/test-double-libmvec-sincos-avx
UNSUPPORTED: math/test-double-libmvec-sincos-avx2
UNSUPPORTED: math/test-double-libmvec-sincos-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx
UNSUPPORTED: math/test-float-libmvec-alias-avx-main
UNSUPPORTED: math/test-float-libmvec-alias-avx2
UNSUPPORTED: math/test-float-libmvec-alias-avx2-main
UNSUPPORTED: math/test-float-libmvec-alias-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512-main
UNSUPPORTED: math/test-float-libmvec-sincosf-avx
UNSUPPORTED: math/test-float-libmvec-sincosf-avx2
UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
UNSUPPORTED: misc/tst-pkey
FAIL: misc/tst-ttyname
UNSUPPORTED: nptl/test-cond-printers
UNSUPPORTED: nptl/test-condattr-printers
UNSUPPORTED: nptl/test-mutex-printers
UNSUPPORTED: nptl/test-mutexattr-printers
UNSUPPORTED: nptl/test-rwlock-printers
UNSUPPORTED: nptl/test-rwlockattr-printers
FAIL: nptl/tst-basic3
FAIL: nptl/tst-basic4
FAIL: nptl/tst-call-once
FAIL: nptl/tst-cancel-self
FAIL: nptl/tst-cancel-self-cancelstate
FAIL: nptl/tst-cancel-self-canceltype
FAIL: nptl/tst-cancel-self-testcancel
FAIL: nptl/tst-cancel1
FAIL: nptl/tst-cancel10
FAIL: nptl/tst-cancel11
FAIL: nptl/tst-cancel12
FAIL: nptl/tst-cancel13
FAIL: nptl/tst-cancel14
FAIL: nptl/tst-cancel15
FAIL: nptl/tst-cancel16
FAIL: nptl/tst-cancel17
FAIL: nptl/tst-cancel18
FAIL: nptl/tst-cancel2
FAIL: nptl/tst-cancel20
FAIL: nptl/tst-cancel21
FAIL: nptl/tst-cancel22
FAIL: nptl/tst-cancel23
FAIL: nptl/tst-cancel24
FAIL: nptl/tst-cancel25
FAIL: nptl/tst-cancel3
FAIL: nptl/tst-cancel4
FAIL: nptl/tst-cancel4_1
FAIL: nptl/tst-cancel4_2
FAIL: nptl/tst-cancel5
FAIL: nptl/tst-cancel6
FAIL: nptl/tst-cancel7
FAIL: nptl/tst-cancel8
FAIL: nptl/tst-cancel9
FAIL: nptl/tst-cancelx10
FAIL: nptl/tst-cancelx11
FAIL: nptl/tst-cancelx12
FAIL: nptl/tst-cancelx13
FAIL: nptl/tst-cancelx14
FAIL: nptl/tst-cancelx15
FAIL: nptl/tst-cancelx16
FAIL: nptl/tst-cancelx17
FAIL: nptl/tst-cancelx18
FAIL: nptl/tst-cancelx2
FAIL: nptl/tst-cancelx20
FAIL: nptl/tst-cancelx21
FAIL: nptl/tst-cancelx3
FAIL: nptl/tst-cancelx4
FAIL: nptl/tst-cancelx5
FAIL: nptl/tst-cancelx6
FAIL: nptl/tst-cancelx7
FAIL: nptl/tst-cancelx8
FAIL: nptl/tst-cancelx9
FAIL: nptl/tst-cleanup0
FAIL: nptl/tst-cleanup0-cmp
FAIL: nptl/tst-cleanup1
FAIL: nptl/tst-cleanup3
FAIL: nptl/tst-cleanup4
FAIL: nptl/tst-cleanupx0
FAIL: nptl/tst-cleanupx1
FAIL: nptl/tst-cleanupx3
FAIL: nptl/tst-cleanupx4
FAIL: nptl/tst-cnd-basic
FAIL: nptl/tst-cnd-broadcast
FAIL: nptl/tst-cnd-timedwait
FAIL: nptl/tst-cond-except
FAIL: nptl/tst-cond22
FAIL: nptl/tst-cond25
FAIL: nptl/tst-cond7
FAIL: nptl/tst-cond8
FAIL: nptl/tst-exec5
FAIL: nptl/tst-execstack
FAIL: nptl/tst-exit2
FAIL: nptl/tst-exit3
FAIL: nptl/tst-fini1
FAIL: nptl/tst-join1
FAIL: nptl/tst-join5
FAIL: nptl/tst-join6
FAIL: nptl/tst-key3
FAIL: nptl/tst-minstack-cancel
FAIL: nptl/tst-minstack-exit
FAIL: nptl/tst-minstack-throw
FAIL: nptl/tst-mtx-basic
FAIL: nptl/tst-mtx-timedlock
FAIL: nptl/tst-mtx-trylock
FAIL: nptl/tst-mutex8
FAIL: nptl/tst-mutexpi8
FAIL: nptl/tst-once3
FAIL: nptl/tst-once4
FAIL: nptl/tst-oncex3
FAIL: nptl/tst-oncex4
FAIL: nptl/tst-robust1
FAIL: nptl/tst-robust2
FAIL: nptl/tst-robust3
FAIL: nptl/tst-robust4
FAIL: nptl/tst-robust5
FAIL: nptl/tst-robust6
FAIL: nptl/tst-robust7
FAIL: nptl/tst-robustpi1
FAIL: nptl/tst-robustpi2
FAIL: nptl/tst-robustpi3
FAIL: nptl/tst-robustpi4
FAIL: nptl/tst-robustpi5
FAIL: nptl/tst-robustpi6
FAIL: nptl/tst-robustpi7
FAIL: nptl/tst-sem11
FAIL: nptl/tst-sem12
FAIL: nptl/tst-sem16
FAIL: nptl/tst-stack4
FAIL: nptl/tst-thrd-detach
FAIL: nptl/tst-thrd-sleep
FAIL: nptl/tst-thread-exit-clobber
FAIL: nptl/tst-thread_local1
FAIL: nptl/tst-tsd5
FAIL: nptl/tst-tss-basic
FAIL: nss/tst-cancel-getpwuid_r
UNSUPPORTED: nss/tst-nss-test3
FAIL: posix/tst-getopt-cancel
UNSUPPORTED: resolv/tst-resolv-ai_idn
UNSUPPORTED: resolv/tst-resolv-ai_idn-latin1
FAIL: rt/tst-cpuclock2
FAIL: rt/tst-mqueue8
FAIL: rt/tst-mqueue8x
FAIL: rt/tst-shm-cancel
FAIL: stdlib/tst-quick_exit
FAIL: stdlib/tst-thread-quick_exit
Summary of test results:
    141 FAIL
   5809 PASS
     32 UNSUPPORTED
     17 XFAIL
      2 XPASS
make[1]: *** [Makefile:405: tests] Error 1
make[1]: Leaving directory '/sources/glibc-2.29'
make: *** [Makefile:9: check] Error 2
 
Old 08-23-2019, 02:38 AM   #2
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,387
Blog Entries: 9

Rep: Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893
At last! Someone who gets a list similar to mine! Let's do a comparison. First, what is your architecture, 32-bit or 64-bit? I'm building out of a 64-bit system but it's a multilib build so I need a 32-bit glibc as well as a 64-bit one. On the native 64-bit glibc build, I get only a couple of errors but my 32-bit glibc behaves just like yours.

The nptl errors have to do with the POSIX thread library. How many errors do you get if you subtract those? Ignore XPASSes, XFAILs and unsupported tests; they're harmless.

As I only need the 32-bit glibc for my printer driver, which wouldn't be using threads, I ignore the errors. However, you can't do that with your main glibc. I've been using -j4 so far but I'm going to try without and see if that makes a difference. I suspect that your first check failed, not because you used -j4 but because you forget to make those ld-linux links specified in the book. Those weren't needed in LFS-8.4 but they are now. I forgot them first time around and also got a crash.

Last edited by hazel; 08-23-2019 at 09:23 AM.
 
Old 08-23-2019, 09:22 AM   #3
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,387
Blog Entries: 9

Rep: Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893
OK, here's the (possible) answer. I have just built glibc again. The 64-bit library was built and tested with -j4 as this didn't cause any previous trouble. The 32-bit glibc was built and tested this time with -j1. And the answers came out identical: 3 FAILs, two of them expected.

So I suggest that you scrap your wonky glibc build and redo it with -j1 for both the build and the test stages. There's something about multiple core use that doesn't agree with the 32-bit POSIX thread library.

Last edited by hazel; 08-23-2019 at 09:25 AM.
 
Old 08-23-2019, 10:47 AM   #4
melvyniandrag
LQ Newbie
 
Registered: Aug 2019
Posts: 4

Original Poster
Rep: Reputation: Disabled
Hey there I'm on 64bit Ubuntu with some multiarch tools installed.

Code:
melvyn@melvyn-ThinkPad-T410:~$ cat /var/lib/dpkg/arch
amd64
i386
Though I'm not sure what role the i386 plays in my lfs build process, because I just want to build 64bit and proceeded accordingly. Admittedly, there was a bit of information in the book about cross compiling and architectures that I glossed over. At this point I'm not worried about drivers too much, I just want to boot into LFS, write hello world in vim and then compile and run it. Just to tick this LFS thing off the bucket list.

Glad to see someone else with the same issues too. I noticed in addition to the nptl errors that there were a couple of failed test cases about threads in different test suites, I'm was a bit worried about that because I use pthreads in alot of code I write and I'm sure that linux packages depend heavily on them too.

So I just continued on last night and ignored the make check fails. Then when I tried to compile dummy.c I got linker errors. First for crt1.0 and crti.o. I wasn't sure what to do. I ctrl+f-ed the pdf and couldn't find anywhere that we were supposed to make links to those. So I just went ahead and made links myself between /lib and /tools/lib ( I think, I forget). This solved that issue but then ld couldn't find libc, I got an error like blah-ld: cannot find -lc. At this point I decided I should just start over, and went to bed. Today going to start from scratch and be even more careful about reading hte book.

Do you have any insight on those linker errors? Was there some obvious step that I missed? Thanks for the info Hazel! I'm going to look into building 64 and 32 bit tools on my next go round and I'll see what comes up.
 
Old 08-23-2019, 11:03 AM   #5
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,387
Blog Entries: 9

Rep: Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893
You can't simply go on. The tests already show that your glibc is screwed. I'm interested that in your case the problem showed up in 64-bit glibc, which didn't cause me any problems at all. I wonder if it is something to do with your using Ubuntu as a build host; it has a poor reputation in LFS circles.

Did you save your tool set before adjusting it, as suggested in the book? If so, you can go back: clear the tools directory and repopulate it with the saved set. Then build glibc again with -j1 and check it with -j1 too. For me, that cleared the problem. Your mileage may vary!

The multilib build that I am using is unofficial. The official way to do multilib is using CLFS. But this thread started by Emmett1 shows how you can do a multilib build within LFS itself. I need this because I have a printer with 32-bit drivers which depend on a 32-bit libc.

Last edited by hazel; 08-23-2019 at 11:05 AM.
 
Old 08-23-2019, 11:08 AM   #6
melvyniandrag
LQ Newbie
 
Registered: Aug 2019
Posts: 4

Original Poster
Rep: Reputation: Disabled
Interesting.

I didnt back up the tools at the end of chapter 5 because the chapter 5 process was so simple that I was sure it wouldnt be necessary, this go around I definitely will!


I've got a T430 in the closet with debian 9 I havent touched in a while. Will try that and post back with results. If I'm not lazy maybe I can build on both in parallel and see if Ubuntu is in fact finicky.

Hoping to post a success story ( about glibc at least ) within 24 hours!
 
Old 08-23-2019, 11:11 AM   #7
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 3,387
Blog Entries: 9

Rep: Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893Reputation: 1893
With Debian, there are two things you need to fix before you start building LFS.

1) Install gawk. Debian uses mawk by default and that won't work.

2) Make sure your system shell (/bin/sh) points to bash. By default it will be dash and that doesn't work either. Apart from that, you shouldn't have any problems.

PS: I've just had an idea: what does Ubuntu use for these 2 tools? Because Ubuntu is based on Debian after all.

Last edited by hazel; 08-23-2019 at 11:12 AM.
 
Old 08-23-2019, 11:39 AM   #8
melvyniandrag
LQ Newbie
 
Registered: Aug 2019
Posts: 4

Original Poster
Rep: Reputation: Disabled
gawk + dash but its easy to dpkg --reconfigure dash to bash as I've done. It meets all the requirements in the book and passes the version-check.sh script when sh -> bash.

Debian is a pita sometimes I think Ill actually leave that alone for now because I don't know what havok changing mawk to gawk might wreak. I'm thinking ubuntu for one last try!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
make check glibc failures sleepyspider Linux From Scratch 3 03-13-2017 10:56 AM
make check failures for glibc midiox Linux From Scratch 3 12-27-2005 04:53 AM
LFS 6, chapter 6.11; Glibc 'make check' error Zamochit Linux From Scratch 5 05-31-2005 12:54 PM
Problems with "make check" while compiling Glibc in Chapter 6.11 Spuckdung Linux From Scratch 2 02-13-2005 05:12 AM
Chapter 6: Glibc make check problems davemar Linux From Scratch 0 04-08-2004 05:17 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Linux From Scratch

All times are GMT -5. The time now is 06:47 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration