emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Trunk bootstrap failure [Cygwin]


From: Ken Brown
Subject: Re: Trunk bootstrap failure [Cygwin]
Date: Wed, 07 Jul 2010 08:11:07 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1

On 7/7/2010 6:34 AM, Eli Zaretskii wrote:
Date: Wed, 07 Jul 2010 11:12:32 +0200
From: Angelo Graziosi<address@hidden>
CC: emacs<address@hidden>, Eli Zaretskii<address@hidden>,
  Ken Brown<address@hidden>

--- 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.

I'm afraid I don't have a clue either.

Ken



reply via email to

[Prev in Thread] Current Thread [Next in Thread]