From: Reini Urban <rurban@x-ray.at>
To: cygwin-apps@cygwin.com
Subject: Re: ffcall
Date: Sat, 21 Feb 2015 12:59:00 -0000 [thread overview]
Message-ID: <54E8812D.9050601@x-ray.at> (raw)
In-Reply-To: <54E7FF3A.30609@cornell.edu>
On 02/21/2015 04:44 AM, Ken Brown wrote:
> On 2/19/2015 2:46 PM, Reini Urban wrote:
>> And the deal with the latest clisp 2.49 was that modules can be
>> dynaloaded.
>> If the gnulib steps would work. I never did for me. And I fixed most of
>> the other
>> module compilation problems before.
>
> But I just discovered that clisp-2.49 builds fine with the configure
> option --without-dynamic-modules. Is there any reason not to do
> that? After all, clisp-2.48 is built without dynamic modules, so
> what's the harm in doing the same for 2.49?
Technically this is the best.
But I never published 2.49 with this option, because there were not many
other changes.
So it's almost the same as 2.48 and my version was not as confusing.
next prev parent reply other threads:[~2015-02-21 12:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 18:49 ffcall Ken Brown
2015-02-18 19:28 ` ffcall Yaakov Selkowitz
2015-02-18 20:08 ` ffcall Corinna Vinschen
2015-02-18 22:41 ` ffcall Ken Brown
2015-02-19 9:38 ` ffcall Corinna Vinschen
2015-02-19 15:43 ` ffcall Reini Urban
2015-02-19 16:45 ` ffcall Ken Brown
2015-02-19 17:18 ` ffcall Ken Brown
2015-02-19 17:44 ` ffcall Corinna Vinschen
2015-02-19 18:47 ` ffcall Ken Brown
2015-02-19 19:46 ` ffcall Reini Urban
2015-02-19 22:30 ` ffcall Ken Brown
2015-02-21 10:03 ` ffcall David Billinghurst
2015-02-21 17:16 ` ffcall Ken Brown
2015-02-21 20:43 ` ffcall Achim Gratz
2015-02-21 21:04 ` ffcall Achim Gratz
2015-02-23 11:38 ` ffcall Corinna Vinschen
2015-02-23 17:48 ` ffcall Achim Gratz
2015-02-23 20:32 ` ffcall Corinna Vinschen
2015-02-23 20:56 ` ffcall Achim Gratz
2015-02-21 3:45 ` ffcall Ken Brown
2015-02-21 12:59 ` Reini Urban [this message]
2015-02-21 17:20 ` ffcall Ken Brown
2015-02-18 22:17 ` ffcall Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E8812D.9050601@x-ray.at \
--to=rurban@x-ray.at \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).