From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: ffcall
Date: Mon, 23 Feb 2015 20:56:00 -0000 [thread overview]
Message-ID: <87egpgwdn6.fsf@Rainer.invalid> (raw)
In-Reply-To: <20150223203253.GZ437@calimero.vinschen.de> (Corinna Vinschen's message of "Mon, 23 Feb 2015 21:32:53 +0100")
Corinna Vinschen writes:
> Own malloc and own GC? WHat if it misses the fact that the C library
> (aka Cygwin) uses malloc, too?
I didn't really follow through after that fail. I did successfully
compile ecl and it seems to work with maxima, but ecl doesn't produce
executables. But really, what's the matter with those Lisp folks and
their wierd build systems? (don't answer, rhetorical question)
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2015-02-23 20:56 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 ` Achim Gratz [this message]
2015-02-21 3:45 ` ffcall Ken Brown
2015-02-21 12:59 ` ffcall Reini Urban
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=87egpgwdn6.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).