Bug#951052: marked as done (FTBFS with menhir 20200123)
Your message dated Mon, 10 Feb 2020 15:22:28 +0000
with message-id <E1j1AtI-0009TH-R7@fasolo.debian.org>
and subject line Bug#951052: fixed in why3 1.2.1-3
has caused the Debian Bug report #951052,
regarding FTBFS with menhir 20200123
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
951052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951052
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:why3
Version: 1.2.1-2
Severity: grave
Tags: ftbfs
Dear Maintainer,
why3 FTBFS with menhir 20200123:
https://buildd.debian.org/status/package.php?p=why3&suite=sid
Log:
> [...]
> Linking bin/why3.opt
> x86_64-linux-gnu-gcc: error: /usr/lib/ocaml/menhirLib/menhirLib.o: No such file or directory
> File "caml_startup", line 1:
> Error: Error during linking
> make[1]: *** [Makefile:2234: bin/why3.opt] Error 2
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> make: *** [debian/rules:18: build-arch] Error 2
I suspect the build system is trying to link with menhirLib.cmx instead of menhirLib.cmxa.
Cheers,
--
Stéphane
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: why3
Source-Version: 1.2.1-3
We believe that the bug you reported is fixed in the latest version of
why3, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 951052@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stéphane Glondu <glondu@debian.org> (supplier of updated why3 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 10 Feb 2020 13:57:51 +0100
Source: why3
Architecture: source
Version: 1.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
Changed-By: Stéphane Glondu <glondu@debian.org>
Closes: 951052
Changes:
why3 (1.2.1-3) unstable; urgency=medium
.
[ Stéphane Glondu ]
* Team upload
* Fix FTBFS with menhir 20200123 (Closes: #951052)
.
[ Ralf Treinen ]
* drop cvc3 from Recommends and debian/tests as the cvc3 package has
been removed from sid.
Checksums-Sha1:
470482c12b42f501cc4a5cfc90f2db68e132a34f 2421 why3_1.2.1-3.dsc
3d7c0b015259d0d9bf24c30383d047b009aaf617 17532 why3_1.2.1-3.debian.tar.xz
Checksums-Sha256:
080279720fb443a6c2a2876ac9ca07c9fb8f02b7df3e410ecaa50ced239df028 2421 why3_1.2.1-3.dsc
f8d110d0a40268603b40b5b821d581a7ec4d1a785a2e1c4acb02c62d8c84c73f 17532 why3_1.2.1-3.debian.tar.xz
Files:
8d2bfee975caa3b77008005c7491c11c 2421 math optional why3_1.2.1-3.dsc
85b5a88636a82f116eb6587ba75d8418 17532 math optional why3_1.2.1-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl5BcGEACgkQIbju8bGJ
MIEEwwf+NPSHj62E6HuErGZkfSc4y7Wv69uA9S0uFa7HmNBVulZXFrzK/3xTM8Qh
gHWxCh0WObuSI6ffrPifuE0i6l9kg2F251VBd2v/GXlStPeCoDUHJdHDuNVbyatR
scCseii2cNwidU/faZVYVSxOyXukKznVWgMCTr8sIK1Iu2QEk+THLEfsQiZ2VZIG
aveivu0Eirzn+R8+XpsgzdwyjwmbAB3EkjKWaZTz250T8vNi9EdH5S4vPJSB3bTU
U9HyTc1FhhvWxjCY0cPW9FTd7c0y1jUM/wMDyUwLTpVKUHRb/sZSz31K24mpz7cW
4g42Dy3yvL//kqdwp55XZI+EapDfEg==
=9OJF
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: