From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Failure to link GDB 7.6
Date: Sat, 18 Aug 2012 12:42:00 -0000 [thread overview]
Message-ID: <83boi8gynf.fsf@gnu.org> (raw)
On GNU/Linux, I get the following link error trying to build GDB 7.5:
gcc -g -O2 \
-o gdb gdb.o amd64-tdep.o amd64-linux-tdep.o i386-tdep.o i387-tdep.o i386-linux-tdep.o glibc-tdep.o solib-svr4.o symfile-mem.o linux-tdep.o linux-record.o ser-base.o ser-unix.o ser-pipe.o ser-tcp.o inf-ptrace.o fork-child.o i386-nat.o amd64-nat.o amd64-linux-nat.o linux-nat.o linux-osdata.o proc-service.o linux -thread-db.o linux-fork.o linux-procfs.o linux-ptrace.o remote.o dcache.o tracepoint.o ax-general.o ax-gdb.o remote-fileio.o cli-dump.o cli-decode.o cli-script.o cli-cmds.o cli-setshow.o cli-logging.o cli-interp.o cli-utils.o mi-out.o mi-console.o mi-cmds.o mi-cmd-env.o mi-cmd-var.o mi-cmd-break.o mi-cmd-stack.o mi-cmd-file.o mi-cmd-disas.o mi-symbol-cmds.o mi-cmd-target.o mi-cmd-info.o mi-interp.o mi-main.o mi-parse.o mi-getopt.o tui-command.o tui-data.o tui-disasm.o tui-file.o tui-hooks.o tui-interp.o tui-io.o tui-layout.o tui-out.o tui-regs.o tui-source.o tui-stack.o tui-win.o tui-windata.o tui-wingeneral.o tui-winsource.o tui.o python.o py-auto-load.o py-block.o py-bpe
../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -lncurses -lz -lm -L/home/e/eliz/lib/python2.6/config -lpthread -ldl -lutil -lm -lpython2.6 -Xlinker -export-dynamic /home/e/eliz/lib/libexpat.so -Wl,-rpath -Wl,/home/e/eliz/lib ../libiberty/libiberty.a build-gnulib/import/libgnu.a -ldl -rdynamic
/home/e/eliz/lib/python2.6/config/libpython2.6.a(posixmodule.o): In function `posix_tmpnam':
/home/e/eliz/Python-2.6.1/./Modules/posixmodule.c:7079: warning: the use of `tmpnam_r' is dangerous, better use `mkstemp'
/home/e/eliz/lib/python2.6/config/libpython2.6.a(posixmodule.o): In function `posix_tempnam':
/home/e/eliz/Python-2.6.1/./Modules/posixmodule.c:7034: warning: the use of `tempnam' is dangerous, better use `mkstemp'
charset.o: In function `do_cleanup_iterator':
/home/e/eliz/gdb-7.5/gdb/charset.c:615: undefined reference to `libiconv_close'
charset.o: In function `validate':
/home/e/eliz/gdb-7.5/gdb/charset.c:325: undefined reference to `libiconv_open'
/home/e/eliz/gdb-7.5/gdb/charset.c:329: undefined reference to `libiconv_close'
/home/e/eliz/gdb-7.5/gdb/charset.c:331: undefined reference to `libiconv_open'
/home/e/eliz/gdb-7.5/gdb/charset.c:335: undefined reference to `libiconv_close'
charset.o: In function `wchar_iterate':
/home/e/eliz/gdb-7.5/gdb/charset.c:648: undefined reference to `libiconv'
charset.o: In function `make_wchar_iterator':
/home/e/eliz/gdb-7.5/gdb/charset.c:594: undefined reference to `libiconv_open'
charset.o: In function `convert_between_encodings':
/home/e/eliz/gdb-7.5/gdb/charset.c:487: undefined reference to `libiconv_open'
/home/e/eliz/gdb-7.5/gdb/charset.c:509: undefined reference to `libiconv'
charset.o: In function `cleanup_iconv':
/home/e/eliz/gdb-7.5/gdb/charset.c:465: undefined reference to `libiconv_close'
collect2: ld returned 1 exit status
It uses libiconv I built myself:
checking how to link with libiconv... /home/e/eliz/lib/libiconv.so -Wl,-rpath -Wl,/home/e/eliz/lib
checking for iconv declaration... install-shextern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
What is wrong with my libiconv? (There's no other libiconv on this
system, which is why I built my own some time ago.)
TIA
next reply other threads:[~2012-08-18 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 12:42 Eli Zaretskii [this message]
2012-08-18 15:51 ` Joel Brobecker
2012-08-18 17:03 ` Failure to link GDB 7.5 Eli Zaretskii
2012-08-18 17:17 ` Joel Brobecker
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=83boi8gynf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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