[SOLVED] Help Me! Psmisc-23.1 Chapter 6 LFS

lfs1121 · 11-14-2018, 05:45 AM

Hello,
I am following the instruction for compiling Psmisc-23.2. I get the following error each time I try:

(lfs chroot) root:/sources/psmisc-23.2# ./configure --prefix=/usr
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /tools/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking how to create a pax tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/sources/psmisc-23.2':
configure: error: C compiler cannot create executables
See `config.log' for more details
(lfs chroot) root:/sources/psmisc-23.2# make
make: *** No targets specified and no makefile found. Stop.
(lfs chroot) root:/sources/psmisc-23.2# ./configure --prefix=/usr
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /tools/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking how to create a pax tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/sources/psmisc-23.2':
configure: error: C compiler cannot create executables
See `config.log' for more details

Any help would be highly appreciated.

business_kid · 11-14-2018, 06:57 AM

Code:

configure: error: C compiler cannot create executables

That's your problem. It checks to see if the compiler (cc) can handle the simplest program it can get away with, and write the file. That checks that a compiler exists, and can compile & write. You fail.

What book are you in? What page number? What Project? What are you compiling for? LFS has several projects on offer.

lfs1121 · 11-14-2018, 07:05 AM

Quote:

Originally Posted by business_kid

Code:

configure: error: C compiler cannot create executables

That's your problem. It checks to see if the compiler (cc) can handle the simplest program it can get away with, and write the file. That checks that a compiler exists, and can compile & write. You fail.

What book are you in? What page number? What Project? What are you compiling for? LFS has several projects on offer.

I am building linux from scratch following the instructions from LFS Book 8.3, chapter 6. I have completed the previous chapters with no errors.
At the moment, I am compiling psmisc-23.2 package.

Code:

 I get this error configure: error: C compiler cannot create executables

for all other packages that begins compilation with

Code:

 ./configure --prefix=/usr

Here is the html link to the book I am following:
http://www.linuxfromscratch.org/lfs/...-system-kernfs

business_kid · 11-14-2018, 11:53 AM

That's python utilities, and not in chapter 6 of LFS unless you can quote me thye page number (top LH corner)

Anyhow, my diagnosis is correct. Your compiler is AWOL. If you're starting chapter 6, your $PATH should be showing the compiler in /tools. Start over at the beginning of ch 6. If you're not starting, tell me what you have done.

hazel · 11-14-2018, 01:14 PM

Quote:

Originally Posted by business_kid

If you're starting chapter 6, your $PATH should be showing the compiler in /tools. Start over at the beginning of ch 6. If you're not starting, tell me what you have done.

Actually if he is carrying out the instructions in the correct sequence, he will be well into chapter 6 by the time psmisc comes along. The complete toolchain (gcc, binutils, glibc) should be in /usr/bin and the /tools versions will not be used any more.

@OP: have you had this problem on any of your previous Chapter 6 builds (e.g sed or libcap)? Did gcc pass all its sanity tests? Did you correctly carry out the adjustments in 6.10? And are you doing all this in one session or are you going in and out of chroot? If you are doing that, have you checked at the beginning of each session that your mount and chroot was correctly carried out?

lfs1121 · 11-14-2018, 03:21 PM

Quote:

Originally Posted by business_kid

That's python utilities, and not in chapter 6 of LFS unless you can quote me thye page number (top LH corner)

Anyhow, my diagnosis is correct. Your compiler is AWOL. If you're starting chapter 6, your $PATH should be showing the compiler in /tools. Start over at the beginning of ch 6. If you're not starting, tell me what you have done.

The page number of Linux From Scratch-Version 8.3 is 137. The package name is 6.29. Psmics-23.1. I get the error message after running the command

Code:

 ./configure --prefix=/usr

All the previous packages I compiled are exactly done the way instructed in the book.

lfs1121 · 11-14-2018, 03:27 PM

Quote:

Originally Posted by hazel

Actually if he is carrying out the instructions in the correct sequence, he will be well into chapter 6 by the time psmisc comes along. The complete toolchain (gcc, binutils, glibc) should be in /usr/bin and the /tools versions will not be used any more.

@OP: have you had this problem on any of your previous Chapter 6 builds (e.g sed or libcap)? Did gcc pass all its sanity tests? Did you correctly carry out the adjustments in 6.10? And are you doing all this in one session or are you going in and out of chroot? If you are doing that, have you checked at the beginning of each session that your mount and chroot was correctly carried out?

You are right, I am carrying out the instructions in a sequence-following the book. I did not have any error with the previous packages. I also did not proceed in case I get any error while compiling previous packages. No, I am not doing all these in one session. I mount my devices and chroot at each login with the following commands:

