This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Aw: Re: Aw: Re: How to compile gcc toolchain with special sysroot correctly?
- From: Andrew Haley <aph at redhat dot com>
- To: johannes89 at mailueberfall dot de
- Cc: gcc-help at gcc dot gnu dot org
- Date: Wed, 27 Nov 2013 11:50:53 +0000
- Subject: Re: Aw: Re: Aw: Re: How to compile gcc toolchain with special sysroot correctly?
- Authentication-results: sourceware.org; auth=none
- References: <trinity-425a7633-38e3-434e-98e7-055d18333fd0-1385552120647 at 3capp-gmx-bs06>
On 11/27/2013 11:35 AM, johannes89@mailueberfall.de wrote:
>>> Ok, but the problem occured when I tried to compile glibc (it was missing it when I configured it). Do you mean I require an old glibc to compile a new one?
>>
>> Yes, you do, because the configure tests are trying to link a program.
>> That isn't going to work unless there is a C library.
>
> Is the glibc only needed for the configure tests, but not for the
> make call?
Hard to say. It doesn't really matter, because the resulting libc
will be standalone.
> I understand that a glibc might be needed to test the
> compiler's feature, but a libc which is linked to another libc
> sounds a bit strange. I guess glibc should be able to build crti.o
> without linking to another crti.o?
Yes.
> Also, can you please explain a good way to solve the problem? Would
> you soft-link the missing files, or should I set a variable like
> LD_LIBRARY_PATH? Sorry - I am new to this.
I'd populate the sysroot with the files.
Andrew.