Your message dated Fri, 22 Sep 2017 10:18:47 +0200
with message-id <1506068327.12056.22.ca...@debian.org>
and subject line Re: Bug#488817: clisp - FTBFS: configure: error: C
preprocessor "gcc -E" fails sanity check
has caused the Debian Bug report #491573,
regarding clisp: please support --build ./configure option
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 ow...@bugs.debian.org
immediately.)
--
491573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clisp
Version: 1:2.44.1-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of clisp_1:2.44.1-1 on lxdebian.bfinv.de by sbuild/s390 98
[...]
> checking dependency style of gcc... (cached) gcc3
> checking how to run the C preprocessor... gcc -E
> configure: error: C preprocessor "gcc -E" fails sanity check
> See `config.log' for more details.
> make: *** [configure-stamp] Error 1
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
> ******************************************************************************
> Build finished at 20080701-1451
> FAILED [dpkg-buildpackage died]
--- End Message ---
--- Begin Message ---
Version: 1:2.48-1
On Tue, 08 Jul 2008 01:14:03 +0200 Luca Capello <l...@pca.it> wrote:
> On Wed, 02 Jul 2008 21:39:28 +0200, Luca Capello wrote:
> > On Wed, 02 Jul 2008 17:23:47 +0200, Luca Capello wrote:
> >> On Wed, 02 Jul 2008 17:17:38 +0200, Bastian Blank wrote:
> >>> The configure call lacks a --build=$(DEB_BUILD_GNU_TYPE) argument.
> >>
> >> Thank you for the hint, I'll test on raptor.d.o if this is the only
> >> thing needed.
> >
> > This doesn't seem to work, at least on amd64 :-(
> [...]
> > Indeed, if I simply use "export CC=$(DEB_BUILD_GNU_TYPE)-gcc" the
> > package is built and checked by debdiff shows no difference with the
> > package built without the export. However, since I'm not a GCC expert,
> > I'm not sure this is the preferred way.
>
> I investigated a bit more and actually the problem relies on CLISP's
> configure: upstream added the support for autoconf --build in version
> 2.45 [1]. So the ideal fix was to backport the upstream one, not only
> for configure but various files [2].
>
> However, this seems to be more pain than expected and it's IMHO an
> upstream bug: tagged as this and forwarded at [3].
>
> Thx, bye,
> Gismo / Luca
>
> Footnotes:
> [1]
> http://clisp.cvs.sourceforge.net/clisp/clisp/configure?revision=1.121&view=markup
> [2] other than the necessary files, I corrected the documentation, too:
> =====
> luca@gismo:~/test-clisp/clisp$ quilt push
> Applying patch 01_standard-autoconf-options-build-host.patch
> patching file configure
> patching file unix/INSTALL
> patching file clisp.spec
> patching file doc/clisp.xml.in
> patching file doc/_clisp.1
> patching file doc/_clisp.html
> patching file src/makemake.in
>
> Now at patch 01_standard-autoconf-options-build-host.patch
> luca@gismo:~/test-clisp/clisp$
> =====
> [3] http://thread.gmane.org/gmane.lisp.clisp.devel/18516
Closing, since the --build option has been added in upstream version 2.45.
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
signature.asc
Description: This is a digitally signed message part
--- End Message ---
