Re: Compilation problems on s390 (was Re: Cross-compilation on Debian: various errors)

[Sam S. <sd...@gn...>]

Hi,

Luca Capello wrote:
> If you prefer we can move to the SF BTS, but I still prefer mails.

I prefer sf bts for specific items which can be usefully referenced 
later and mail for general discussions.

> On Tue, 08 Jul 2008 22:35:37 +0200, Sam Steingold wrote:
>> Luca Capello wrote:
>>> I'm part of the Debian Common Lisp Team [1] and I'm trying to solve the
>>> Debian bug #488817 [2]: basically, clisp-2.44.1 fails to build on s390.
>> is this a native build or a cross-compilation?
> 
> It's a native build, should I file a bug in the SF BTS?
> 
> Let me explain the situation, since I understand that the subject of my
> first mail wasn't completely precise and I still need to understand how
> --build and --host influence the build process.

try with and without --build & --host and diff the configure logs and 
generated Makefiles

> The other option would be to (temporarily) disable Debian support for
> s390 and then enable it again as soon as the compilation problems will
> have been solved.  The same can be applied to arm, since 2.44.1 seems to
> fail to build there, too [7][8].
> 
> [7] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490944
> [8] https://sourceforge.net/tracker/index.php?func=detail&aid=2018687&group_id=1355&atid=101355

fixed in 2.45

>> 1. build the run time (lisp.run). this is done by compiling and
>> linking C files and can be done on the host machine using the usual
>> cross-compilation tools.
>>
>> 2. build the lisp memory image (lispinit.mem). this is done by running
>> the run time (lisp.run) and loading lisp files into it &c. this has to
>> be done on the target machine on which the eventual clisp will
>> run. you *cannot* create a lisp image on a different machine, see
>> bottom of http://clisp.cons.org/impnotes/image.html
> 
> Actually, the Debian CLISP ships a lispinit-orig.mem image which is then
> modified into the final one at installation time (thus on the real
> target machine) [8].
> 
> [8] http://git.debian.org/?p=pkg-common-lisp/clisp.git;a=blob;f=debian/clisp.sh;h=bd36b2a98daeaf429deb059dcc67c5e862824b9b;hb=HEAD

this merely adds common-lisp-controller to an existing image.
this image was built on a target machine too.

>> 3. build modules. this often involves pre-processing C files with
>> clisp (on either host or target) and compiling the C files (on host),
>> and often compiling lisp files (on target).
> 
> AFAIK all the modules are compiled at Debian package built time and host
> and target are always the same architecture.

this simplifies things a lot.
note that the word "module" in this context refers to the 
clisp/modules/* directories.

Good luck.
Sam.