On Thu, Apr 18, 2013 at 04:41:35PM +0200, Matthias Klose wrote: > There are maybe not many use cases where you do want to install an interpreter > like python or perl for a foreign architecture, but there are some use case > where such a setup makes sense. For now I see this limited for architecture > pairs like amd64/i386, armel/armhf, ia64/i386, i.e. for architectures where > the > "foreign" interpreter can be run (without qemu). Use cases are > > - running the OpenJDK hotspot JIT for i386 on ia64, an implementation > which is much faster than the OpenJDK Zero interpreter on ia64. > This can be done today in wheezy. The OpenJDK packages do use > different prefixes and are co-installable. While the packages come > with binaries, these are all installed using alternatives, so the > packages can even be installed for more than architecture (no, I don't > like this alternatives schema much).
Ia64 does no longer (for a while now) support i386. The support has been removed from hardware years ago and from the kernel too. You have to use qemu there. Is that still faster then the ia64 interpreter? > So what is the status for some runtimes/interpreters (would like to see some > follow-up/corrections from package maintainers)? > > - OpenJDK: runtime and development files are co-installable, the > package itself is not cross-buildable, and afaik nobody did try > to cross build any bindings. > > - Perl: Afaik, Neil did prepare the interpreter to cross-build, and > to co-install the runtime and development files. What about > cross-building third party modules? > > - Python: co-installable runtime and development files, cross-buildability > upstreamed for 2.7.4 and 3.3.1. There is a way to cross-build third > party modules using distutils/setuptools. Packages are available in > experimental, but because I didn't backport this to 2.6 and 3.2, not > much useful. Install an Ubuntu raring (13.04) chroot to experiment > with these. Details at http://wiki.debian.org/Python/MultiArch > > - Ruby: Afaik, not yet started on multiarch. > > - Tcl/Tk: Wookey and Dimitrij did start on that in Ubuntu, patches > are available in Debian bug reports. > Currently the shared libraries are split out into separate packages, > and are co-installable. Not yet tested if this enough to run an > embedded interpreter. > > - Lua, Ocaml, Haskell, Guile, ... ? > > Matthias The support for this comes with Multiarch: allowed, which will only be allowed after wheezy. The interpreter declares itself Multiarch: allowed and then depending packages can specify wether they must match the abi (loadable binary plugins) or can work with any arch (binary packages that also contains some perl scripts). Co-installability of interpreters is generally not planed and would have to be made as custom solutions, i.e. place the interpreter in /usr/lib/x86_64-linux-gnu/perl/ and provide /usr/bin/perl as alternative. Also cross-building is not relevant for this issue. Normaly you would build it native (e.g. i386 chroot) and then install it on some other arch (amd64). But I think multiarch support for interpreters will be slow. There aren't many use cases so not a lot of pressure to implement it. Anyway, all of this has to wait till after wheezy. So get that out first. MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130418145645.GF21076@frosties
