2017-01-21 12:49:24 +00:00
|
|
|
{ stdenv, lib, autoconf213, fetchurl, fetchpatch, pkgconfig, nspr, perl, python2, zip }:
|
2011-12-15 12:13:36 +00:00
|
|
|
|
2019-08-13 22:52:01 +01:00
|
|
|
stdenv.mkDerivation {
|
2019-08-15 13:41:18 +01:00
|
|
|
pname = "spidermonkey";
|
2016-11-10 22:26:11 +00:00
|
|
|
version = "1.8.5";
|
2011-12-15 12:13:36 +00:00
|
|
|
|
|
|
|
|
src = fetchurl {
|
2016-11-10 22:26:11 +00:00
|
|
|
url = "mirror://mozilla/js/js185-1.0.0.tar.gz";
|
2011-12-15 12:13:36 +00:00
|
|
|
sha256 = "5d12f7e1f5b4a99436685d97b9b7b75f094d33580227aa998c406bbae6f2a687";
|
|
|
|
|
};
|
|
|
|
|
|
2013-09-30 13:48:16 +01:00
|
|
|
propagatedBuildInputs = [ nspr ];
|
|
|
|
|
|
treewide: isArm -> isAarch32
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
2018-03-20 02:41:06 +00:00
|
|
|
nativeBuildInputs = [ pkgconfig ] ++ lib.optional stdenv.isAarch32 autoconf213;
|
2017-09-05 22:26:13 +01:00
|
|
|
buildInputs = [ perl python2 zip ];
|
2011-12-15 12:13:36 +00:00
|
|
|
|
|
|
|
|
postUnpack = "sourceRoot=\${sourceRoot}/js/src";
|
|
|
|
|
|
|
|
|
|
preConfigure = ''
|
2015-10-05 16:45:54 +01:00
|
|
|
export NIX_CFLAGS_COMPILE="$NIX_CFLAGS_COMPILE -I${nspr.dev}/include/nspr"
|
2011-12-15 12:13:36 +00:00
|
|
|
export LIBXUL_DIST=$out
|
treewide: isArm -> isAarch32
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
2018-03-20 02:41:06 +00:00
|
|
|
${lib.optionalString stdenv.isAarch32 "autoreconf --verbose --force"}
|
2011-12-15 12:13:36 +00:00
|
|
|
'';
|
|
|
|
|
|
2017-01-21 12:49:24 +00:00
|
|
|
patches = [
|
|
|
|
|
(fetchpatch {
|
|
|
|
|
name = "gcc6.patch";
|
2018-07-01 15:39:51 +01:00
|
|
|
url = "https://sources.debian.org/data/main/m/mozjs/1.8.5-1.0.0+dfsg-6/debian/patches/fix-811665.patch";
|
2017-01-21 12:49:24 +00:00
|
|
|
sha256 = "1q8477xqxiy5d8376k5902l45gd0qkd4nxmhl8vr6rr1pxfcny99";
|
|
|
|
|
})
|
treewide: isArm -> isAarch32
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
2018-03-20 02:41:06 +00:00
|
|
|
] ++ stdenv.lib.optionals stdenv.isAarch32 [
|
2016-07-03 12:32:51 +01:00
|
|
|
# Explained below in configureFlags for ARM
|
2016-11-10 22:26:11 +00:00
|
|
|
./1.8.5-findvanilla.patch
|
2016-07-03 12:32:51 +01:00
|
|
|
# Fix for hard float flags.
|
2016-11-10 22:26:11 +00:00
|
|
|
./1.8.5-arm-flags.patch
|
2014-09-18 21:05:52 +01:00
|
|
|
];
|
|
|
|
|
|
|
|
|
|
patchFlags = "-p3";
|
|
|
|
|
|
|
|
|
|
# On the Sheevaplug, ARM, its nanojit thing segfaults in japi-tests in
|
|
|
|
|
# "make check". Disabling tracejit makes it work, but then it needs the
|
|
|
|
|
# patch findvanilla.patch do disable a checker about allocator safety. In case
|
|
|
|
|
# of polkit, which is what matters most, it does not override the allocator
|
|
|
|
|
# so the failure of that test does not matter much.
|
|
|
|
|
configureFlags = [ "--enable-threadsafe" "--with-system-nspr" ] ++
|
2018-08-20 20:11:29 +01:00
|
|
|
stdenv.lib.optionals (stdenv.hostPlatform.system == "armv5tel-linux") [
|
2018-12-22 11:49:41 +00:00
|
|
|
"--with-cpu-arch=armv5t"
|
2014-09-18 21:05:52 +01:00
|
|
|
"--disable-tracejit" ];
|
2013-11-30 08:24:35 +00:00
|
|
|
|
|
|
|
|
# hack around a make problem, see https://github.com/NixOS/nixpkgs/issues/1279#issuecomment-29547393
|
2016-07-03 12:32:51 +01:00
|
|
|
preBuild = ''
|
|
|
|
|
touch -- {.,shell,jsapi-tests}/{-lpthread,-ldl}
|
treewide: isArm -> isAarch32
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
2018-03-20 02:41:06 +00:00
|
|
|
${if stdenv.isAarch32 then "rm -r jit-test/tests/jaeger/bug563000" else ""}
|
2016-07-03 12:32:51 +01:00
|
|
|
'';
|
2013-11-30 08:24:35 +00:00
|
|
|
|
2013-11-30 08:47:02 +00:00
|
|
|
enableParallelBuilding = true;
|
|
|
|
|
|
2013-11-30 08:24:35 +00:00
|
|
|
doCheck = true;
|
2013-12-29 19:15:01 +00:00
|
|
|
|
|
|
|
|
preCheck = ''
|
|
|
|
|
rm jit-test/tests/sunspider/check-date-format-tofte.js # https://bugzil.la/600522
|
|
|
|
|
'';
|
2013-11-30 08:24:35 +00:00
|
|
|
|
2011-12-15 12:13:36 +00:00
|
|
|
meta = with stdenv.lib; {
|
2013-11-30 08:24:35 +00:00
|
|
|
description = "Mozilla's JavaScript engine written in C/C++";
|
|
|
|
|
homepage = https://developer.mozilla.org/en/SpiderMonkey;
|
|
|
|
|
# TODO: MPL/GPL/LGPL tri-license.
|
|
|
|
|
maintainers = [ maintainers.goibhniu ];
|
2016-08-02 18:50:55 +01:00
|
|
|
platforms = platforms.linux;
|
2018-08-21 18:47:51 +01:00
|
|
|
broken = stdenv.isAarch64; # 2018-08-21, broken since 2017-03-08
|
2011-12-15 12:13:36 +00:00
|
|
|
};
|
|
|
|
|
}
|
2013-11-30 08:24:35 +00:00
|
|
|
|