Code:

#set variables of LFS
export LFS=/mnt/lfs

#mount LFS and boot partitions
sudo mount -v -t ext4 /dev/<xxx> $LFS
sudo mount -v -t ext2 /dev/<xxx> $LFS/boot

#start swap partition
sudo /sbin/swapon -v /dev/<xxx>

cd $LFS

#login to chroot
sudo chroot "$LFS" /tools/bin/env -i \
    HOME=/root                  \
    TERM="$TERM"                \
    PS1='(lfs chroot) \u:\w\$ ' \
    PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
    /tools/bin/bash --login +h

lfs1121 · 11-14-2018, 04:00 PM

Quote:

Originally Posted by lfs1121

You are right, I am carrying out the instructions in a sequence-following the book. I did not have any error with the previous packages. I also did not proceed in case I get any error while compiling previous packages. No, I am not doing all these in one session. I mount my devices and chroot at each login with the following commands:

Code:

#set variables of LFS
export LFS=/mnt/lfs

#mount LFS and boot partitions
sudo mount -v -t ext4 /dev/<xxx> $LFS
sudo mount -v -t ext2 /dev/<xxx> $LFS/boot

#start swap partition
sudo /sbin/swapon -v /dev/<xxx>

cd $LFS

#login to chroot
sudo chroot "$LFS" /tools/bin/env -i \
    HOME=/root                  \
    TERM="$TERM"                \
    PS1='(lfs chroot) \u:\w\$ ' \
    PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
    /tools/bin/bash --login +h

So I started to redo the steps from recompiling GCC8.2.0 package (Linux From Scratch-Version 8.3 page# 122).
When running

Code:

rm -f /usr/lib/gcc

It gave me the following error that can not delete lib/gcc is not a directory. I then removed it with -rf command

Code:

rm -rf /usr/lib/gcc

and when running the SED commands, I get the following error

Code:

(lfs chroot) root:/sources/gcc-8.2.0# 
(lfs chroot) root:/sources/gcc-8.2.0# rm -rf /usr/lib/gcc
(lfs chroot) root:/sources/gcc-8.2.0# mkdir -v build
mkdir: created directory 'build'
(lfs chroot) root:/sources/gcc-8.2.0# cd build
<.2.0/build# SED=sed                               \
> ../configure --prefix=/usr            \
>              --enable-languages=c,c++ \
>              --disable-multilib       \
>              --disable-bootstrap      \
>              --disable-libmpx         \
>              --with-system-zlib
configure: error: cannot run /bin/sh ../config.sub

spiky0011 · 11-14-2018, 04:09 PM

You dont show you are mounting
mount -v --bind /dev $LFS/dev and
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
Chapters 6.2.2 and 6.2.3

Before you enter chroot

lfs1121 · 11-15-2018, 02:11 AM

Quote:

Originally Posted by spiky0011

You dont show you are mounting
mount -v --bind /dev $LFS/dev and
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
Chapters 6.2.2 and 6.2.3

Before you enter chroot

This time I did the following steps first:

Code:

#set variables of LFS
export LFS=/mnt/lfs

#mount LFS and boot partitions
sudo mount -v -t ext4 /dev/<xxx> $LFS
sudo mount -v -t ext2 /dev/<xxx> $LFS/boot

#start swap partition
sudo /sbin/swapon -v /dev/<xxx>

#First mount the following
sudo mount -v --bind /dev $LFS/dev
sudo mount -vt devpts devpts $LFS/dev/pts -o gid=5,mode=620
sudo mount -vt proc proc $LFS/proc
sudo mount -vt sysfs sysfs $LFS/sys
sudo mount -vt tmpfs tmpfs $LFS/run

#Go to chroot
sudo chroot "$LFS" /tools/bin/env -i \
    HOME=/root                  \
    TERM="$TERM"                \
    PS1='(lfs chroot) \u:\w\$ ' \
    PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
    /tools/bin/bash --login +h

Then I restarted compiling the GCC8.2.0 package in Chapter 6, section 6.21.1. I get the following error

Code:

 
(lfs chroot) root:/sources# cd gcc-8.2.0
(lfs chroot) root:/sources/gcc-8.2.0# case $(uname -m) in
>   x86_64)
>     sed -e '/m64=/s/lib64/lib/' \
>         -i.orig gcc/config/i386/t-linux64
>   ;;
> esac
(lfs chroot) root:/sources/gcc-8.2.0# rm -f /usr/lib/gcc
(lfs chroot) root:/sources/gcc-8.2.0# mkdir -v build
mkdir: created directory 'build'
(lfs chroot) root:/sources/gcc-8.2.0# cd       build
(lfs chroot) root:/sources/gcc-8.2.0/build# 
(lfs chroot) root:/sources/gcc-8.2.0/build# 
<.2.0/build# SED=sed                               \
> ../configure --prefix=/usr            \
>              --enable-languages=c,c++ \
>              --disable-multilib       \
>              --disable-bootstrap      \
>              --disable-libmpx         \
>              --with-system-zlib
configure: error: cannot run /bin/sh ../config.sub
(lfs chroot) root:/sources/gcc-8.2.0/build#

