From: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Some error info from configure.bat please
Date: Sun, 3 Jul 2005 03:21:28 +0200 [thread overview]
Message-ID: <f7ccd24b05070218211af94862@mail.gmail.com> (raw)
In-Reply-To: <42C73742.3020605@student.lu.se>
On 7/3/05, Lennart Borgman <lennart.borgman.073@student.lu.se> wrote:
> Maybe different strategies are needed for different times.
Perhaps. But when I started compiling my own Emacs I would've been
glad to have a list: "get texinfo from http://here, and make.xe from
http://there, oh, and rm and other common tools from
http://over/there." Adding to the problem is that, if the user
overlooks the "cvs update -kb" bit of information, he's gonna think
his make.exe doesn't work and he's gonna start losing hair really
fast... (Been there, done that, lost the patience.)
> Perhaps that could be extended a bit. I see three different current tool
> packages on w32: GnuWin32, CygWin and MSYS+MinGW.
Yes, although Cygwin is more for those that want a total Unix
immersion environment in Windows; I wouldn't recommend it for a user
that just wants to compile Emacs (building in Cygwin is more like
building on GNU/Linux than in Windows).
> I am not sure about
> UnxUtilites, are they maintained?
I think there's only one developer and the last update is from 2003;
still, the simple tools (like rm, cp) work for me much better than the
ones in MSYS, for example (I had weird network issues with these).
> Staying with one of those for a
> particular purposes may be the best.
>
> In my case I have decided to go with GnuWin32+MinGW when building Emacs.
That is two ;-)
> Currently I have
> MSYS installed, but it is not on my path (except for sometimes inside
> Emacs).
I do the opposite: I have MSYS and MinGW on my path, but I take them
out for building and running Emacs (but I never use shell buffers
inside Emacs).
--
/L/e/k/t/u
next prev parent reply other threads:[~2005-07-03 1:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 9:32 Some error info from configure.bat please Lennart Borgman
2005-07-02 13:22 ` Eli Zaretskii
2005-07-02 12:32 ` Lennart Borgman
2005-07-02 16:53 ` Eli Zaretskii
2005-07-02 16:01 ` Lennart Borgman
2005-07-02 16:34 ` Juanma Barranquero
2005-07-02 17:36 ` Eli Zaretskii
2005-07-02 20:24 ` Jason Rumney
2005-07-02 21:16 ` Juanma Barranquero
2005-07-02 21:37 ` Jason Rumney
2005-07-02 21:45 ` Lennart Borgman
2005-07-02 22:20 ` Jason Rumney
2005-07-03 6:19 ` Eli Zaretskii
2005-07-02 21:37 ` Lennart Borgman
2005-07-03 0:22 ` Juanma Barranquero
2005-07-03 0:54 ` Lennart Borgman
2005-07-03 1:14 ` David Kastrup
2005-07-03 1:40 ` Juanma Barranquero
2005-07-03 8:19 ` David Kastrup
2005-07-03 10:42 ` Juanma Barranquero
2005-07-03 1:21 ` Juanma Barranquero [this message]
2005-07-03 6:30 ` Eli Zaretskii
2005-07-03 7:29 ` Lennart Borgman
2005-07-03 16:02 ` Eli Zaretskii
2005-07-03 7:50 ` Lennart Borgman
2005-07-03 16:11 ` Eli Zaretskii
2005-07-03 16:27 ` Juanma Barranquero
2005-07-03 18:58 ` Eli Zaretskii
2005-07-03 18:17 ` Juanma Barranquero
2005-07-04 14:54 ` Stefan Monnier
2005-07-04 15:17 ` Andreas Schwab
2005-07-04 18:07 ` Stefan Monnier
2005-07-04 18:45 ` Lennart Borgman
2005-07-16 12:39 ` Eli Zaretskii
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=f7ccd24b05070218211af94862@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@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).