[Nix-dev] Re: [Nix-commits] SVN commit: nix - 18534 - viric - in nixpkgs/branches/stdenv-updates/pkgs: build-support/gcc-cross-wrapper development/compilers/gcc-4.3 development/interpreters/guile development/libraries/glibc-2.9 development/libraries/physfs dev

[Nicolas Pierron]

On Mon, Nov 23, 2009 at 12:19, Lluís Batlle <viriketo at gmail.com> wrote:
> 2009/11/23 Nicolas Pierron <nicolas.b.pierron at gmail.com>:
>> On Sun, Nov 22, 2009 at 20:51, Llus Batlle <viriketo at gmail.com> wrote:
>>> - Fixed the generic stdenv expression, which did a big mess on buildInputs and
>>>  buildNativeInputs. Now it distinguishes when there is a stdenvCross or not.
>>>  Maybe we should have a single stdenv and forget about the stdenvCross
>>>  adapter - this could end in a stdenv a bit complex, but simpler than the
>>>  generic stdenv + adapter.
>>
>> Yes & No.  The generic stdenv should handle gccHost and libcHost (not
>> gccCross & glibcCross).  But you still need an adapter to change
>> between the stdenv and to give the abstraction of the hostDrv &
>> buildDrv.  As you mention stdenv give you one derivation which is a
>> sane design.
>>
>> Yes, you need an stdenv which handles cross-compilation attributes.
>> No, you need an adapter to introduce stdenv changes to either build
>> the buildDrv or the hostDrv.
>
> Does this mean that you agree with the actual code, and so you do not
> propose to aim towards any change in the current adapter and generic
> stdenv?
>

No, I mean that you have to move the arguments of the adapter into the
generic stdenv. (gccCross, binutilsCross, ...)  But you don't need to
move the hostDrv & buildDrv in the generic stdenv, the adapter
stdenvCross should only be used to handle 2 stdenv-s, one for the
build-2-build and one for the build-2-host.

-- 
Nicolas Pierron
http://www.linkedin.com/in/nicolasbpierron - http://nbp.name/
Richard Feynman - I think I can safely say that nobody understands
quantum mechanics.