From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, sds@gnu.org
Subject: Re: macosx linking fails: _freea referenced from: _rpl_realpath
Date: Tue, 25 Jun 2019 17:00:58 +0200 [thread overview]
Message-ID: <11319098.sJsK0NTokd@omega> (raw)
In-Reply-To: <m1blylvjfr.fsf@gnu.org>
Sam Steingold wrote:
> I get this error when linking Emacs:
>
> --8<---------------cut here---------------start------------->8---
> CCLD temacs
> Undefined symbols for architecture x86_64:
> "_freea", referenced from:
> _rpl_realpath in libgnu.a(canonicalize-lgpl.o)
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see invocation)
> make[1]: *** [temacs] Error 1
> --8<---------------cut here---------------end--------------->8---
>
> I also reported this as https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36356
> (https://lists.gnu.org/archive/html/bug-gnu-emacs/2019-06/msg01229.html)
1) After your latest "git pull" from emacs, have you done a "make distclean"
followed by a reconfiguration?
If you don't remember: Does the issue persist after a "make distclean"
followed by a reconfiguration?
2) Which symbols does
nm lib/malloca.o
show? If, as I would expect, it lists '_mmalloca' but not '_freea', it means
that the macro HAVE_ALLOCA was defined in the compilation unit
canonicalize-lgpl.c but not defined in the compilation unit malloca.c.
Can you investigate why this is so? (Where is HAVE_ALLOCA defined? In config.h,
I would guess. It is undefined somewhere? I would guess no. What are the
preprocessor symbols that are defined [use "$CC -E -dM"] in the
compilation unit canonicalize-lgpl.c, versus the compilation unit malloca.c?
Bruno
next prev parent reply other threads:[~2019-06-25 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 14:16 macosx linking fails: _freea referenced from: _rpl_realpath Sam Steingold
2019-06-25 15:00 ` Bruno Haible [this message]
2019-06-25 16:19 ` Sam Steingold
2019-06-25 17:11 ` Bruno Haible
2019-06-25 18:26 ` Sam Steingold
2019-06-25 20:31 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11319098.sJsK0NTokd@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=sds@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.
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).