On Wed, Jul 02, 2008 at 04:43:54PM +0200, Luca Capello wrote:

...

...

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 I cannot reproduce it on i386 nor on amd64, so this should be s390 specific.

I think I had such a problem lately but I'm not able to find the corresponding bug.

...

...

See `config.log' for more details. Is config.log available somewhere?

| configure:5183: checking how to run the C preprocessor | configure:5299: result: gcc -E | configure:5328: gcc -E conftest.c | In file included from /usr/include/features.h:354, | from /usr/include/limits.h:27, | from /usr/lib/gcc/s390-linux-gnu/4.3.1/include-fixed/limits.h:122, | from /usr/lib/gcc/s390-linux-gnu/4.3.1/include-fixed/syslimits.h:7, | from /usr/lib/gcc/s390-linux-gnu/4.3.1/include-fixed/limits.h:11, | from conftest.c:14: | /usr/include/gnu/stubs.h:9:27: error: gnu/stubs-64.h: No such file or directory | configure:5334: $? = 1 | configure: failed program was: | | /* confdefs.h. */ | | #define PACKAGE_NAME "GNU CLISP" | | #define PACKAGE_TARNAME "clisp" | | #define PACKAGE_VERSION "2.44.1 (2008-02-23)" | | #define PACKAGE_STRING "GNU CLISP 2.44.1 (2008-02-23)" | | #define PACKAGE_BUGREPORT "http://clisp.cons.org/" | | #define PACKAGE "clisp" | | #define VERSION "2.44.1 (2008-02-23)" | | #ifndef __s390x__ | | #define __s390x__ 1 | | #endif | | /* end confdefs.h. */ | | #ifdef __STDC__ | | # include <limits.h> | | #else | | # include <assert.h> | | #endif | | Syntax error The configure call lacks a --build=$(DEB_BUILD_GNU_TYPE) argument.

I'll ask for access to raptor.d.o and try to investigate the failure, but I'm not a gcc expert and frankly speaking I don't have a lot of time (other Common Lisp bugs come before).

Hmm. The Debian Lisp team don't have a DD? Bastian -- Violence in reality is quite different from theory. -- Spock, "The Cloud Minders", stardate 5818.4

tags 488817 + patch thanks Hi Bastian! 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 :-( If I add "--build=$(DEB_BUILD_GNU_TYPE)" to ./configure: ===== ./configure debian/build --prefix=/usr --fsstnd=debian --with-dynamic-ffi --with-dynamic-modules \ --with-module=bindings/glibc --with-module=clx/new-clx --with-module=berkeley-db --build=x86_64-linux-gnu ./configure: invalid argument --build=x86_64-linux-gnu ./configure: Try `./configure --help' make: *** [configure-stamp] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 ===== And if I add "--build $(DEB_BUILD_GNU_TYPE)" to ./configure: ===== dh_testdir ./configure debian/build --prefix=/usr --fsstnd=debian --with-dynamic-ffi --with-dynamic-modules \ --with-module=bindings/glibc --with-module=clx/new-clx --with-module=berkeley-db --build x86_64-linux-gnu [...] configure: ** check for host type checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for style of include used by make... GNU checking for gcc... x86_64-linux-gnu checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. make: *** [configure-stamp] Error 77 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 ===== I guess this is because: ===== sh-3.2# ./configure --help Usage: configure [options] [dirname] [...] --build unix/INSTALL steps 3-8: configure, build, check [...] Specifying the C compiler: If you wish to specify the C compiler that will get used to build CLISP, set the environment variables CC, CFLAGS, LIBS. Put compiler flags that have to be passed to the preprocessor into the CC variable, not the CFLAGS variable. For example, if you want to use gcc in ANSI C mode, execute the following before calling `configure': setenv CC "gcc -ansi" if using csh export CC="gcc -ansi" if using bash or ksh CC="gcc -ansi"; export CC if using sh ===== 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'll try the patch above on raptor.d.o and commit it if ./configure will continue. Let's see if there are other errors then ;-) Thx, bye, Gismo / Luca

tags 488817 + upstream forwarded 488817 http://thread.gmane.org/gmane.lisp.clisp.devel/18516 thanks Hi Bastian! 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

On Tue, Jul 08, 2008 at 01:14:03AM +0200, Luca Capello wrote:

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].

This is weird. src/configure is generated from autoconf and for sure support --build and --host. | $ ./configure --build=powerpc-linux-gnu --host=s390-linux-gnu | [...] | checking build system type... powerpc-unknown-linux-gnu | checking host system type... s390-ibm-linux-gnu Bastian -- The more complex the mind, the greater the need for the simplicity of play. -- Kirk, "Shore Leave", stardate 3025.8