From: Greg Troxel <gdt@ir.bbn.com>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: Guile User List <guile-user@gnu.org>,
Guile Development <guile-devel@gnu.org>
Subject: Re: Reconsideration of MinGW work
Date: Mon, 22 Mar 2010 19:38:05 -0400 [thread overview]
Message-ID: <rmiy6hkkjvm.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <11640D11-A8D6-4C58-86FA-EF79F4D60770@raeburn.org> (Ken Raeburn's message of "Sun, 21 Mar 2010 21:28:18 -0400")
[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]
Ken Raeburn <raeburn@raeburn.org> writes:
> One nagging concern I've got about my Guile-Emacs project is the
> seemingly narrow focus of active Guile developers as far as platforms
> are concerned. I'm one of, what, two or three people testing the
> development versions on Mac OS X now and then, and most of the rest of
> the work is on x86 or x86-64 GNU/Linux systems, it seems? But Emacs
> works on a lot more systems (including MinGW, for people who don't
> want all of Cygwin), and saying "hey, we can change Emacs to be
> Guile-based on x86 GNU/Linux systems; too bad about all the other
> platforms" wouldn't go over terribly well.
I test on NetBSD, and in theory care about not only i386 and amd64 but
also sparc64. But I have not had a lot of spare time lately to hack on
guile. I am running autobuilds on list.ir.bbn.com (NetBSD amd64):
http://autobuild.josefsson.org/guile/
and it looked like some non-portable assumptions have crept in:
http://autobuild.josefsson.org/guile/log-201003220603936147000.txt
> For a random Scheme implementation, it's okay to pick the set of
> platforms you want to support, and drop whatever's inconvenient. But
> if you want to be the official extension language for the GNU project,
> used by (theoretically) lots of GNU packages, you've got to support
> all the platforms the developers of those platforms want to support,
> if you possibly can. I think that includes both Cygwin and MinGW, and
> probably not just supporting whatever subset can be mapped into POSIX
> functions via Gnulib. We can probably punt on VMS, though....
The target set definitely ought to include cygwin, but the GNU project
has a bias for Free and/or POSIX operating systems so I am willing to
forgo getting upset about lack of mingw support. But surely we should
be happy if someone provides it.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2010-03-22 23:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 20:51 Reconsideration of MinGW work Neil Jerram
2010-03-21 21:36 ` Grant Rettke
2010-03-22 1:28 ` Ken Raeburn
2010-03-22 20:10 ` Andy Wingo
2010-03-22 23:38 ` Greg Troxel [this message]
2010-03-23 0:04 ` Neil Jerram
2010-03-23 6:59 ` Ken Raeburn
2010-03-23 8:50 ` Andy Wingo
2010-03-28 22:32 ` guile on lemote (was Re: Reconsideration of MinGW work) Ken Raeburn
2010-03-29 21:37 ` guile on lemote Neil Jerram
2010-03-22 8:10 ` Reconsideration of MinGW work Peter Brett
2010-03-22 20:00 ` Andy Wingo
2010-03-22 20:05 ` Linas Vepstas
2010-03-23 0:20 ` Neil Jerram
2010-03-23 0:13 ` Neil Jerram
2010-03-28 22:26 ` Ludovic Courtès
2010-03-29 20:34 ` Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2010-03-21 22:45 carlo.bramix
2010-03-23 0:35 ` Reconsideration " Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rmiy6hkkjvm.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=raeburn@raeburn.org \
/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).