From: Ken Brown <kbrown@cornell.edu>
To: Dan Nicolaescu <dann@gnu.org>
Cc: "6715@debbugs.gnu.org" <6715@debbugs.gnu.org>
Subject: bug#6715: 24.0.50; [PATCH] Cygwin build should use pre-crt0.c
Date: Sun, 25 Jul 2010 10:38:10 -0400 [thread overview]
Message-ID: <4C4C4C52.9050801@cornell.edu> (raw)
In-Reply-To: <yxqfwz85ztu.fsf@fencepost.gnu.org>
On 7/24/2010 5:34 PM, Dan Nicolaescu wrote:
> Here's some other cygwin related cleanups:
>
> - remove this:
>
> #ifdef CYGWIN
> #define BSD4_2
> #endif
>
> and instead add defined(CYGWIN) in the right place in the only user: vm-limit.c
Done.
>
> - in configure.in the setting for lastfile.o
> cygwin is the only platform that uses different linking order.
> If the "normal" linking order works on cygwin too, it would simplify the build a bit.
No, the "normal" linking order doesn't work on cygwin;
bootstrap-emacs.exe gets built, but it hangs when trying to byte compile
the .el files. What about turning the question around? Would the
linking order that works on cygwin also work on other platforms? Or is
it safer to just leave this alone?
Ken
next prev parent reply other threads:[~2010-07-25 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 22:44 bug#6715: 24.0.50; [PATCH] Cygwin build should use pre-crt0.c Ken Brown
2010-07-24 1:23 ` Chong Yidong
2010-07-24 5:13 ` Dan Nicolaescu
2010-07-24 12:22 ` Ken Brown
2010-07-24 18:48 ` Ken Brown
2010-07-24 20:26 ` Eli Zaretskii
2010-07-24 21:33 ` Ken Brown
2010-07-24 21:34 ` Dan Nicolaescu
2010-07-25 14:38 ` Ken Brown [this message]
2010-07-25 20:39 ` Dan Nicolaescu
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=4C4C4C52.9050801@cornell.edu \
--to=kbrown@cornell.edu \
--cc=6715@debbugs.gnu.org \
--cc=dann@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).