[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#909125: marked as done (ffcall FTCBFS: wrong use of AC_TRY_RUN)

Your message dated Wed, 28 Aug 2019 20:59:57 +0000
with message-id <E1i352r-0006F3-M6@fasolo.debian.org>
and subject line Bug#909125: fixed in ffcall 2.2-1
has caused the Debian Bug report #909125,
regarding ffcall FTCBFS: wrong use of AC_TRY_RUN
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

909125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909125
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: ffcall
Version: 2.1-2
Tags: patch upstream
User: helmutg@debian.org
Usertags: rebootstrap

ffcall fails to cross build from source, because there are three cases
where AC_TRY_RUN is used wrongly. The arguments for AC_TRY_RUN are:
1. program source
2. success code
3. failure code
4. cross compile code

In three cases, the third argument was skipped. That is evident from the
comments in the actual third argument hinting that the argument was
intended for cross compilation but actually got used for the failure
case. Inserting the missing failure case makes ffcall cross buildable.

Please consider applying the attached patch.

--- ffcall-2.1.orig/m4/codeexec.m4
+++ ffcall-2.1/m4/codeexec.m4
@@ -177,6 +177,7 @@
+                 [ffcall_cv_malloc_mprotect_can_exec=no],
                  [dnl When cross-compiling, assume SELinux on Linux.
                   dnl If we don't know, assume the worst.
                   case "$host_os" in
@@ -267,6 +268,7 @@
+                     [ffcall_cv_mmap_mprotect_can_exec=no],
                      [dnl When cross-compiling, assume SELinux on Linux.
                       dnl If we don't know, assume the worst.
                       case "$host_os" in
@@ -339,6 +341,7 @@
+                       [ffcall_cv_mmap_shared_can_exec=no],
                        [dnl When cross-compiling, assume yes, since this is the result
                         dnl on all the platforms where we have tested it.
                         ffcall_cv_mmap_shared_can_exec="guessing yes"

--- End Message ---
--- Begin Message ---
Source: ffcall
Source-Version: 2.2-1

We believe that the bug you reported is fixed in the latest version of
ffcall, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 909125@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Sébastien Villemot <sebastien@debian.org> (supplier of updated ffcall 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)

Hash: SHA512

Format: 1.8
Date: Wed, 28 Aug 2019 21:39:51 +0200
Source: ffcall
Architecture: source
Version: 2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team <debian-common-lisp@lists.debian.org>
Changed-By: Sébastien Villemot <sebastien@debian.org>
Closes: 457930 883043 909125 925129
 ffcall (2.2-1) unstable; urgency=medium
   * New upstream release
     + fixes hppa support (Closes: #457930, #883043)
   * Drop mips-fpxx.patch, no longer needed
   * mips-r6.patch: refresh patch, and incorporate fix for jaql instruction.
     Thanks to Luyou Peng (Closes: #925129)
   * cross.patch: new patch, fixes FTCBFS. Thanks to Helmut Grohne
     (Closes: #909125)
   * d/copyright: reflect upstream changes
   * Add Build-Depends-Package field in symbols files
   * Add Rules-Requires-Root: no
   * Bump S-V to 4.4.0
   * Bump to debhelper compat level 12
   * Re-export upstream signing key without extra signatures.
   * Set upstream metadata fields: Bug-Submit.
 78872c33fe1d76508fd25634ac5745e678d940e7 2440 ffcall_2.2-1.dsc
 464f1af197d417366face3007d7b63848b8fd6f4 954623 ffcall_2.2.orig.tar.gz
 08b700fe187bc27514a2911a7b0b620bf6139dfa 819 ffcall_2.2.orig.tar.gz.asc
 a9190faf63c18cf6e4206310c8e7f4589994042e 548156 ffcall_2.2-1.debian.tar.xz
 709294602b6099f8fa29396ad3b13cc228f2f666 7855 ffcall_2.2-1_amd64.buildinfo
 a16ab48934d90f23c4efc0eb9ba033fdbedf898414e51172a5a1027f7df06548 2440 ffcall_2.2-1.dsc
 ebfa37f97b6c94fac24ecf3193f9fc829517cf81aee9ac2d191af993d73cb747 954623 ffcall_2.2.orig.tar.gz
 2d93b17726d832e50acda0b2a03c6e5277579ff2c4644b61179edee6364e3ae6 819 ffcall_2.2.orig.tar.gz.asc
 685b9b67171675f3cf9bd667bb276c88ed97c755b221ed05fea19c18fc424746 548156 ffcall_2.2-1.debian.tar.xz
 ab62bd9a8d9573d69905379fd770c73a37dc077f350eed19068173f6f6d90f63 7855 ffcall_2.2-1_amd64.buildinfo
 ae40e6081a7a84b9bfa08883f74db95d 2440 libs optional ffcall_2.2-1.dsc
 d4c7bf840673ec30c1f3b3edab98a7c6 954623 libs optional ffcall_2.2.orig.tar.gz
 21dbbcf7978b616778914f5917f06465 819 libs optional ffcall_2.2.orig.tar.gz.asc
 f92105d1595ede45faa7e1e178badeb6 548156 libs optional ffcall_2.2-1.debian.tar.xz
 f8def559bffef6ef4433e234719effd2 7855 libs optional ffcall_2.2-1_amd64.buildinfo



--- End Message ---

Reply to: