From: Harald Maier <harald@maierh.de>
Cc: help-emacs-windows@gnu.org, bug-gnu-emacs@gnu.org, jasonr@gnu.org
Subject: Re: [h-e-w] Current word on binaries
Date: Sat, 14 Feb 2004 18:24:08 +0100 [thread overview]
Message-ID: <m3vfm9y3pj.fsf@ate.maierh> (raw)
In-Reply-To: <2914-Sat14Feb2004185617+0200-eliz@elta.co.il> (Eli Zaretskii's message of "Sat, 14 Feb 2004 18:56:18 +0200")
"Eli Zaretskii" <eliz@elta.co.il> writes:
>> From: Harald Maier <harald@maierh.de>
>> Date: Sat, 14 Feb 2004 16:41:29 +0100
>>
>> Ok, I remember it again. Last year there was a patch about _fmode and
>> O_BINARY for gcc -mno-cygwin. See herefor the the messages in
>> emacs-devel with:
>>
>> ,----
>> | Subject: [david.ponce@wanadoo.fr: Re: Issues with Windows gcc -mno-cygwin
>> | (Mingw)]
>> `----
>
> Sorry, I'm confused: what does this have to do with the problem at
> hand? Did you verify that the crash is related to this patch?
Yes, I added the patch and all worked fine. emacs-21.3.tar.gz was made
before that change of gcc. If you want to build emacs with newer gccs
you need that fix, otherwise you will get the errors as discussed.
IIRC that patch was added to the RC branch.
> Why not simply patch the sources and be done with it?
If this is possible, I don't have a problem with that. My only problem
is that the current emacs-21.3.tar.gz _sources_ in a actual cygwin
environment are useless. You will always get discussions about the
problem. Are there any plans to distribute the RC branch. That would
fix the problem too.
Harald
next prev parent reply other threads:[~2004-02-14 17:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <009901c3ec70$b3013940$6400a8c0@austin.rr.com>
[not found] ` <m3broc4fdc.fsf@ate.maierh>
2004-02-14 9:33 ` [h-e-w] Current word on binaries Harald Maier
2004-02-14 11:57 ` Jason Rumney
2004-02-14 12:06 ` Eli Zaretskii
2004-02-14 12:18 ` [h-e-w] " Jason Rumney
2004-02-16 19:52 ` Richard Stallman
2004-02-16 20:38 ` Jason Rumney
2004-02-17 6:50 ` [h-e-w] " Eli Zaretskii
2004-02-17 8:56 ` Jason Rumney
2004-02-17 19:03 ` Eli Zaretskii
2004-02-18 0:13 ` Jason Rumney
2004-02-18 6:11 ` Eli Zaretskii
2004-02-18 8:38 ` Richard Stallman
2004-02-18 10:39 ` [h-e-w] " Eli Zaretskii
2004-02-18 12:30 ` Harald Maier
2004-02-18 13:37 ` [h-e-w] " Jason Rumney
2004-02-18 14:28 ` Eli Zaretskii
2004-02-18 23:29 ` Jason Rumney
2004-02-18 13:43 ` Jason Rumney
2004-02-18 18:54 ` [h-e-w] " Eli Zaretskii
2004-02-14 13:18 ` Harald Maier
2004-02-14 13:37 ` Jason Rumney
2004-02-14 15:41 ` Harald Maier
2004-02-14 16:56 ` [h-e-w] " Eli Zaretskii
2004-02-14 17:24 ` Harald Maier [this message]
2004-02-14 17:49 ` Eli Zaretskii
2004-02-14 19:26 ` Harald Maier
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=m3vfm9y3pj.fsf@ate.maierh \
--to=harald@maierh.de \
--cc=bug-gnu-emacs@gnu.org \
--cc=help-emacs-windows@gnu.org \
--cc=jasonr@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).