Hi,

What does the config.log tell you?
Can you post the relevant part from the config.log (a few lines before and after the error part)?

Well, I think this is the most relavent part:

configure:2361: checkinbg for gcc
configure:2377: found /tools/bin/gcc
configure:2384: results: gcc
configure:2631: checking for C compiler version
configure:2634: gcc --version </dev/null >&5
../glibc-2.3.6/configure: line 2635: /tools/bin/gcc: No such file or directory
configure:2537: $? = 127
configure:2639: gcc -v </dev/null >&5
../glibc-2.3.6/configure: line 2640: /tools/bin/gcc: No such file or directory
configure:2642: $? = 127
configure:2644: gcc -v </dev/null >&5
../glibc-2.3.6/configure: line 2645: /tools/bin/gcc: No such file or directory
configure:2647: $? = 127
configure:2651: checking for suffix of object files
configure:2672: gcc -c conftest.c >&5
../glibc-2.3.6/configure: line 2673: /tools/bin/gcc: No such file or directory
cinfigure:2675: $? = 127
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "GNU C LIBRARY"
| #define PACKAGE_TARNAME "c-library"
| #define PACKAGE_VERSION "(see version.h)"
| #define PACKAGE_STRING "GNU C Library (see version.h)"
| #define PACKAGE_BUGREPORT "glibc"
| #define USE_REGPARMS 1
| /* end condefs.h */


There is more, but I don't think it's revelant. By the looks of it, it is GCC which is causing the problem.

Any ideas?

Thanks,

Tom

Hi,

Yes, that looks like the relevant part.

I've got more questions.

All from within the chrooted environment and a correctly set up base:

- Does gcc -v work,
- what about /tools/bin/gcc -v,
- What's your PATH setting.

I've seen questions about this problem before and the solution is not clear. Some redo all for glibc and it 'suddenly' seems to works, some link /tools/bin/gcc to /bin/gcc (which could give you problems on a later date if you decide to remove the tools dir) and some start over using a different LFS (liveCD) version.

Hopefully there's a solution after you post the answers to my questions.

Both Questions 1 and 2 produce:

bash: /tools/bin/gcc: No such file or directory

When i enter echo $PATH i get:

/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin


Hope this is what you meant?

Thanks,

Tom

Hi,

That's exactly what I meant, but not what I was hoping for .....

Which LFS version are you building (6.1.1, 6.2 ??) I'm not interested in the liveCD version (it's 6.2-2, you mentioned that. 6.2-3 works like a charm, just installed lfs 6.2 from this liveCD, no problems whatsoever).

Oh, just thought of this: What happens when you do this:

cd /tools/bin
./gcc -v

The .pdf just says 6.2.


cd /tools/bin
./gcc -v produces ./gcc No such file or directory


Shall I just start from the beginning of the book again with my current live cd?
Or would it be better to download the 6.2-3 and re-start using that?

Thanks,

Tom

Hi,

You could try and solve this, but if this is your first LFS I wouldn't. There's enough to learn without the hassle of debugging, trying this and that and in the end not knowing if your result will be stable/useful.

I did notice over time that most of the errors and dead-ends are caused by not following the book (due to typo's, misunderstanding and personalized edits). Don't deviate from the book, especially if it is your first LFS.

Download/burn the 6.2-3 liveCD use the packages that are on the cd. The documentation is also included.

Too bad your problem could not be solved, but maybe this is for the best.

ok, thanks for all your help

Tom

oops... delete this plz...

druuna,
I was joking about having a special version of tar. My tar is exactly what LFS-6.1.1 says [it's version 1.15.1] and there's absolutely nothing special about it. I know that other versions of tar need the -z or -j option [tar in my FC3 distro is an example].

Hi,

If you have tar version 1.15 or higher you indeed do not need the Z, z or j option, it's auto-detected.