From: Meino.Cramer@gmx.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Upgrade of gdb this morning failed to compile
Date: Sat, 29 Oct 2016 05:03:13 +0200 [thread overview]
Message-ID: <20161029030313.GA5279@solfire> (raw)
Hi,
the daily update I usually do failed while compiling gdb:
Before I post every bit/log of the compilation process...
Here are the last lines. Is there already known, how to fix that?
libdecnumber.a -ldl -ldl -ltermcap -lncurses -lm -ldl -lpthread -ldl -lutil -lm -lpython2.7 -Xlinker -export-dynamic ../libiberty/libiberty.a build-gnulib/import/libgnu.a -ldl -Wl,--dynamic-list=./proc-service.list
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libncurses.so.5, needed by /lib64/libreadline.so.6, may conflict with libncurses.so.6
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/../../../../x86_64-pc-linux-gnu/bin/ld: tui-io.o: undefined reference to symbol 'resetty'
/lib64/libtinfo.so.6: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
Makefile:1405: recipe for target 'gdb' failed
make[2]: *** [gdb] Error 1
make[2]: Leaving directory '/var/tmp/portage/sys-devel/gdb-7.10.1/work/gdb-7.10.1/gdb'
Makefile:8119: recipe for target 'all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory '/var/tmp/portage/sys-devel/gdb-7.10.1/work/gdb-7.10.1'
Makefile:845: recipe for target 'all' failed
make: *** [all] Error 2
* ERROR: sys-devel/gdb-7.10.1::gentoo failed (compile phase):
* emake failed
Cheers,
Meino
next reply other threads:[~2016-10-29 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 3:03 Meino.Cramer [this message]
2016-10-29 14:52 ` [gentoo-user] Upgrade of gdb this morning failed to compile Fernando Rodriguez
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=20161029030313.GA5279@solfire \
--to=meino.cramer@gmx.de \
--cc=gentoo-user@lists.gentoo.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