[Nix-dev] Re: [Nix-commits] SVN commit: nix - 18833 - viric - in nixpkgs/branches/stdenv-updates/pkgs: development/compilers/gcc-4.3 development/compilers/gcc-4.4 top-level

[Ludovic Courtès]

Hey,

Lluís Batlle <viriketo at gmail.com> writes:

> Now I solved it better, as I commented. FLAGS_FOR_TARGET, and no
> libtool patch. I think this will make you happy. :)

Yes, I like it better, thanks!

>>>>  If you are not building a C library in the same source tree as GCC,
>>>>  you should also provide the target libraries and headers before
>>>>  configuring GCC, specifying the directories with --with-sysroot or
>>>>  --with-headers and --with-libs.
>>> How would I get target libraries, if I don't have any cross-compiler
>>> to build them?
>>
>> The target libs are built with the just-built cross compiler, as
>> explained in build.html.
> You said "...  you should also provide the target libraries and
> headers ...". I did not mean the target libs coming with gcc.

This sentence is quoted from build.html.  I presume “target libraries”
refers to glibc, GMP, MPFR, etc., in this context.

>>> And for glibc to be able to install proper headers, I think it would
>>> need at least to be able to run a target compiler for some configure
>>> tests. But this latter is only a guess.
>>
>> I think this bootstrapping issue is not too different from that of
>> ‘stdenvLinux’, is it?
> It goes quite different.
> stdenvLinux bootstraps having a gcc, a g++, and a glibc ready for the
> platform. So we can either build a new gcc, a new glibc, or whatever
> in nixpkgs, I'd say.
>
> Creating a cross-toolchain, we start without any target library, and
> without a cross compiler.

Right.  So how did you address it with 4.3?

Thanks,
Ludo’.