$LFS Error

cbates55 · 12-22-2001, 09:28 PM

I got the following error when I was do the static install of the kernel in Linux From Scratch($LFS).

rm -f /mnt/lfs/usr/src/linux/scripts/mkdep-docbook
rm -rf DBTOHTML_OUTPUT*
make[1]: Leaving directory `/mnt/lfs/usr/src/linux/Documentation/DocBook'
bash: yes: command not found
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
/bin/sh scripts/Configure arch/i386/config.in
#
# Using defaults found in arch/i386/defconfig
#
*
* Code maturity level options
*
Prompt for development and/or incomplete code/drivers (CONFIG_EXPERIMENTAL) [N/y/?]
make: *** [config] Error 1

Can any of you help me with this problem. I did notice that it said: 'bash: yes: command not found', could this be the problem and if it is how can I fix this problem.

bluecadet · 12-23-2001, 05:13 AM

yes is a damn clever idea. a minute program that says yes to stdout. you'll need to compile yes in order to get past that.

cbates55 · 12-23-2001, 07:47 PM

bluecadet replied:
you'll need to compile yes in order to get past that.

So where can I get it to compile it. HELP

taz.devil · 12-23-2001, 08:18 PM

Bummer, I believe that the "yes" command is found in either the fileutils package or diffutils. I can't remember, if anything, all you have to do is go through the book and each packages file contents are listed and you can find which one it's in from there.

cbates55 · 12-23-2001, 08:31 PM

I found that it is in the Sh-util package.

Do you think I could use the source from Linux from scratch to compile it for my host system? If I can how can I make sure that I don't break what is already there?

taz.devil · 12-23-2001, 08:38 PM

What I would do is remove the old sh-utils source directory: example rm -rf sh-utils-2.0 and then unzip the LFS sh-utils package again and do a fresh install of the utils and I think you will be good after that. Then go back into the chrooted environment and try glibc again.

cbates55 · 12-24-2001, 01:46 AM

Thanks for the help with the Sh-utils problem, got past that problem, but I now have a new problem. Here it is as follows:

ibc-build/rt:/usr/src/sources/g/glibc-build/resolv:/usr/src/sources/g/glibc-build/crypt:/usr/src/sources/g/glibc-build/linuxthreads /usr/src/sources/g/glibc-build/sunrpc/rpcgen -Y `gcc -print-file-name=cpp | sed 's|/cpp$||'` -c rpcsvc/bootparam_prot.x -o /usr/src/sources/g/glibc-build/sunrpc/xbootparam_prot.T
cannot find C preprocessor: cpp/cpp
/usr/src/sources/g/glibc-build/sunrpc/rpcgen: C preprocessor failed with exit code 1
make[2]: *** [/usr/src/sources/g/glibc-build/sunrpc/xbootparam_prot.stmp] Error 1
make[2]: Leaving directory `/usr/src/sources/g/glibc-2.2.4/sunrpc'
make[1]: *** [sunrpc/others] Error 2
make[1]: Leaving directory `/usr/src/sources/g/glibc-2.2.4'
make: *** [all] Error 2
[I have no name!@Draco: glibc-build]#

This is the output I get when I went to install Glibc-2.2.4 on LFS. This time I have no idea what went wrong. The only clue I have is it cann't find C preprocessor: cpp/cpp. HELP!!!

taz.devil · 12-24-2001, 11:28 AM

Well, no problems, there's always a fix! A hammer is last resort though, so put that down!

cpp is part of the gcc-2.95.3 package and somehow didn't get installed or the path is wrong. Look for it on your system, and if you don't find it in /usr/bin then you'll need to reinstall gcc-2.95.3 and the patch.

cbates55 · 12-26-2001, 06:55 PM

What if I find it

Look for it on your system, and if you don't find it in /usr/bin

in /usr/bin and my path is setup to include the /usr/bin? At this point I'm stumped at what to do.

Please help me!!!

taz.devil · 12-26-2001, 07:16 PM

Hmm, I can't say right off hand why it's not finding cpp if it's in your path. You could try a fresh install of the package since it'll have to be installed anyhow. Just wipe out your gcc-2.95.3 source dir and re-do it so to speak.

cbates55 · 12-29-2001, 10:24 PM

Your going to laugh at this. You know how they tell you in the LFS book to create a directory under /usr/src called 'sources' and then place directories under it (a-z) with the source code.

Well I did that and I was running the installs from those directories. So when I went to install glibc it failed on the looking for the cpp program. After beatting my head against the monitor I put the glibc source code directory right under the /usr/src directories and it worked after I cleared out some room for it to compile.