bug-libsigsegv
[Top][All Lists]
Advanced

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

Re: [bug-libsigsegv] new clisp/libffcall/libsigsegv for testing


From: Bruno Haible
Subject: Re: [bug-libsigsegv] new clisp/libffcall/libsigsegv for testing
Date: Tue, 18 Apr 2017 00:51:28 +0200
User-agent: KMail/5.1.3 (Linux/4.4.0-72-generic; KDE/5.18.0; x86_64; ; )

Hi Mojca,

You wrote in <http://tug.org/pipermail/tlbuild/2017q2/003774.html>
(and I couldn't reply earlier because I'm not subscribed to that list
and you didn't CC me):

> I optimistically tried to cross-compile on Mac OS X, but libffcall
> fails to detect the proper architecture and libsigsegv's "make check"
> fails. I'll try to see if I can trick the compiler to avoid having to
> go to a different machine with different architecture just for the
> sake of compiling clisp (the rest of TL works just fine this way).

None of clisp/libffcall/libsigsegv supports effortless cross-compilation
because:
  * libffcall and libsigsegv run behavioral tests at configure time
    (cf. AC_RUN_IFELSE), and we don't have a complete database of the
    outcome of these tests on the various platforms. (I have access to
    ca. 50 platforms - you can imagine the amount of work it would be
    to keep this database up to date.)
  * clisp creates memory images as part of its build process, and these
    memory images are highly platform dependent (on the memory word size
    in particular).

Bruno




reply via email to

[Prev in Thread] Current Thread [Next in Thread]