[Nix-dev] libiconv on non-GNU systems
Sander van der Burg - EWI
S.vanderBurg at tudelft.nl
Mon Oct 18 13:45:35 CEST 2010
I just removed some of these dirty if system == i686-freebsd lines. They were never consistent. I think the best way of determining whether to use libiconv is to check whether a particular system has glibc and then add libiconv to the buildItems.
Some packages also seem to require libintl on non-glibc platforms, which is part of the GNU gettext package.
-----Original Message-----
From: nix-dev-bounces at cs.uu.nl on behalf of Yury G. Kudryashov
Sent: Mon 10/18/2010 6:45 AM
To: nix-dev at cs.uu.nl
Subject: [Nix-dev] libiconv on non-GNU systems
-----Original Message-----
From: nix-dev-bounces at cs.uu.nl on behalf of Yury G. Kudryashov
Sent: Mon 10/18/2010 6:45 AM
To: nix-dev at cs.uu.nl
Subject: [Nix-dev] libiconv on non-GNU systems
Hi!
# grep libiconv all-packages.nix
libiconv = if stdenv.isDarwin then libiconv else null;
zlib curl gd postgresql openssl pkgconfig sqlite getConfig libiconv
libjpeg libpng;
libiconv = if (stdenv.system == "i686-freebsd") then libiconv else null;
libiconv = if stdenv.system == "i686-freebsd" then libiconv else null;
libiconv = if stdenv.system == "i686-freebsd" then libiconv else null;
libiconv = callPackage ../development/libraries/libiconv { };
Which test should be used instead of all these? I'm going to unify all these
tests into something like
libiconvPkg = callPackage ...;
libiconv = if ... then libiconvPkg else stdenv.gcc.libc;
Then use libiconv everywhere else without re-checking.
_______________________________________________
nix-dev mailing list
nix-dev at cs.uu.nl
https://mail.cs.uu.nl/mailman/listinfo/nix-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20101018/f459c81d/attachment.html
More information about the nix-dev
mailing list