Salut, 2010/3/10 Ludovic Courtès <[email protected]>: > Lluís Batlle <[email protected]> writes: >> 2010/3/10 Ludovic Courtès <[email protected]>: >> ... >> We have different stdenvs for different platforms, and some platforms >> have fixed either glibc or another thing. Cross-building, it gets >> quite flexible; there is "libcCross", and it points to either a uclibc >> or glibc, depending on what the user chose. > > OK, thanks for explaining. > > I don’t think there’s any other case where an attribute name can refer > to different packages, as ‘libc’ in this case. Usually attribute names > correspond to the implementation name (e.g., ‘inetutils’, ‘nettools’), > not to the feature provided (‘ifconfig’).
We have something called "linux". I'm thinking of getting linux 2.4 in, for cross builds. And I have something similar with "uboot", between the usual upstream version, and that of the sheevaplug (forked long ago, and having difficulties to get merged into upstream). > >> I could have done: if (stdenv.cross.libc == "glibc"), and then take >> libiconv as a usual input. Do you prefer this way? This would be easy. > > Why not. It would better reflect the intent IMO. Ok! I will do that. _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
