unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Cc: emacs-devel@gnu.org
Subject: Re: make bootstrap:  need moral support.  :-(
Date: Tue, 21 Feb 2006 00:33:18 +0200	[thread overview]
Message-ID: <20060220223318.GA13290@flame.pc> (raw)
In-Reply-To: <20060220205725.GC78518@flame.pc>

On 2006-02-20 22:57, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
> Yes.
>
> The malloc/realloc -> xmalloc/xrealloc change to src/regex.c adds a
> conditional dependency on some of the allocators available in emacs/src/
> to lib-src files too.
>
> I'm currently building a snapshot with the following patch applied to
> see if it fixes things:

Actually, scratch that.  The `etags.c' source file already has
xrealloc() and xmalloc(), but they are static.  The patch that fixes
bootstrap for me here is much simpler :)

%%%
Index: emacs/lib-src/etags.c
===================================================================
--- emacs/lib-src/etags.c	(.../branches/gnu)	(revision 26)
+++ emacs/lib-src/etags.c	(.../trunk)	(revision 26)
@@ -414,8 +414,8 @@
 static void canonicalize_filename __P((char *));
 static void linebuffer_init __P((linebuffer *));
 static void linebuffer_setlen __P((linebuffer *, int));
-static PTR xmalloc __P((unsigned int));
-static PTR xrealloc __P((char *, unsigned int));
+PTR xmalloc __P((unsigned int));
+PTR xrealloc __P((char *, unsigned int));
 
 \f
 static char searchar = '/';	/* use /.../ searches */
@@ -6864,7 +6864,7 @@
 }
 
 /* Like malloc but get fatal error if memory is exhausted. */
-static PTR
+PTR
 xmalloc (size)
      unsigned int size;
 {
@@ -6874,7 +6874,7 @@
   return result;
 }
 
-static PTR
+PTR
 xrealloc (ptr, size)
      char *ptr;
      unsigned int size;
%%%

  reply	other threads:[~2006-02-20 22:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 15:07 make bootstrap: need moral support. :-( Alan Mackenzie
2006-02-19 21:27 ` Giorgos Keramidas
2006-02-20  2:31 ` Robert J. Chassell
2006-02-20  4:09   ` Miles Bader
2006-02-20 15:24   ` Randal L. Schwartz
2006-02-20 20:47     ` Michael Price
2006-02-20 20:57     ` Giorgos Keramidas
2006-02-20 22:33       ` Giorgos Keramidas [this message]
2006-02-20  4:58 ` Eli Zaretskii
2006-02-20  4:03   ` Alan Mackenzie
2006-02-20 20:52     ` Eli Zaretskii
2006-02-20 22:32       ` Alan Mackenzie
2006-02-21  4:34         ` Eli Zaretskii
2006-02-21  9:06           ` Jan D.
2006-02-21  9:44       ` Kim F. Storm
2006-02-20 16:21 ` Eric Hanchrow
2006-02-20 21:38   ` Giorgos Keramidas
2006-02-21  5:18     ` Ken Raeburn
2006-02-21  8:52       ` Giorgos Keramidas
2006-02-21  9:22         ` Ken Raeburn
2006-02-20 18:42 ` Richard M. Stallman
2006-02-20 22:37   ` Alan Mackenzie
2006-02-21 20:22     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2006-02-22 10:30 Francesco Potorti`
2006-02-22 10:54 ` Giorgos Keramidas

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=20060220223318.GA13290@flame.pc \
    --to=keramida@ceid.upatras.gr \
    --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).