Group: Software/research/ProgrammingLanguages
(→Compilers features and languages: gcc gnat was used) |
(→Parabola status: Ruby is now fixed in Parabola. I tested on x86_64 and I can even run ruby programs.) |
||
(24 intermediate revisions by 2 users not shown) | |||
Line 15: | Line 15: | ||
! Automake | ! Automake | ||
! Libtool<ref name="libtool">libtool is part of the autotools and it abstracts linking to make it work on a lot of operating systems. The status of the programming languages other than C and C++ can be found here: https://www.gnu.org/software/libtool/manual/libtool.html#Tags</ref> | ! Libtool<ref name="libtool">libtool is part of the autotools and it abstracts linking to make it work on a lot of operating systems. The status of the programming languages other than C and C++ can be found here: https://www.gnu.org/software/libtool/manual/libtool.html#Tags</ref> | ||
− | ! GCC | + | ! GCC 13 support<ref>Compared with other compilers like LLVM and rustc, GCC supports many CPU architectures and it's quite well integrated with various other software (gdb, gprof, build systems, etc). It also has long term support in mind as it continues to support other programming language standards. It also has good documentation that explain how it handles C code for instance. In addition it's a GNU project, so it has users freedom in mind. In addition Guix has made GCC bootstrapable from a binary that is less than 1KB, and it doesn't require huge resources to build or bootstrap.</ref> |
+ | ! Other free compilers | ||
! Shared libraries<ref name="shared-libraries">Shared libraries systems enable way better performances on older computers as it uses way less RAM.</ref> | ! Shared libraries<ref name="shared-libraries">Shared libraries systems enable way better performances on older computers as it uses way less RAM.</ref> | ||
! Microcontrollers<ref name="microcontrollers">Can we compile and/or run code for/on microcontrollers, if so which compilers/interpreters are used / necessary for that.</ref> | ! Microcontrollers<ref name="microcontrollers">Can we compile and/or run code for/on microcontrollers, if so which compilers/interpreters are used / necessary for that.</ref> | ||
Line 23: | Line 24: | ||
| | | | ||
| | | | ||
+ | | | ||
+ | | {{yes}}<ref name="gcc-supported-languages">https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/G_002b_002b-and-GCC.html</ref> | ||
| | | | ||
| {{yes}} | | {{yes}} | ||
− | + | | {{yes|GCC}}<ref>At the FOSDEM 2023 I was told at the Ada table that it worked fine on microcontrollers with 16k of RAM, and that it was widely used in microcontrollers. The table also had several microcontroller boards.</ref> | |
− | | {{yes|GCC}}<ref>At the FOSDEM 2023 I was told at the | + | | {{yes}}<ref>The ISO standard specification can be found [http://www.ada-auth.org/arg.html here]. It is provided by the ARG (Ada Rapporteur Group) free of charge and the license allows for modifications and reproductions while requiring the license to be reproduced.</ref> |
− | | | ||
|- | |- | ||
! C | ! C | ||
Line 33: | Line 35: | ||
| {{yes}} | | {{yes}} | ||
| {{yes}} | | {{yes}} | ||
− | | {{yes}} | + | | {{yes}}<ref name="gcc-supported-languages"></ref> |
+ | | | ||
+ | * [https://packages.guix.gnu.org/packages/cc65/ cc65] | ||
+ | * [https://packages.guix.gnu.org/packages/clang/ clang] | ||
+ | * [https://packages.guix.gnu.org/packages/dev86/ dev86] | ||
+ | * [https://packages.guix.gnu.org/packages/mes mes] | ||
+ | * [https://packages.guix.gnu.org/packages/tcc tcc] | ||
+ | * [https://packages.guix.gnu.org/packages/sdcc sdcc] | ||
| {{yes|defaults to shared libraries}} | | {{yes|defaults to shared libraries}} | ||
| {{yes|GCC, SDCC}} | | {{yes|GCC, SDCC}} | ||
Line 42: | Line 51: | ||
| {{yes}} | | {{yes}} | ||
| {{yes}} | | {{yes}} | ||
− | | {{yes}} | + | | {{yes}}<ref name="gcc-supported-languages"></ref> |
+ | | | ||
| {{yes|defaults to shared libraries}} | | {{yes|defaults to shared libraries}} | ||
| {{yes|GCC, other?}} | | {{yes|GCC, other?}} | ||
Line 51: | Line 61: | ||
| | | | ||
| | | | ||
− | | {{yes}} | + | | {{yes}}<ref name="gcc-supported-languages"></ref> |
| | | | ||
| | | | ||
Line 60: | Line 70: | ||
| | | | ||
| | | | ||
− | | {{no}} | + | | {{no}}<ref name="gcc-supported-languages"></ref> |
+ | | | ||
| | | | ||
| | | | ||
Line 69: | Line 80: | ||
| {{yes|Fortran 77, Fortran 9x}} | | {{yes|Fortran 77, Fortran 9x}} | ||
| {{yes|Fortran, Fortran 77}} | | {{yes|Fortran, Fortran 77}} | ||
− | | {{yes}} | + | | {{yes}}<ref name="gcc-supported-languages"></ref> |
+ | | | ||
| | | | ||
| | | | ||
| ? | | ? | ||
+ | |- | ||
+ | ! GNU C | ||
+ | | {{yes}} | ||
+ | | {{yes}} | ||
+ | | {{yes}} | ||
+ | | {{yes}}<ref name="gcc-supported-languages"></ref> | ||
+ | | | ||
+ | * [https://packages.guix.gnu.org/packages/clang/ clang]<ref>https://clang.llvm.org/features.html#gcccompat</ref> | ||
+ | * [https://packages.guix.gnu.org/packages/tcc tcc] | ||
+ | | {{yes|defaults to shared libraries}} | ||
+ | | {{yes|GCC}} | ||
+ | | {{yes|Documented under the GFDL.}}<ref>https://www.gnu.org/software/gnu-c-manual/</ref> | ||
|- | |- | ||
! Go | ! Go | ||
Line 78: | Line 102: | ||
| {{orange|no}}<ref>While automake isn't supported, it's still possible to use it if we add a rule to handle .go files in our Makefile.am. [https://mail.gnu.org/archive/html/automake-patches/2001-07/msg00012.html For some reasons] we then also need to add link rules for every program/library we create. I've created a [https://framagit.org/GNUtoo/autotools-go-hello-world autotools-go-hello-world] project to show how to use autoconf and automake together with go. Note that I didn't look if that scaled well or the limitations in more complex projects. For instance I'm unsure how to handle shared libraries, how to link to dependencies, etc.</ref> | | {{orange|no}}<ref>While automake isn't supported, it's still possible to use it if we add a rule to handle .go files in our Makefile.am. [https://mail.gnu.org/archive/html/automake-patches/2001-07/msg00012.html For some reasons] we then also need to add link rules for every program/library we create. I've created a [https://framagit.org/GNUtoo/autotools-go-hello-world autotools-go-hello-world] project to show how to use autoconf and automake together with go. Note that I didn't look if that scaled well or the limitations in more complex projects. For instance I'm unsure how to handle shared libraries, how to link to dependencies, etc.</ref> | ||
| {{yes}} | | {{yes}} | ||
− | | {{yes}} | + | | {{yes}}<ref name="gcc-supported-languages"></ref> |
| | | | ||
| | | | ||
Line 87: | Line 111: | ||
| {{yes|with CGJ}} | | {{yes|with CGJ}} | ||
| {{yes|with CGJ}} | | {{yes|with CGJ}} | ||
− | | {{no}} | + | | {{no}}<ref name="gcc-supported-languages"></ref><ref>The last GCC version supporting GCJ seems to be 6.5.0: https://gcc.gnu.org/onlinedocs/gcc-6.5.0/gcc/G_002b_002b-and-GCC.html#G_002b_002b-and-GCC</ref> |
| | | | ||
| | | | ||
Line 96: | Line 120: | ||
| {{yes}} | | {{yes}} | ||
| | | | ||
− | | {{yes}} | + | | {{yes}}<ref name="gcc-supported-languages"></ref> |
+ | | | ||
| | | | ||
| | | | ||
Line 105: | Line 130: | ||
| {{yes}} | | {{yes}} | ||
| | | | ||
− | | {{yes}} | + | | {{yes}}<ref name="gcc-supported-languages"></ref> |
+ | | | ||
| | | | ||
| | | | ||
Line 114: | Line 140: | ||
| {{no}} | | {{no}} | ||
| {{no}} | | {{no}} | ||
− | | {{no|Work in progress}} | + | | {{no|Work in progress}}<ref name="gcc-supported-languages"></ref> |
+ | | | ||
| | | | ||
| | | | ||
Line 123: | Line 150: | ||
| {{yes|partial}} | | {{yes|partial}} | ||
| | | | ||
− | | {{no}} | + | | {{no}}<ref name="gcc-supported-languages"></ref> |
+ | | | ||
| | | | ||
| | | | ||
Line 133: | Line 161: | ||
| | | | ||
| {{yes|valac uses GCC}} | | {{yes|valac uses GCC}} | ||
+ | | | ||
+ | * [https://packages.guix.gnu.org/packages/vala/ valac] | ||
| | | | ||
| {{no|depends on glib}} | | {{no|depends on glib}} | ||
Line 171: | Line 201: | ||
! Microcontrollers<ref name="microcontrollers"></ref> | ! Microcontrollers<ref name="microcontrollers"></ref> | ||
! Strict specifications<ref name="strict-specifications"></ref> | ! Strict specifications<ref name="strict-specifications"></ref> | ||
+ | |- | ||
+ | ! Perl | ||
+ | | Perl | ||
+ | | {{yes|C, some C libraries}} | ||
+ | | {{no}} | ||
+ | | {{no}}<ref>From [https://en.wikipedia.org/wiki/Perl#Implementation Wikipedia article on perl]: "No written specification or standard for the Perl language exists for Perl versions through Perl 5"</ref> | ||
|- | |- | ||
! rowspan="2" | Python | ! rowspan="2" | Python | ||
Line 181: | Line 217: | ||
| {{yes|C, some C libraries}} | | {{yes|C, some C libraries}} | ||
| {{yes}} | | {{yes}} | ||
+ | |- | ||
|} | |} | ||
Line 250: | Line 287: | ||
| {{Orange}} | | {{Orange}} | ||
| {{Orange}} | | {{Orange}} | ||
− | | {{ | + | | {{Yes|Bootstraped from source with a 25 MiB Guile binary.}}<ref name="reduced-binary-seed-manual-section">https://guix.gnu.org/en/blog/2023/the-full-source-bootstrap-building-from-source-all-the-way-down</ref> |
| {{Orange}} | | {{Orange}} | ||
| {{Orange}} | | {{Orange}} | ||
| {{Orange}} | | {{Orange}} | ||
| {{Orange}} | | {{Orange}} | ||
− | | {{ | + | | {{Yes|Bootstraped from source with a 25 MiB Guile binary}}<ref name="reduced-binary-seed-manual-section"></ref> |
| {{Orange}} | | {{Orange}} | ||
| {{Orange}} | | {{Orange}} | ||
Line 267: | Line 304: | ||
| {{no}} | | {{no}} | ||
| {{no}} | | {{no}} | ||
− | | {{Orange|Bootstrapped from ghc-4 | + | | {{Orange|Bootstrapped from generated C code}}<ref name="guix-ghc-4">https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/haskell.scm?h=v1.4.0#n363</ref> |
| {{no}} | | {{no}} | ||
| {{no}} | | {{no}} | ||
| {{no}} | | {{no}} | ||
| {{no}} | | {{no}} | ||
− | | {{Orange|Bootstrapped from ghc-4 | + | | {{Orange|Bootstrapped from generated C code}}<ref name="guix-ghc-4"></ref> |
| {{no}} | | {{no}} | ||
| {{no}} | | {{no}} | ||
Line 384: | Line 421: | ||
| {{yes}} | | {{yes}} | ||
| {{yes}} | | {{yes}} | ||
+ | |- | ||
+ | | Ruby | ||
+ | | ruby | ||
+ | | {{yes}}<ref name="parabola-ruby">Before it was broken due to the removal of rubygems, but it now works agains thanks to libre/ruby.</ref> | ||
+ | | {{yes}}<ref name="parabola-ruby"></ref> | ||
+ | | {{yes}}<ref name="parabola-ruby"></ref> | ||
|- | |- | ||
| Rust | | Rust | ||
Line 397: | Line 440: | ||
| {{yes}} | | {{yes}} | ||
|- | |- | ||
+ | |} | ||
+ | |||
+ | == Trisquel 11 (aramo) == | ||
+ | |||
+ | {| border="0" style="font-size: smaller" | ||
+ | <!-- Below is the column for easy copy-paste and replacement --> | ||
+ | <!-- Language --> | ||
+ | <!-- Toolchain --> | ||
+ | <!-- amd64 --> | ||
+ | <!-- arm64 --> | ||
+ | <!-- armhf --> | ||
+ | <!-- ppc64el --> | ||
+ | |- bgcolor="#6699ff" | ||
+ | ! Language | ||
+ | ! Toolchain | ||
+ | ! amd64 | ||
+ | ! arm64 | ||
+ | ! armhf | ||
+ | ! ppc64el | ||
+ | |- | ||
+ | | Ada | ||
+ | | [https://packages.trisquel.org/aramo/gnat gcc-ada] | ||
+ | | {{yes}} | ||
+ | | {{yes}} | ||
+ | | {{yes}} | ||
+ | | {{yes}} | ||
+ | |- | ||
+ | | C# | ||
+ | | [https://packages.trisquel.org/aramo/all/mono-mcs mono] | ||
+ | | {{yes}}<ref name="mono-mcs">mono-mcs is architecture independent. It depends on packages like [https://packages.trisquel.org/aramo/mono-runtime mono-runtime] which works on amd64, arm64, armhf, ppc64el.</ref> | ||
+ | | {{yes}}<ref name="mono-mcs"></ref> | ||
+ | | {{yes}}<ref name="mono-mcs"></ref> | ||
+ | | {{yes}}<ref name="mono-mcs"></ref> | ||
+ | |- | ||
+ | | Haskell | ||
+ | | [https://packages.trisquel.org/aramo/ghc ghc] | ||
+ | | {{yes}} | ||
+ | | {{yes}} | ||
+ | | {{yes}} | ||
+ | | {{yes}} | ||
|} | |} | ||
Latest revision as of 11:15, 13 September 2024
Contents
Introduction
The goal of this page is to understand the status of various programming languages and toolchains. It can help people deciding on a programming language to choose or to learn, or enable people to understand where distributions need contributions to support well a language.
It could also contain information on what language works where or if we can target specific operating systems with free software or not.
Toolchain status
Compilers features and languages
Language | Autoconf | Automake | Libtool[1] | GCC 13 support[2] | Other free compilers | Shared libraries[3] | Microcontrollers[4] | Strict specifications[5] |
---|---|---|---|---|---|---|---|---|
Ada | Yes[6] | Yes | GCC[7] | Yes[8] | ||||
C | Yes | Yes | Yes | Yes[6] | defaults to shared libraries | GCC, SDCC | Drafts are available gratis, probably not under free licenses.[9] | |
C++ | Yes | Yes | Yes | Yes[6] | defaults to shared libraries | GCC, other? | ? | |
D | Yes[6] | ? | ||||||
Erlang | Yes | No[6] | ? | |||||
Fortran | Fortran 77, Fortran 90, Fortran 95 | Fortran 77, Fortran 9x | Fortran, Fortran 77 | Yes[6] | ? | |||
GNU C | Yes | Yes | Yes | Yes[6] | defaults to shared libraries | GCC | Documented under the GFDL.[11] | |
Go | basic support for gccgo | no[12] | Yes | Yes[6] | ? | |||
Java | with CGJ | with CGJ | No[6][13] | ? | ||||
Objective-C | Yes | Yes | Yes[6] | ? | ||||
Objective-C++ | Yes | Yes | Yes[6] | ? | ||||
Rust | No | No | No | Work in progress[6] | No[14] | |||
Unified Parallel C. | partial | No[6] | ? | |||||
Vala | partial | valac uses GCC | depends on glib | ? |
Compilers bootstraping
Compiler | Languages | Dependencies |
---|---|---|
gcc-ada |
|
Depends on gcc-ada |
nim |
|
nim depends on itself but translated C files are provided by upstream |
valac |
|
valac depends on itself but translated C files are provided by upstream |
Interpreters features and languages
Language | Interpreter | Dependencies | Microcontrollers[4] | Strict specifications[5] |
---|---|---|---|---|
Perl | Perl | C, some C libraries | No | No[15] |
Python | CPython | C, some C libraries | No | ? |
MicroPython | C, some C libraries | Yes |
Build system status
Build system | Cross compilation | Easy to support in distributions | Targets |
---|---|---|---|
Autotools | Yes | Yes | |
setup.py | ? | Yes |
Didstributions status
Guix status
Guix is the most strict FSDG compliant distribution with regard to languages support: it requires the bootstrap process to be reproducible.
While there are still binary compilers being used in the bootstrap process for some languages, other languages are completely bootstrapped from source.
Language | Toolchain | GNU/Hurd i586 | GNU/Linux armv7h | GNU/Linux aarch64 | GNU/Linux i686 | GNU/Linux mips64el | GNU/Linux powerpc | GNU/Linux powerpc64le | GNU/Linux riscv64 | GNU/Linux x86_64 | Mingw i686 | Mingw x86_64 |
---|---|---|---|---|---|---|---|---|---|---|---|---|
Ada | No | |||||||||||
C | gcc-toolchain | Yes | Yes | Yes | Bootstraped from source with a 25 MiB Guile binary.[18] | Yes | Yes | Yes | Yes | Bootstraped from source with a 25 MiB Guile binary[18] | Yes | Yes |
C# | No | |||||||||||
Haskell | ghc | No | No | No | Bootstrapped from generated C code[19] | No | No | No | No | Bootstrapped from generated C code[19] | No | No |
Java | openjdk | ? | ? | ? | bootstraped from source[20] | ? | ? | ? | ? | bootstraped from source[20] | ? | ? |
nim | ? | ? | ? | Bootstrapped from generated C code[21] | ? | ? | ? | ? | Bootstrapped from generated C code[21] | ? | ? | |
Rust | rustc | No[22] | No[22] | Bootstrapped from source with mrustc[22] | No[22] | No[22] | No[22] | No[22] | Bootstrapped from source with mrustc[22] | Bootstrapped from source with mrustc[22] | No[22] | No[22] |
vala | valac | ? | ? | ? | Bootstrapped from generated C code[23] | ? | ? | ? | ? | Bootstrapped from generated C code[23] | ? | ? |
Parabola status
Parabola has a policy which requires all the packages to be built from source. But it doesn't have a policy to reduce the size of the bootstrap binaries, so there can be circular dependencies.
Language | Toolchain | GNU/Linux armv7h | GNU/Linux i686 | GNU/Linux x86_64 |
---|---|---|---|---|
Ada | gcc-ada | No | Yes | Yes |
C | gcc-toolchain | Yes | Yes | Yes |
C# | mono | Yes | Yes | Yes |
Haskell | ghc | No | Yes | Yes |
Java | openjdk | Yes | Yes | Yes |
nim | Yes | Yes | Yes | |
Ruby | ruby | Yes[24] | Yes[24] | Yes[24] |
Rust | rustc | Yes | Yes | Yes |
Vala | valac | Yes | Yes | Yes |
Trisquel 11 (aramo)
Language | Toolchain | amd64 | arm64 | armhf | ppc64el |
---|---|---|---|---|---|
Ada | gcc-ada | Yes | Yes | Yes | Yes |
C# | mono | Yes[25] | Yes[25] | Yes[25] | Yes[25] |
Haskell | ghc | Yes | Yes | Yes | Yes |
Standalone toolchains
Programming languages | Distributor | Release | Host | Target | Source code review | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Adacore | 2021[26] | GNU/Linux (i686?) | ARM ELF 32bit |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GNU/Linux i686 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GNU/Linux x86_64 | RISCV ELF 32bit | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GNU/Linux x86_64 | RISCV ELF 64bit | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GNU/Linux x86_64 |
References
- ↑ libtool is part of the autotools and it abstracts linking to make it work on a lot of operating systems. The status of the programming languages other than C and C++ can be found here: https://www.gnu.org/software/libtool/manual/libtool.html#Tags
- ↑ Compared with other compilers like LLVM and rustc, GCC supports many CPU architectures and it's quite well integrated with various other software (gdb, gprof, build systems, etc). It also has long term support in mind as it continues to support other programming language standards. It also has good documentation that explain how it handles C code for instance. In addition it's a GNU project, so it has users freedom in mind. In addition Guix has made GCC bootstrapable from a binary that is less than 1KB, and it doesn't require huge resources to build or bootstrap.
- ↑ 4.04.1 Can we compile and/or run code for/on microcontrollers, if so which compilers/interpreters are used / necessary for that.
- ↑ 5.05.1 Having a standard or something similar to refer to enables people to write code that can still be used without requiring too much maintenance to adapt to newer compiler versions.
- ↑ 6.006.016.026.036.046.056.066.076.086.096.106.116.12 https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/G_002b_002b-and-GCC.html
- ↑ At the FOSDEM 2023 I was told at the Ada table that it worked fine on microcontrollers with 16k of RAM, and that it was widely used in microcontrollers. The table also had several microcontroller boards.
- ↑ The ISO standard specification can be found here. It is provided by the ARG (Ada Rapporteur Group) free of charge and the license allows for modifications and reproductions while requiring the license to be reproduced.
- ↑ Ideally the specifications should be available under free licenses.
- ↑ https://clang.llvm.org/features.html#gcccompat
- ↑ https://www.gnu.org/software/gnu-c-manual/
- ↑ While automake isn't supported, it's still possible to use it if we add a rule to handle .go files in our Makefile.am. For some reasons we then also need to add link rules for every program/library we create. I've created a autotools-go-hello-world project to show how to use autoconf and automake together with go. Note that I didn't look if that scaled well or the limitations in more complex projects. For instance I'm unsure how to handle shared libraries, how to link to dependencies, etc.
- ↑ The last GCC version supporting GCJ seems to be 6.5.0: https://gcc.gnu.org/onlinedocs/gcc-6.5.0/gcc/G_002b_002b-and-GCC.html#G_002b_002b-and-GCC
- ↑ See one of the two talks on rust in GNU cauldron 2022.
- ↑ From Wikipedia article on perl: "No written specification or standard for the Perl language exists for Perl versions through Perl 5"
- ↑ Autotools contains *a lot* of information and/or workarounds on how to support most Posix-like systems, including less well known systems. See the [1] and automake manuals for more details.
- ↑ https://autotools.info/libtool/windows.html
- ↑ 18.018.1 https://guix.gnu.org/en/blog/2023/the-full-source-bootstrap-building-from-source-all-the-way-down
- ↑ 19.019.1 https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/haskell.scm?h=v1.4.0#n363
- ↑ 20.020.1 In gnu/packages/java.scm icedtea-7 depends on jamvm which depends on jamvm-1-bootstrap which is built from source. The source bootstrap is not architecture specific.
- ↑ 21.021.1 Both the Guix package and the official build instructions use the build.sh script that compiles code (in the c_code directory) that has been generated with the nim compiler.
- ↑ 22.0022.0122.0222.0322.0422.0522.0622.0722.0822.0922.10 See supported-systems in the rust 1.54 package definition
- ↑ 23.023.1 The vala source code contains C files generated from vala source code that is also present in that source code. Since the Guix package and the README.md included in the vala source code require a C compiler but not a vala compiler to compile vala, the C code is then used to build it.
- ↑ 24.024.124.2 Before it was broken due to the removal of rubygems, but it now works agains thanks to libre/ruby.
- ↑ 25.025.125.225.3 mono-mcs is architecture independent. It depends on packages like mono-runtime which works on amd64, arm64, armhf, ppc64el.
- ↑ This release also had additional hosts like Windows and darwin, and additional targets too like "Raspberry Pi 2 Linux (32bits)" but I didn't look into them.
- ↑ Here we used GNU/Linux x86_64 host and target source code for the review. I hope that all the host/target combination have the same source but I didn't check.
- ↑ So far I used 'guix package --show=<package-name>' to find the license. I also didn't check license compatibilities.