Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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.
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: *** [/usr/src/sources/g/glibc-build/sunrpc/xbootparam_prot.stmp] Error 1
make: Leaving directory `/usr/src/sources/g/glibc-2.2.4/sunrpc'
make: *** [sunrpc/others] Error 2
make: 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!!!
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.
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.
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.