From: Ken Brown <kbrown@cornell.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: New emacs maintainer for cygwin
Date: Tue, 19 May 2009 22:39:43 -0400 [thread overview]
Message-ID: <4A136D6F.20903@cornell.edu> (raw)
In-Reply-To: <jwv1vqky14f.fsf-monnier+emacs@gnu.org>
On 5/19/2009 10:14 PM, Stefan Monnier wrote:
>> --- origsrc/emacs-23.0.92/src/s/cygwin.h 2009-01-08 06:46:27.000000000 -0500
>> +++ src/emacs-23.0.92/src/s/cygwin.h 2009-05-17 11:40:55.812500000 -0400
>> @@ -108,8 +108,12 @@ along with GNU Emacs. If not, see <http
>> /* 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
>> +/* but this can cause problems if the user later rebases; so I'm
>> + changing it (KB) */
>> +
>> +/* #define DATA_SEG_BITS 0x20000000 */
>> +/* #define LINKER $(CC) -Wl,--image-base,DATA_SEG_BITS */
>> +#define LINKER $(CC)
>
> If that can be used (which requires the use of USE_LSB_TAG), it's
> a better solution indeed.
Could you elaborate on this? I don't know anything about USE_LSB_TAG.
All I know is that I applied the patch and built emacs, and so far it
seems to work fine. But I only did this a day or two ago, so maybe a
problem could still show up. (Previously I've always used the
workaround described in etc/PROBLEMS.) Is there some test I should try
to see if my build is OK?
Thanks.
Ken
next prev parent reply other threads:[~2009-05-20 2:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 13:41 New emacs maintainer for cygwin Ken Brown
2009-05-15 14:16 ` Eli Zaretskii
2009-05-15 14:35 ` Ken Brown
2009-05-15 14:42 ` Lennart Borgman
2009-05-15 14:55 ` Chong Yidong
2009-05-17 4:01 ` Stefan Monnier
2009-05-20 0:21 ` Ken Brown
2009-05-20 2:14 ` Stefan Monnier
2009-05-20 2:39 ` Ken Brown [this message]
2009-05-20 15:22 ` Stefan Monnier
2009-05-20 17:37 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2009-05-20 8:05 Angelo Graziosi
2009-05-20 12:30 ` Ken Brown
2009-05-20 12:46 ` Angelo Graziosi
2009-05-20 22:19 Angelo Graziosi
2009-05-20 22:39 ` Ken Brown
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=4A136D6F.20903@cornell.edu \
--to=kbrown@cornell.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).