From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Building without Emacs malloc, possible?
Date: Thu, 22 Feb 2007 07:57:59 +0100 [thread overview]
Message-ID: <45DD3EF7.9080906@swipnet.se> (raw)
In-Reply-To: <uvehukeha.fsf@gnu.org>
Eli Zaretskii skrev:
>> Date: Wed, 21 Feb 2007 21:31:17 +0100
>> From: =?ISO-8859-1?Q?Jan_Dj=E4rv?= <jan.h.d@swipnet.se>
>>
>> What is the status of building without Emac malloc? There are some problems
>> on cygwin + Gtk. Basically Gtk+ (glib actually) calls memalign, but on cygwin
>> this does not call the Emacs supplied memalign, but cygwins own. Since malloc
>> is the one Emacs has, cygwin memalign refuses to work. I don't know why the
>> Emace memalign is not called, dynamic libraries on W32 seems to behave strange
>> in this regard.
>
> That is very unfortunate. Using system malloc will cause Emacs to
> grow in its footprint much more than it does with gmalloc, possibly an
> unlimited growth. Did you try asking for advice on the Cygwin mailing
> list?
Yes, the advice was that Emacs should not use its own malloc in this case. If
that works, I'll add a configure check so that Emacs uses its own malloc on
cygwin except when Gtk+ is used. I still don't understand why the Emacs
supplied memalign doesn't get called.
>
>> One solution would be for Emacs to not use its own malloc, but that gives
>> compilation errors. I don't have the errors here, but they are unresolved
>> symbols in vm-limit.c.
>>
>> So, the question is what is need to compile on cygwin without Emacs malloc? I
>> just added
>>
>> #define SYSTEM_MALLOC
>>
>> to s/cygwin.h. Apparently something more is needed.
>
> Defining SYSTEM_MALLOC ought to be enough. What errors do you see?
> Do the same errors happen when you try building with SYSTEM_MALLOC on
> GNU/Linux?
>
> Btw, I think you need to "make distclean" and reconfigure after adding
> SYSTEM_MALLOC; maybe you didn't, and that's the reason for the
> problems?
I'll try again with that when I get access to the w32 machine again. Thanks
for the advice.
Jan D.
next prev parent reply other threads:[~2007-02-22 6:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 20:31 Building without Emacs malloc, possible? Jan Djärv
2007-02-22 4:23 ` Eli Zaretskii
2007-02-22 6:57 ` Jan Djärv [this message]
2007-02-23 18:07 ` Eli Zaretskii
2007-02-22 18:48 ` Jan D.
2007-02-23 18:12 ` Eli Zaretskii
2007-02-22 23:33 ` Stefan Monnier
2007-02-23 0:17 ` Jason Rumney
2007-02-23 6:42 ` Jan Djärv
2007-02-23 6:38 ` Jan Djärv
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=45DD3EF7.9080906@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).