6.14.2 glibc installation - patch command not found
Linux From ScratchThis 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
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
6.14.2 glibc installation - patch command not found
Ok, things have been going along here smoothly, but now I'm at 6.14.2, Glibc installation. I follow along and unpack the clibc-linuxthreads into my glibc-2.3.1 directory. I also moved the 2 patch files in there.
When i run: patch -Np1 -i glibc-2.3.1-root-perl.patch
I get the command not found error on patch:
bash: patch: command not found
Any ideas where I went wrong and now don't have patch?
From my Ch. 5 fun I have a patch-2.5.4 directory that has patch in it. I suppose I should just put that path in there and run the command.
The way I'm doing it, that directory is in /LFS/packages/temp. In Ch. 6 I am unpacking to /LFS/packages/temp6.
If you followed the commands to install patch exactly as they were in chapter 5, then the executable should have been placed in either /bin or /usr/bin. So my only guesses are:
1) You accidentally mis-typed the path string when you chroot'ed
2) You accidentally left off the prefix argument for patch
Where is teh static version of patch located on your drive?
Hmmmm... the only patch I have is in /packages/temp/Patch-2.5.4. No find hits in any of the lib directories. So, I must've missed something in Chapter 5. I was being vewie vewie careful though...
Which bin directory should patch be in, /bin or /usr/bin? I'm assuming /usr/bin, since that's where it is on this red hat machine. Also, I'm assuming that I can now just simply copy patch from /packages/temp/patch-2.5.4 directly into /usr/bin.
Dang! Gotta be careful with all those assumings....
In that case, are you sure you executed the "make install" part of the patch installation? If the only place you have patch is in the directory you compiled it in, that would likely be the case.
As for my /bin and /usr/bin comment, it should be located in $LFS/static/bin. I was getting a little ahead of myself. When you compile patch again later in chapter 6, it will be put in /usr/bin. Any and all of your statically compiled programs will reside in $LFS/static/bin.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.