From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: dann@gnu.org, kbrow1i@gmail.com, emacs-devel@gnu.org
Subject: Re: Trunk bootstrap failure [Cygwin]
Date: Wed, 07 Jul 2010 13:34:19 +0300 [thread overview]
Message-ID: <8339vv8tsk.fsf@gnu.org> (raw)
In-Reply-To: <4C344500.9010906@alice.it>
> Date: Wed, 07 Jul 2010 11:12:32 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: emacs <emacs-devel@gnu.org>, Eli Zaretskii <eliz@gnu.org>,
> Ken Brown <kbrow1i@gmail.com>
>
> --- configure.orig 2010-07-02 11:27:38.000000000 +0200
> +++ configure 2010-07-06 10:45:21.656250000 +0200
> @@ -5864,7 +5864,7 @@
> case $opsys in
> cygwin )
> LIB_MATH=
> - START_FILES='ecrt0.o'
> + START_FILES='pre-crt0.o'
> ;;
> darwin )
> ## Adding -lm confuses the dynamic linker, so omit it.
> --- cygwin.h.orig 2010-06-06 11:34:28.000000000 +0200
> +++ cygwin.h 2010-07-07 10:24:22.625000000 +0200
> @@ -112,5 +112,7 @@
> returns ENOSYS. A workaround is to set G_SLICE=always-malloc. */
> #define G_SLICE_ALWAYS_MALLOC
>
> +#define TEXT_START 0x00400000
> +
> /* arch-tag: 5ae7ba00-83b0-4ab3-806a-3e845779191b
> (do not change this comment) */
> ============
>
> ...and Emacs (rev. 100739) bootstraps fine...
>
> But, are those patches the best solution? Are we sure that in the future
> there will not pitfalls or drawbacks?
>
> Eli, Ken, have you comments and/or suggestions?
Sorry, I don't know enough about the memory layout used by Cygwin and
about its startup code to speak intelligently about this.
next prev parent reply other threads:[~2010-07-07 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 23:35 Trunk bootstrap failure [Cygwin] Angelo Graziosi
2010-07-06 2:29 ` Dan Nicolaescu
2010-07-06 9:08 ` Angelo Graziosi
2010-07-06 15:19 ` Dan Nicolaescu
2010-07-07 9:12 ` Angelo Graziosi
2010-07-07 10:34 ` Eli Zaretskii [this message]
2010-07-07 12:11 ` Ken Brown
2010-07-07 16:22 ` Dan Nicolaescu
2010-07-08 0:16 ` Angelo Graziosi
2010-07-08 5:54 ` Dan Nicolaescu
2010-07-08 9:01 ` Angelo Graziosi
2010-07-08 10:09 ` Angelo Graziosi
2010-07-08 10:22 ` Eli Zaretskii
2010-07-08 10:32 ` Andreas Schwab
2010-07-08 23:07 ` Dan Nicolaescu
2010-07-09 13:49 ` Angelo Graziosi
2010-07-09 17:08 ` Dan Nicolaescu
2010-07-09 22:35 ` Angelo Graziosi
2010-07-10 1:36 ` 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=8339vv8tsk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=dann@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrow1i@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).