
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