Regarding Patches and a failure in the GCC Compilation

arcelios · 07-11-2008, 05:27 PM

This question is going to be two questions rolled into one.

1. How do you apply patches?
I understand how to run a .patch file, but I'm afraid that I do not know where to place the patch file when running it. Whenever I attempt to run a .patch file, it asks me which file I would like to patch, prompting me for a path. I have been using Linux for some time now, but I hadn't run into a .patch file until now.

2. How do I fix this error with the GCC Compilation?
On page 5.4 of LFS current stable, it tells me to to type:

Code:

make bootstrap

I type this, and it goes through the normal quick-scrolling text that a make command usually generates, but then it stops suddenly, with an error. Here are the last several lines of the make:

Code:

configure: creating ./config.status
config.status: creating Makefile
config.status: creating testsuite/Makefile
config.status: creating config.h
config.status: executing default commands
make[1]: Entering directory '/mnt/lfs/sources/gcc-4.0.3/build-i686-pc-linux-gnu/libiberty'
make[1]: *** No rule to make target '../include/ansidecl.h', needed by 'regex.o'. Stop.
make[1]: Leaving directory '/mnt/lfs/sources/gcc-4.0.3/build-i686-pc-linux-gnu/libiberty'
make: *** [all-build-libiberty] Error 2

Then it just brings me back to the standard prompt:

Code:

lfslivecd:root | Fri 11 Jul 2008 6:07:38 PM GMT | /mnt/lfs/sources/gcc-4.0.3
# _

Help much appreciated!

--
Arc

gerald_M2B · 07-11-2008, 09:56 PM

The patch file can be placed anywhere, but the path that is given must show where to find it. The strip count may be different, depending on where you are patching from, in the TOPSOURCE directory, or its parent.
Put the whole patch thing into the command line, and it will not prompt you.

On the second question, use the versions that are listed in the LFS book to avoid running into pesky problems. 4.0.3 is old, LFS-6.3 is 4.1.2
When trying versions not used in the book, there may be files that are missing.
Usually I would try to locate the file, and put a link in the appropriate place where that is expected, and try again. It can take as many as three times to get through the compiler, otherwise I bail out.

Gerald

dracayr · 07-12-2008, 07:25 AM

the book will tell you when and how to use the patch files in the corresponding chapters

dracayr