unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: noloader@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Duplicate symbols due to <emacs dir>/src/termcap.c
Date: Fri, 05 Jan 2018 22:15:52 -0500	[thread overview]
Message-ID: <fv608ffziv.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAH8yC8nsa96fntUrURrSmJ4hAeXENU--HmtZno_D+Pmd=U=upA@mail.gmail.com> (Jeffrey Walton's message of "Wed, 3 Jan 2018 17:39:13 -0500")

Jeffrey Walton wrote:

>     /usr/local/lib64/libtermcap.a(tparam.o): In function `tparam':
>     /home/scripts/termcap-1.3.1/tparam.c:101: multiple definition of `tparam'
>     terminfo.o:terminfo.c:(.text+0x0): first defined here
>     terminfo.o: In function `tparam':
>     terminfo.c:(.text+0x4a): undefined reference to `tparm'
>     collect2: error: ld returned 1 exit status
>
> It looks like it is due to a local copy of termcap.c:
>
>     $ find . -name termcap.c
>     ./emacs-24.5/src/termcap.c

I think your conclusion about the cause of this issue is incorrect.
Emacs does not use its file src/termcap.c, except on MS-DOS.

> gcc -Demacs  -I. -I. -I../lib -I./../lib -MMD -MF deps/.d -MP -m64
> -march=native -fPIC  -Wl,-znocombreloc  -L/usr/local/lib64 -m64
> -Wl,-R,/usr/local/lib64 -Wl,--enable-new-dtags \
>   -o temacs  vm-limit.o dispnew.o frame.o scroll.o xdisp.o menu.o
> window.o charset.o coding.o category.o ccl.o character.o chartab.o
> bidi.o cm.o term.o terminal.o xfaces.o    emacs.o keyboard.o macros.o
> keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o
> fileio.o dired.o cmds.o casetab.o casefiddle.o indent.o search.o
> regex.o undo.o alloc.o data.o doc.o editfns.o callint.o eval.o
> floatfns.o fns.o font.o print.o lread.o syntax.o unexelf.o bytecode.o
> process.o gnutls.o callproc.o region-cache.o sound.o atimer.o doprnt.o
> intervals.o textprop.o composite.o xml.o inotify.o profiler.o
> decompress.o          terminfo.o lastfile.o gmalloc.o ralloc.o
> ../lib/libgnu.a                -lrt          -ltermcap
> -lpthread   -lm -lz

Note lack of "termcap.o" in the above.

> /usr/local/lib64/libtermcap.a(tparam.o): In function `tparam':
> /home/scripts/termcap-1.3.1/tparam.c:101: multiple definition of `tparam'
> terminfo.o:terminfo.c:(.text+0x0): first defined here
> terminfo.o: In function `tparam':
> terminfo.c:(.text+0x4a): undefined reference to `tparm'

So it looks like you have a hand-compiled, static version of libtermcap,
which is rather unusual. I think the problem is internal to your
libtermcap installation.

Emacs's configure script will use any of libtinfo, libncurses,
libterminfo in preference to libtermcap. So you might try installing one
of those, preferably the standard version from your (unspecified)
distribution, and retry with a clean build.

Note also that Emacs 25.3 is the latest release.



      parent reply	other threads:[~2018-01-06  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 22:39 Duplicate symbols due to <emacs dir>/src/termcap.c Jeffrey Walton
2018-01-05 13:32 ` ken
2018-01-06  3:15 ` Glenn Morris [this message]

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=fv608ffziv.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=noloader@gmail.com \
    /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).