all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan D." <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 19:48:12 +0100	[thread overview]
Message-ID: <45DDE56C.6070909@swipnet.se> (raw)
In-Reply-To: <uvehukeha.fsf@gnu.org>

Eli Zaretskii wrote:
> 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 did make distclean, reconfigured, and I still get this:

vm-limit.o: In function `check_memory_limits':
/home/jhd/src/emacs-22.0.93/src/vm-limit.c:185: undefined reference to 
`___morecore'
vm-limit.o: In function `memory_warnings':
/home/jhd/src/emacs-22.0.93/src/vm-limit.c:259: undefined reference to 
`___after_morecore_hook'

I see this in src/Makefile.in:

#ifdef CYGWIN
/* Cygwin differs because of its unexec(). */
otherobj= $(termcapobj) $(gmallocobj) $(rallocobj) lastfile.o vm-limit.o 
$(allocaobj) $(widgetobj) $(LIBOBJS)
#else
otherobj= $(termcapobj) lastfile.o $(mallocobj) $(allocaobj) 
$(widgetobj) $(LIBOBJS)
#endif

so apparently the solution is more complex.  Maybe we just should say 
that Gtk+ and cygwin is not possible?

    Jan D.

  parent reply	other threads:[~2007-02-22 18:48 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
2007-02-23 18:07     ` Eli Zaretskii
2007-02-22 18:48   ` Jan D. [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45DDE56C.6070909@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.