From: David Kastrup <dak@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
Subject: Re: Some error info from configure.bat please
Date: Sun, 03 Jul 2005 03:14:31 +0200 [thread overview]
Message-ID: <854qbcg07c.fsf@lola.goethe.zz> (raw)
In-Reply-To: <42C73742.3020605@student.lu.se> (Lennart Borgman's message of "Sun, 03 Jul 2005 02:54:26 +0200")
Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
> Juanma Barranquero wrote:
>
>>The problem is, I don't think that checking tools is a good strategy,
>>on the long term. Different versions sometimes work or cease to work.
>>I was able to build the Emacs info files with Cygwin for a while, and
>>after some update or other the thing failed. Me, I've assembled a .ZIP
>>with the tools needed (except MinGW, which I install separately), and
>>I unzip it wherever I want to compile Emacs. They are completely
>>separated of other installations of Unix tools that I may have on my
>>computer, and for sure I don't intend to change anything inside it
>>unless a future Emacs requires an upgrade (as Jason said, that
>>sometimes happens with make-info).
>>
>>
> Maybe different strategies are needed for different times. I have
> noticed the careful notes in INSTALL about certain parts of the
> tools. Perhaps that could be extended a bit. I see three different
> current tool packages on w32: GnuWin32, CygWin and MSYS+MinGW.
>From the vole itself: SFU
<URL:http:http://www.microsoft.com/windowsserversystem/sfu/>.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-07-03 1:14 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 [this message]
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
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=854qbcg07c.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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 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).