LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
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 05-07-2019, 03:18 PM   #1
portabledoor
LQ Newbie
 
Registered: May 2019
Posts: 3

Rep: Reputation: Disabled
glibc-2.29 fails to compile : /dev/null unkown type name (step 6.9.1)


Hi,

I have followed all the instructions without deviation.
Unfortunately, I seem to have reached somewhat of an impasse with the (second? proper?) compile of glibc. Either way the terminal output is as follows:

-I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -D_LIBC_REENTRANT -include /sources/glibc-2.29/build/libc-modules.h -DMODULE_NAME=libc -include ../include/libc-symbols.h -DTOP_NAMESPACE=glibc -o /sources/glibc-2.29/build/csu/Mcrt1.o -x c /dev/null
/dev/null:1:8: error: unknown type name 'GNU'
mkdir (GNU coreutils) 8.30
^~~
make[2]: *** [Makefile:168: /sources/glibc-2.29/build/csu/Mcrt1.o] Error 1
make[2]: Leaving directory '/sources/glibc-2.29/csu'
make[1]: *** [Makefile:258: csu/subdir_lib] Error 2
make[1]: Leaving directory '/sources/glibc-2.29'
make: *** [Makefile:9: all] Error 2

My limited Linux knowledge tells me that the 'mkdir (GNU coreutils)' command is directly written into the file, thus my suspicion is either:
  1. (very unlikely to impossible) There is an error with glibc.
  1. (more likely) There is something that is incorrect on my behalf. What this something is, I cannot be certain. Perhaps a file I have not linked, or build in the correct place, or perhaps a command during the configure process I have overlooked? However, I remain confused as to from where such an error could arise, seeing as I have pretty much copy-pasted almost all commands into the terminal.

Thank you for your help and time with this issue.
 
Old 05-08-2019, 01:06 PM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,309

Rep: Reputation: 2325Reputation: 2325Reputation: 2325Reputation: 2325Reputation: 2325Reputation: 2325Reputation: 2325Reputation: 2325Reputation: 2325Reputation: 2325Reputation: 2325
Sounds not too serious. Give us the exact page (e.g. 6.21 or whatever). When the compile pukes, hit up-arrow & return and post all it spews out. Tell us your host system
 
Old 05-08-2019, 03:52 PM   #3
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 7,583
Blog Entries: 19

Rep: Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454
Are you sure you have bound all dynamic directories in your new partition to their equivalents on the host before chrooting over? Please go through chapter 6.2 carefully.
 
Old 05-09-2019, 06:06 AM   #4
portabledoor
LQ Newbie
 
Registered: May 2019
Posts: 3

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by business_kid View Post
Sounds not too serious. Give us the exact page (e.g. 6.21 or whatever). When the compile pukes, hit up-arrow & return and post all it spews out. Tell us your host system
Here you go:

(lfs chroot) root:/sources/glibc-2.29/build# make
make -r PARALLELMFLAGS="" -C .. objdir=`pwd` all
make[1]: Entering directory '/sources/glibc-2.29'
make subdir=csu -C csu ..=../ subdir_lib
make[2]: Entering directory '/sources/glibc-2.29/csu'
gcc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include -isystem /usr/include -c -std=gnu11 -fgnu89-inline -g -O2 -Wall -Wwrite-strings -Wundef -fmerge-all-constants -frounding-math -fno-stack-protector -Wstrict-prototypes -Wold-style-definition -fmath-errno -fno-stack-protector -DSTACK_PROTECTOR_LEVEL=0 -ftls-model=initial-exec -I../include -I/sources/glibc-2.29/build/csu -I/sources/glibc-2.29/build -I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch -I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch -I../sysdeps/x86_64 -I../sysdeps/x86 -I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -D_LIBC_REENTRANT -include /sources/glibc-2.29/build/libc-modules.h -DMODULE_NAME=libc -include ../include/libc-symbols.h -DTOP_NAMESPACE=glibc -o /sources/glibc-2.29/build/csu/Mcrt1.o -x c /dev/null
/dev/null:1:8: error: unknown type name 'GNU'
mkdir (GNU coreutils) 8.30
^~~
make[2]: *** [Makefile:168: /sources/glibc-2.29/build/csu/Mcrt1.o] Error 1
make[2]: Leaving directory '/sources/glibc-2.29/csu'
make[1]: *** [Makefile:258: csu/subdir_lib] Error 2
make[1]: Leaving directory '/sources/glibc-2.29'
make: *** [Makefile:9: all] Error 2

Hope it helps. 95% of it is indecipherable to me. :P

Thank you so far.

p.s. I am running on Bodhi Linux (so that the base system does not consume that many resources) in a virtualbox. And yes, I made sure to install or update all the relevant software, and make the appropriate symlinks.

Last edited by portabledoor; 05-09-2019 at 06:12 AM.
 
Old 05-09-2019, 06:10 AM   #5
portabledoor
LQ Newbie
 
Registered: May 2019
Posts: 3

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by hazel View Post
Are you sure you have bound all dynamic directories in your new partition to their equivalents on the host before chrooting over? Please go through chapter 6.2 carefully.
I would have thought so, seeing as I have inputted all the commands in chapters 5 and 6 as they are printed. However, just so we are on the same page, to someone who doesn't quite have as much expertise as you, what type/types of commands should I be looking for exactly when binding the dynamic in my new partitions?
 
Old 05-09-2019, 06:28 AM   #6
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 7,583
Blog Entries: 19

Rep: Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454Reputation: 4454
This is the bit I meant
Quote:
Originally Posted by The Book
mount -v --bind /dev $LFS/dev
mount -vt devpts devpts $LFS/dev/pts -o gid=5,mode=620
mount -vt proc proc $LFS/proc
mount -vt sysfs sysfs $LFS/sys
mount -vt tmpfs tmpfs $LFS/run
Your error message suggests to me that you may not have a working /dev directory in your chroot environment. You can check that easily by listing /dev with the ls command. If the directory is empty, you have forgotten to bind it to the dev directory of your host.

If you are building in stages on separate days, you need to carry out these bind commands before each session. You do it in the host environment before you chroot over. The easiest way, I've found, is to put everything -- mount, bind and chroot -- into a permanent script, then just run it.
 
  


Reply



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
[SOLVED] Stopping cron job emails to root, do I use >/dev/null 2>&1 or &> /dev/null anon091 Linux - Newbie 3 11-12-2013 10:21 AM
[SOLVED] Why is there a need for /dev/null, /dev/zero and other special device (files) in /dev suttiwit Linux - General 13 08-07-2012 12:26 AM
What is meant by " file > /dev/null 2>&1 </dev/null " attockonian Linux - Newbie 5 06-30-2006 10:51 PM
1> /dev/null 2> /dev/null elyk Programming 9 09-20-2004 05:44 PM
1>/dev/null 2>/dev/null chr15t0 Linux - General 2 07-19-2002 08:37 AM

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

All times are GMT -5. The time now is 04:52 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
Open Source Consulting | Domain Registration