I had previously compiled this package and got no error, the installation went successful, but I don't understand what I am doing wrong and I am already exhausted.

business_kid · 11-15-2018, 04:09 AM

@lfs1121: Doing LFS when things go wrong can be exhausting. We've all been there (Well, I certainly have).

Going back before the $PATH was readjusted (to get rid on /tools) is probably a good idea. Ch 6 from the top. Losing gcc is a show stopper - nothing would compile. So some recent package must have introduced that error, and that's exactly the sort of thing you don't want to chase. It could be worse. Halfway through ch. 6, I once found I had to delete, change my main OS, & restart ch.5

.

lfs1121 · 11-15-2018, 04:15 AM

Quote:

Originally Posted by business_kid

@lfs1121: Doing LFS when things go wrong can be exhausting. We've all been there (Well, I certainly have).

Going back before the $PATH was readjusted (to get rid on /tools) is probably a good idea. Ch 6 from the top. Losing gcc is a show stopper - nothing would compile. So some recent package must have introduced that error, and that's exactly the sort of thing you don't want to chase. It could be worse. Halfway through ch. 6, I once found I had to delete, change my main OS, & restart ch.5

.

Well, I just started to do chapter 6 from the beginning. Are you suggesting that I should redoing the process from Chapter 5? Doing LFS is part of my course assignment. Unfortunately, I am almost running out of time for this assignment.

hazel · 11-15-2018, 06:03 AM

Oh dear! From what you have said, I am pretty sure your chroot before doing psmisc was bad. Either you did not mount all your dynamic filesystems, as Spiky suggested, or you did not have LFS defined on your host system. If you had not panicked, the problem could have been solved very simply: exit chroot, set up all necessary filesystems properly (and make sure they are there by running the mount command), go back into chroot, delete the psmisc directory and untar the package afresh.

Unfortunately it seems that you have now started deleting previously installed stuff so you cannot continue.

Repeating chapter 6 from the beginning will probably not work because of the alterations you made to /tools/bin/ld and /tools/bin/gcc in 6.10. Repeating chapter 5 would work, but you say you have a problem with time.

For the future, I suggest that you create a script covering sections 6.2 and 6.4 and keep it in /root ready to run. Here is the one I use:

Code:

#! /bin/bash

# Define LFS variable
export LFS="/mnt/newlfs"

# Mount new LFS partition
mount /dev/sda5

# Mount dynamic directories
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

#...and now chroot!
chroot "$LFS" /tools/bin/env -i \
 HOME=/root     TERM="$TERM" \
 PS1='(lfs chroot) \u:\w\$ ' \
 PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login

If you go in and out of chroot by hand on different days, it is all too easy to miss something out.

lfs1121 · 11-15-2018, 06:30 AM

Quote:

Originally Posted by hazel

Oh dear! From what you have said, I am pretty sure your chroot before doing psmisc was bad. Either you did not mount all your dynamic filesystems, as Spiky suggested, or you did not have LFS defined on your host system. If you had not panicked, the problem could have been solved very simply: exit chroot, set up all necessary filesystems properly (and make sure they are there by running the mount command), go back into chroot, delete the psmisc directory and untar the package afresh.

Unfortunately it seems that you have now started deleting previously installed stuff so you cannot continue.

Repeating chapter 6 from the beginning will probably not work because of the alterations you made to /tools/bin/ld and /tools/bin/gcc in 6.10. Repeating chapter 5 would work, but you say you have a problem with time.

For the future, I suggest that you create a script covering sections 6.2 and 6.4 and keep it in /root ready to run. Here is the one I use:

Code:

#! /bin/bash

# Define LFS variable
export LFS="/mnt/newlfs"

# Mount new LFS partition
mount /dev/sda5

# Mount dynamic directories
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

#...and now chroot!
chroot "$LFS" /tools/bin/env -i \
 HOME=/root     TERM="$TERM" \
 PS1='(lfs chroot) \u:\w\$ ' \
 PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login

If you go in and out of chroot by hand on different days, it is all too easy to miss something out.

Thank you all so much for the help. I am now restarting the steps from the very beginning. Even redoing from chapter 5 didn't help. I sure learned from the errors I got and learned how to troubleshot them.