help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unable to build Emacs 23.3 Release Candidate 2


From: Eli Zaretskii
Subject: Re: Unable to build Emacs 23.3 Release Candidate 2
Date: Sat, 09 Mar 2013 09:59:36 +0200

> Date: Fri, 8 Mar 2013 12:40:19 -0800 (PST)
> From: Luka <ribonucleico@gmail.com>
> Injection-Date: Fri, 08 Mar 2013 20:40:19 +0000
> 
> I am having problems compiling Emacs 23.3 Release Candidate 2:

You mean, Emacs 24.3 Release Candidate 2, right?

This should go to bug-gnu-emacs@gnu.org or emacs-devel@gnu.org.  The
release manager of Emacs must be alerted to any problems in release
candidates ASAP.

> I run `autogen.sh`, then  `./configure`, but when I run `make` I get this 
> error:

Why do you run autogen.sh when building from a release tarball?  It's
not needed, and you are running the risk of getting a bad configure
script and Makefile's.

>      gcc -std=gnu99     -I. -I../src -I../lib 
> -I/home/john/bin/emacs/rc/emacs-24.3/lib-src 
> -I/home/john/opt/emacs/rc/emacs-24.3/lib-src/../src -I/home/
>     john/bin/emacs/rc/emacs-24.3/lib-src/../lib  -Wl,-znocombreloc   -g3 -O2 
> -DEMACS_NAME="\"GNU Emacs\"" \
>               -DVERSION="\"24.3\"" 
> /home/john/bin/emacs/rc/emacs-24.3/lib-src/etags.c \
>               regex.o ../lib/libgnu.a  -o etags
>     regex.o: In function `stpncpy':
>     /usr/include/bits/string3.h:160: multiple definition of `stpncpy'
>     /tmp/ccntBfBN.o:/usr/include/bits/string3.h:160: first defined here
>     regex.o: In function `realpath':
> [...]
>     collect2: error: ld returned 1 exit status
>     make[1]: *** [etags] Error 1
>     make[1]: Leaving directory `/home/james/bin/emacs/rc/emacs-24.3/lib-src'
>     make: *** [lib-src] Error 2
> 
> I have never seen an error like this before. What does this mean and how do I 
> fix it?

Hard to tell.  It looks like some strange temporary object file
(/tmp/ccntBfBN.o) causes multiple definitions of inline functions
defined on standard headers.  Add -v to the link command line and
examine the output produced by GCC when linking, it might tell you
what is wrong.

If you cannot fix this or convince yourself it's a pilot error,
_please_ report it to one of the lists mentioned above ASAP.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]