From: Andy Wingo <wingo@pobox.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: taylanbayirli@gmail.com, guile-user@gnu.org, joakim@verona.se,
bt@hcoop.net, emacs-devel@gnu.org
Subject: Re: Guile-Emacs update
Date: Sat, 07 Sep 2013 13:14:36 +0200 [thread overview]
Message-ID: <87a9jox4rn.fsf@pobox.com> (raw)
In-Reply-To: <83d2olkkzw.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Sep 2013 13:02:27 +0300")
On Sat 07 Sep 2013 12:02, Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andy Wingo <wingo@pobox.com>
>> Date: Sat, 07 Sep 2013 11:29:10 +0200
>> Cc: guile-user@gnu.org, BT Templeton <bt@hcoop.net>, joakim@verona.se,
>> emacs-devel@gnu.org
>>
>> On Thu 01 Aug 2013 00:17, taylanbayirli@gmail.com (Taylan Ulrich B.) writes:
>>
>> > the "dumping" feature of Emacs is disabled
>>
>> Eventually Guile will support linking together multiple separately
>> compiled files into one ELF image. (The object file format in the
>> development Guile branch is ELF -- we have our own linker and loader, so
>> we currently plan on using this format even on non-ELF platforms.)
>
> Was this ever tested on any non-ELF platform, such as MinGW?
It just landed a couple months ago, so the time for that hasn't really
come yet. But it doesn't rely on any interfaces of the platform, so I
don't anticipate problems.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-09-07 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 23:54 Guile-Emacs update BT Templeton
2013-07-21 1:32 ` Noah Lavine
2013-07-22 7:52 ` Taylan Ulrich B.
2013-07-24 21:50 ` BT Templeton
2013-07-31 18:54 ` joakim
2013-07-31 20:28 ` Paul Smith
2013-07-31 20:46 ` joakim
2013-07-31 22:17 ` Óscar Fuentes
2013-07-31 22:17 ` Taylan Ulrich B.
2013-09-07 9:29 ` Andy Wingo
2013-09-07 10:02 ` Eli Zaretskii
2013-09-07 11:14 ` Andy Wingo [this message]
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=87a9jox4rn.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bt@hcoop.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=joakim@verona.se \
--cc=taylanbayirli@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.