From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Failure to link GDB 7.5
Date: Sat, 18 Aug 2012 17:03:00 -0000 [thread overview]
Message-ID: <83628ggmji.fsf@gnu.org> (raw)
In-Reply-To: <20120818155136.GG2798@adacore.com>
> Date: Sat, 18 Aug 2012 08:51:36 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > What is wrong with my libiconv? (There's no other libiconv on this
> > system, which is why I built my own some time ago.)
>
> I do not think it's your libiconv. It looks like the link command is
> missing the reference to libiconv (something like -liconv, or /path/to/
> libiconv.so in your case [which I find a little unusual on a Unix system]).
> It is probably a consequence of how you configured GDB. I think that
> if you configure with --with-libiconv-prefix=/path/to/libiconv/prefix,
> everything should work (famous last words).
It didn't work (note that in the original build, I showed a line from
the configure script output that found my libiconv).
But your suggestion pointed me in the right direction: I eventually
succeeded by running "make INTL='-L/home/e/eliz/lib -liconv'".
I wonder why the default command didn't work. Let me know if you need
me to dig deeper.
Thanks.
next prev parent reply other threads:[~2012-08-18 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 12:42 Failure to link GDB 7.6 Eli Zaretskii
2012-08-18 15:51 ` Joel Brobecker
2012-08-18 17:03 ` Eli Zaretskii [this message]
2012-08-18 17:17 ` Failure to link GDB 7.5 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=83628ggmji.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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