[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New emacs maintainer for cygwin
From: |
Ken Brown |
Subject: |
Re: New emacs maintainer for cygwin |
Date: |
Wed, 20 May 2009 13:37:16 -0400 |
User-agent: |
Thunderbird 2.0.0.21 (Windows/20090302) |
On 5/20/2009 11:22 AM, Stefan Monnier wrote:
Could you elaborate on this? I don't know anything about USE_LSB_TAG. All
grep for USE_LSB_TAG in src/lisp.h. It's quite likely that Cygwin uses
it already (ideally, all systems should use it).
That does seem to be the case, if I understand src/lisp.h correctly.
I'm using gcc, so __GNUC__ is defined, and src/config.h contains #define
GNU_MALLOC 1. This should guarantee that USE_LSB_TAG is being used. Right?
I therefore propose the following patch to src/s/cygwin.h, which is a
slightly modified version of the one I sent yesterday:
--- cygwin.h.orig 2009-05-20 13:30:27.062500000 -0400
+++ cygwin.h 2009-05-20 13:31:17.140625000 -0400
@@ -105,11 +105,7 @@
#define SYSV_SYSTEM_DIR 1
#define UNEXEC unexcw.o
#define POSIX_SIGNALS 1
-/* force the emacs image to start high in memory, so dll relocation
- can put things in low memory without causing all sorts of grief for
- emacs lisp pointers */
-#define DATA_SEG_BITS 0x20000000
-#define LINKER $(CC) -Wl,--image-base,DATA_SEG_BITS
+#define LINKER $(CC)
/* Use terminfo instead of termcap. Fewer environment variables to
go wrong, more terminal types. */
I realize that this patch does not fix a regression from emacs 22.3, so
maybe it should wait until after 23.1 is released. But it affect only
the cygwin build, and it would simplify my task of patching etc/PROBLEMS
if it could be applied soon.
Ken