From: Eli Zaretskii <eliz@gnu.org>
To: Sam Steingold <sds@gnu.org>
Cc: jan.h.d@swipnet.se, emacs-devel@gnu.org
Subject: Re: cannot build on w32
Date: Thu, 20 Jan 2011 10:27:51 -0500 [thread overview]
Message-ID: <E1PfwQR-0006of-3y@fencepost.gnu.org> (raw)
In-Reply-To: <AANLkTimH4PJ7bjQpitgpLwnOBmXXoVnSMZW1evhsCTpE@mail.gmail.com> (message from Sam Steingold on Thu, 20 Jan 2011 10:17:55 -0500)
> Date: Thu, 20 Jan 2011 10:17:55 -0500
> From: Sam Steingold <sds@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>
> > OSX uses autoconf and doesn't build right now...
>
> it's not enough to have a magic bullet - you also have to know how to use it :-)
> (in this particular case - switching to gnulib is a non-trivial step,
> so some breakage is nigh inevitable).
Exactly my point: with such a non-trivial step, the fact that the w32
build is broken does not mean we should conclude that the Windows port
cannot be reasonably maintained without using autoconf.
next prev parent reply other threads:[~2011-01-20 15:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 15:12 cannot build on w32 Sam Steingold
2011-01-19 15:18 ` Tom Tromey
2011-01-19 15:33 ` Sam Steingold
2011-01-19 15:53 ` Sam Steingold
2011-01-19 16:03 ` Eli Zaretskii
2011-01-19 16:14 ` Sam Steingold
2011-01-19 16:32 ` Eli Zaretskii
2011-01-19 16:05 ` Sam Steingold
2011-01-19 16:09 ` Eli Zaretskii
2011-01-19 16:16 ` Sam Steingold
2011-01-19 16:39 ` Eli Zaretskii
2011-01-19 17:36 ` Sam Steingold
2011-01-19 19:01 ` Jan Djärv
2011-01-20 15:17 ` Sam Steingold
2011-01-20 15:27 ` Eli Zaretskii [this message]
2011-01-20 18:46 ` Sam Steingold
2011-01-20 14:12 ` Richard Stallman
2011-01-20 14:50 ` Sam Steingold
2011-01-20 15:00 ` Eli Zaretskii
2011-01-21 20:15 ` Richard Stallman
2011-01-19 16:21 ` Óscar Fuentes
2011-01-19 16:41 ` Eli Zaretskii
2011-01-19 16:52 ` Óscar Fuentes
2011-01-19 15:36 ` Andreas Schwab
2011-01-19 15:40 ` Tom Tromey
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1PfwQR-0006of-3y@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=sds@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).