From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: Bootstrap failed during compile of process.c
Date: Wed, 04 Jan 2006 20:27:25 +0200 [thread overview]
Message-ID: <usls3hmr6.fsf@gnu.org> (raw)
In-Reply-To: <43BC124E.2000106@student.lu.se> (message from Lennart Borgman on Wed, 04 Jan 2006 19:22:06 +0100)
> Date: Wed, 04 Jan 2006 19:22:06 +0100
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> CC: storm@cua.dk, emacs-devel@gnu.org
>
> I saw some pages saying that winsock2.h must be included before
> windows.h. Maybe that is the reason?
Maybe, I don't know. I will have to study the differences between
winsock.h and winsock2.h, and that will have to wait until I have
enough time, unless someone more knowledgeable beats me to it.
In any case, it's not for this release (there are much safer changes
than this that I'm holding until after the release, like using DWARF-2
debug info in compilation commands).
> This however reminds me of the problem with emacsserver/client that does
> not work yet on w32. In gnuserver/client (which works) windows2.h is
> used. Is there maybe some compatibility reason to use windows2.h?
Where can I find the up-to-date sources of gnuserver/client? Looking
there might help me understand the issue better (or sooner ;-).
next prev parent reply other threads:[~2006-01-04 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 6:58 Bootstrap failed during compile of process.c Lennart Borgman
2006-01-04 9:05 ` Kim F. Storm
2006-01-04 14:31 ` Lennart Borgman
2006-01-04 15:49 ` Kim F. Storm
2006-01-04 17:51 ` Lennart Borgman
2006-01-04 17:59 ` Eli Zaretskii
2006-01-04 17:56 ` Eli Zaretskii
2006-01-04 18:22 ` Lennart Borgman
2006-01-04 18:27 ` Eli Zaretskii [this message]
2006-01-04 18:50 ` Lennart Borgman
2006-01-04 19:59 ` Lennart Borgman
2006-01-04 18:43 ` Lennart Borgman
2006-01-05 16:02 ` Stefan Monnier
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=usls3hmr6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).