From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: jasonr@gnu.org, mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: The bootstrap of Emacs on Cygwin is broken [Is also: unicode branch is merged to trunk]
Date: Tue, 05 Feb 2008 22:17:52 +0200 [thread overview]
Message-ID: <u7ihjtaxb.fsf@gnu.org> (raw)
In-Reply-To: <47A8367D.60803@alice.it> (message from Angelo Graziosi on Tue, 05 Feb 2008 11:12:13 +0100)
> Date: Tue, 05 Feb 2008 11:12:13 +0100
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org, jasonr@gnu.org
>
> -#define STATIC_HEAP_SIZE (12 * 1024 * 1024)
> +#ifdef CYGWIN
> + #define STATIC_HEAP_SIZE (32 * 1024 * 1024)
> +#else
> + #define STATIC_HEAP_SIZE (12 * 1024 * 1024)
> +#endif
>
> int debug_sheap = 0;
> ========================================================
>
> (Eli, if you object that things as "#ifdef CYGWIN" should go to
> cygwin.h, observe the sheap.c yet contains an "#ifdef CYGWIN sbrk...")
Actually, I wonder why do you need "#ifdef CYGWIN" at all: sheap.c is
compiled _only_ for the Cygwin build (see src/Makefile.in). It looks
like you can change the above line unconditionally.
next prev parent reply other threads:[~2008-02-05 20:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 20:32 The bootstrap of Emacs on Cygwin is broken [Is also: unicode branch is merged to trunk] Angelo Graziosi
2008-02-02 18:03 ` Eli Zaretskii
2008-02-02 19:32 ` Angelo Graziosi
2008-02-02 19:43 ` Eli Zaretskii
2008-02-02 21:21 ` Angelo Graziosi
2008-02-03 4:10 ` Eli Zaretskii
2008-02-03 9:19 ` Angelo Graziosi
2008-02-03 19:40 ` Eli Zaretskii
2008-02-03 21:02 ` Angelo Graziosi
2008-02-03 21:02 ` Jason Rumney
2008-02-03 21:14 ` Angelo Graziosi
2008-02-04 4:19 ` Eli Zaretskii
2008-02-04 8:39 ` Angelo Graziosi
2008-02-04 9:00 ` YAMAMOTO Mitsuharu
2008-02-04 10:35 ` Angelo Graziosi
2008-02-04 11:01 ` YAMAMOTO Mitsuharu
2008-02-04 11:11 ` Jason Rumney
2008-02-04 20:55 ` Eli Zaretskii
2008-02-04 22:07 ` Angelo Graziosi
2008-02-05 4:17 ` Eli Zaretskii
2008-02-05 2:10 ` Angelo Graziosi
2008-02-05 4:17 ` Eli Zaretskii
2008-02-05 10:12 ` Angelo Graziosi
2008-02-05 10:19 ` Jason Rumney
2008-02-05 10:52 ` Angelo Graziosi
2008-02-05 11:10 ` Jason Rumney
2008-02-05 12:03 ` Angelo Graziosi
2008-02-05 20:17 ` Eli Zaretskii [this message]
2008-02-05 20:49 ` Angelo Graziosi
2008-02-06 4:10 ` Eli Zaretskii
2008-02-06 15:27 ` Angelo Graziosi
2008-05-28 2:15 ` Jashy
2008-05-28 3:06 ` Stefan Monnier
2008-05-28 3:21 ` YAMAMOTO Mitsuharu
2008-02-05 17:22 ` Angelo Graziosi
2008-02-04 4:16 ` Eli Zaretskii
2008-02-04 8:58 ` Jason Rumney
2008-02-02 18:03 ` Dan Nicolaescu
2008-02-02 18:32 ` Eli Zaretskii
2008-05-28 7:42 ` Angelo Graziosi
2008-05-28 10:20 ` Jashy
2008-05-28 10:30 ` YAMAMOTO Mitsuharu
2008-05-28 11:36 ` Jashy
2008-05-28 12:06 ` YAMAMOTO Mitsuharu
2008-05-28 13:16 ` Jashy
2008-05-28 17:21 ` Angelo Graziosi
2008-05-29 0:38 ` YAMAMOTO Mitsuharu
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=u7ihjtaxb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).