ba52ae5048
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
68 lines
2.3 KiB
Nix
68 lines
2.3 KiB
Nix
{ stdenv, fetchurl, ncurses, xlibsWrapper }:
|
|
|
|
let
|
|
useX11 = !stdenv.isAarch32 && !stdenv.isMips;
|
|
useNativeCompilers = !stdenv.isMips;
|
|
inherit (stdenv.lib) optionals optionalString;
|
|
in
|
|
|
|
stdenv.mkDerivation rec {
|
|
name = "ocaml-${version}";
|
|
version = "4.00.1";
|
|
|
|
src = fetchurl {
|
|
url = "http://caml.inria.fr/pub/distrib/ocaml-4.00/${name}.tar.bz2";
|
|
sha256 = "33c3f4acff51685f5bfd7c260f066645e767d4e865877bf1613c176a77799951";
|
|
};
|
|
|
|
prefixKey = "-prefix ";
|
|
configureFlags = ["-no-tk"] ++ optionals useX11 [ "-x11lib" xlibsWrapper ];
|
|
buildFlags = "world" + optionalString useNativeCompilers " bootstrap world.opt";
|
|
buildInputs = [ncurses] ++ optionals useX11 [ xlibsWrapper ];
|
|
installTargets = "install" + optionalString useNativeCompilers " installopt";
|
|
preConfigure = ''
|
|
CAT=$(type -tp cat)
|
|
sed -e "s@/bin/cat@$CAT@" -i config/auto-aux/sharpbang
|
|
'';
|
|
postBuild = ''
|
|
mkdir -p $out/include
|
|
ln -sv $out/lib/ocaml/caml $out/include/caml
|
|
'';
|
|
|
|
passthru = {
|
|
nativeCompilers = useNativeCompilers;
|
|
};
|
|
|
|
meta = with stdenv.lib; {
|
|
homepage = http://caml.inria.fr/ocaml;
|
|
branch = "4.00";
|
|
license = with licenses; [
|
|
qpl /* compiler */
|
|
lgpl2 /* library */
|
|
];
|
|
description = "Most popular variant of the Caml language";
|
|
|
|
longDescription =
|
|
''
|
|
OCaml is the most popular variant of the Caml language. From a
|
|
language standpoint, it extends the core Caml language with a
|
|
fully-fledged object-oriented layer, as well as a powerful module
|
|
system, all connected by a sound, polymorphic type system featuring
|
|
type inference.
|
|
|
|
The OCaml system is an industrial-strength implementation of this
|
|
language, featuring a high-performance native-code compiler (ocamlopt)
|
|
for 9 processor architectures (IA32, PowerPC, AMD64, Alpha, Sparc,
|
|
Mips, IA64, HPPA, StrongArm), as well as a bytecode compiler (ocamlc)
|
|
and an interactive read-eval-print loop (ocaml) for quick development
|
|
and portability. The OCaml distribution includes a comprehensive
|
|
standard library, a replay debugger (ocamldebug), lexer (ocamllex) and
|
|
parser (ocamlyacc) generators, a pre-processor pretty-printer (camlp4)
|
|
and a documentation generator (ocamldoc).
|
|
'';
|
|
|
|
platforms = with platforms; linux;
|
|
};
|
|
|
|
}
|