From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: Recent changes to regex.c break bootstrapping
Date: Mon, 20 Feb 2006 08:47:00 +0100 [thread overview]
Message-ID: <43F973F4.9060807@swipnet.se> (raw)
In-Reply-To: <200602200610.k1K6ANa25590@raven.dms.auburn.edu>
Luc Teirlinck wrote:
> After bootstrapping failed due to an undefined reference to xalloc, I
> made the obvious correction to xmalloc and installed in CVS, but after
> that bootstrapping still fails with:
>
> regex.o: In function `extend_range_table_work_area':
> /home/teirllm/emacscvsdir/emacs/lib-src/../src/regex.c:2069: undefined
> reference to `xrealloc'
> /home/teirllm/emacscvsdir/emacs/lib-src/../src/regex.c:2072: undefined
> reference to `xmalloc'
> regex.o: In function `regcomp':
> /home/teirllm/emacscvsdir/emacs/lib-src/../src/regex.c:6295: undefined
> reference to `xmalloc'
> /home/teirllm/emacscvsdir/emacs/lib-src/../src/regex.c:6301: undefined
> reference to `xmalloc'
> collect2: ld returned 1 exit status
> make[3]: *** [etags] Error 1
> make[3]: Leaving directory `/home/teirllm/emacscvsdir/emacs/lib-src'
> make[2]: *** [lib-src] Error 2
> make[2]: Leaving directory `/home/teirllm/emacscvsdir/emacs'
> make[1]: *** [bootstrap-build] Error 2
> make[1]: Leaving directory `/home/teirllm/emacscvsdir/emacs'
> make: *** [bootstrap] Error 2
>
> lisp.h is, at least conditionally, already included in regex.c
No, it is only included if emacs is #define:d (-Demacs), and it is not when
compiling from lib-src. But what are we trying to do, use xrealloc or define
xrealloc as realloc?
In the first case alloc.c needs to be linked in also, or perhaps
xrealloc/xmalloc defined in regex.c also (as it is in termcap.s for example).
Jan D.
next prev parent reply other threads:[~2006-02-20 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 6:10 Recent changes to regex.c break bootstrapping Luc Teirlinck
2006-02-20 7:47 ` Jan D. [this message]
2006-02-20 15:02 ` Andreas Schwab
2006-02-20 16:26 ` Chong Yidong
2006-02-20 17:08 ` Chong Yidong
2006-02-20 22:53 ` Giorgos Keramidas
2006-02-20 22:05 ` Richard M. Stallman
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=43F973F4.9060807@swipnet.se \
--to=jan.h.d@swipnet.se \
--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).