From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Linker error on ArchLinux
Date: Mon, 30 Oct 2017 22:11:25 +0100 [thread overview]
Message-ID: <20171030211125.GA13807@archie.localdomain> (raw)
In-Reply-To: <20171027123919.gi7ywcn64byd6esq@pengutronix.de>
Hi,
On Fri, Oct 27, 2017 at 02:39:19PM +0200, Michael Olbrich wrote:
> Hi,
>
> On Thu, Oct 26, 2017 at 07:09:23PM +0200, Clemens Gruber wrote:
> > when building PTXdist 2017.10.0 on current ArchLinux, a linker error occurs:
> > /usr/bin/ld: lxdialog/checklist.o: undefined reference to symbol 'acs_map'
> > /usr/lib/libtinfo.so.6: error adding symbols: DSO missing from commandline
> >
> > This occured after ArchLinux updated binutils to 2.29.1-1 and ncurses to
> > 6.0+20170902-2.
>
> Strange. I have binutils 2.29.1-6 and ncurses 6.0+20170902-1 here on Debian
> and it works just fine :-/. But:
>
> $ cat /usr/lib/x86_64-linux-gnu/libncurses.so
> INPUT(libncurses.so.5 -ltinfo)
>
> I guess this is different for you...
Yes:
$ cat /usr/lib/libncurses.so
INPUT(-lncursesw)
>
> > I could work around it by adding -ltinfo to LDFLAGS in the PTXdist
> > Makefile.
>
> We have some complex stuff in configure.ac to detect the curses library.
> Maybe we should just require ncurses and use pkg-config.
Yes, pkg-config would have caught it:
$ pkg-config --libs ncurses
-lncursesw -ltinfo
I noticed in the meantime, that the package maintainer made a commit, which
fixes the problem too:
https://git.archlinux.org/svntogit/packages.git/commit/?h=packages/ncurses&id=987faeb8442d44e76a7a58642e8e6432eb220c25
Thanks,
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-10-30 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 17:09 Clemens Gruber
2017-10-27 12:39 ` Michael Olbrich
2017-10-30 21:11 ` Clemens Gruber [this message]
2017-11-01 11:07 ` Michael Olbrich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171030211125.GA13807@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/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