6310a9a3be
If gnum4 is built outside of a chroot, it will decide to use /run/current-system/sw/bin/sh as the shell for "syscmd". (It gets this path via "getconf PATH". Maybe our Glibc shouldn't return that path, at least not during Nix builds...) If such a build of gnum4 is subsequently used *inside* a chroot, it won't work because /run/current-system doesn't exist. So specify an explicit path to the shell.
44 lines
1.6 KiB
Nix
44 lines
1.6 KiB
Nix
{ stdenv, fetchurl }:
|
|
|
|
stdenv.mkDerivation rec {
|
|
name = "gnum4-1.4.17";
|
|
|
|
src = fetchurl {
|
|
url = "mirror://gnu/m4/m4-1.4.17.tar.bz2";
|
|
sha256 = "0w0da1chh12mczxa5lnwzjk9czi3dq6gnnndbpa6w4rj76b1yklf";
|
|
};
|
|
|
|
doCheck = !stdenv.isDarwin
|
|
&& !stdenv.isCygwin # XXX: `test-dup2' fails on Cygwin
|
|
&& !stdenv.isSunOS; # XXX: `test-setlocale2.sh' fails
|
|
|
|
configureFlags = "--with-syscmd-shell=${stdenv.shell}";
|
|
|
|
# Upstream is aware of it; it may be in the next release.
|
|
patches = [ ./s_isdir.patch ];
|
|
|
|
meta = {
|
|
homepage = http://www.gnu.org/software/m4/;
|
|
description = "GNU M4, a macro processor";
|
|
|
|
longDescription = ''
|
|
GNU M4 is an implementation of the traditional Unix macro
|
|
processor. It is mostly SVR4 compatible although it has some
|
|
extensions (for example, handling more than 9 positional
|
|
parameters to macros). GNU M4 also has built-in functions for
|
|
including files, running shell commands, doing arithmetic, etc.
|
|
|
|
GNU M4 is a macro processor in the sense that it copies its
|
|
input to the output expanding macros as it goes. Macros are
|
|
either builtin or user-defined and can take any number of
|
|
arguments. Besides just doing macro expansion, m4 has builtin
|
|
functions for including named files, running UNIX commands,
|
|
doing integer arithmetic, manipulating text in various ways,
|
|
recursion etc... m4 can be used either as a front-end to a
|
|
compiler or as a macro processor in its own right.
|
|
'';
|
|
|
|
license = stdenv.lib.licenses.gpl3Plus;
|
|
};
|
|
|
|
}
|