--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: dh_ocaml cannot be used with arch:all packages
- From: Stéphane Glondu <steph@glondu.net>
- Date: Mon, 05 Oct 2009 16:20:31 +0200
- Message-id: <20091005142031.27359.58010.reportbug@aspirine.inria.fr>
Package: dh-ocaml
Version: 0.9.0
Severity: normal
This bug is a reminder for a known issue with dh_ocaml.
If dh_ocaml is used to compute dependencies of an arch:all package,
this package won't be installable on all architectures. This is
because the ABI of a library may be different on each architectures.
Currently, all *.cmi and *.cmx (if present) are taken into account to
compute a single ABI. A solution to the problem would be to compute
two distinct ABIs per (native) architecture: one for all *.cmi files
(which should be the same on all architectures... unless there is some
kind of conditional compilation), and one for all *.cmx files on
native architectures (this one might be different for each native
architecture, but it shouldn't be a problem).
--
Stéphane
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
dh-ocaml depends on no packages.
Versions of packages dh-ocaml recommends:
ii ocaml-nox 3.11.1-3 ML implementation with a class-bas
dh-ocaml suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 549679-done@bugs.debian.org
- Subject: Re: dh_ocaml cannot be used with arch:all packages
- From: Stéphane Glondu <glondu@debian.org>
- Date: Tue, 30 Jul 2019 13:36:42 +0200
- Message-id: <671fcb20-c0ee-3d05-4860-0e4d4823f9f8@debian.org>
tags 549679 + wontfix
thanks
No progress in more than 8 years on this bug...
IMHO (now), computing two ABIs looks fragile (because of the possibility
of conditional compilation producing arch-dependent bytecode).
Making packages arch:any looks easier and more sensible.
Hence, closing. Feel free to reopen if you have new arguments.
Cheers,
--
Stéphane
--- End Message ---