From: Daniel Jacobowitz <drow@false.org>
To: Bhushan Attarde <Bhushan.Attarde@kpitcummins.com>
Cc: gdb@sourceware.org
Subject: Re: error message : I'm sorry, Dave, I can't do that.Symbolformat'elf32-xc16x' unknown.
Date: Thu, 27 Sep 2007 13:46:00 -0000 [thread overview]
Message-ID: <20070927124403.GA29229@caradoc.them.org> (raw)
In-Reply-To: <7B5265FF85A78C4BB9DAD0EE699C476002C01BC7@sohm.kpit.com>
On Thu, Sep 27, 2007 at 06:03:31PM +0530, Bhushan Attarde wrote:
> 1.There were some undefined references to `_libintl_dgettext'
>
> /* this is the part of gdb/config.log file */
>
> configure:21854: checking for ELF support in BFD
> configure:21878: i686-pc-cygwin-gcc -o conftest.exe -Os
> -I/cygdrive/c/cyggdb/src/gdb-6.7.50_20070918/gdb/../include -I../bfd
> -I/cygdrive/c/cyggdb/src/gdb-6.7.50_20070918/gdb/../bfd -L../bfd
> -L../libiberty conftest.c -lncurses -lm -lbfd -liberty >&5
> ../bfd/libbfd.a(elf.o):elf.c:(.text+0x4d9): undefined reference to
> `_libintl_dgettext'
Aha!
This means the configure check is buggy. What happens if you replace
this line:
LIBS="$LIBS -lbfd -liberty"
with this:
LIBS="$LIBS -lbfd -liberty $LIBINTL"
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-27 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7B5265FF85A78C4BB9DAD0EE699C476002B73136@sohm.kpit.com>
2007-09-26 21:28 ` error message : I'm sorry, Dave, I can't do that.Symbolformat 'elf32-xc16x' unknown Daniel Jacobowitz
2007-09-27 12:44 ` error message : I'm sorry, Dave, I can't do that.Symbolformat'elf32-xc16x' unknown Bhushan Attarde
2007-09-27 13:46 ` Daniel Jacobowitz [this message]
2007-09-27 13:49 ` error message : I'm sorry, Dave, I can't dothat.Symbolformat'elf32-xc16x' unknown Bhushan Attarde
2007-09-27 15:34 ` Daniel Jacobowitz
2007-09-26 7:36 error message : I'm sorry, Dave, I can't do that.Symbolformat 'elf32-xc16x' unknown Bhushan Attarde
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=20070927124403.GA29229@caradoc.them.org \
--to=drow@false.org \
--cc=Bhushan.Attarde@kpitcummins.com \
--cc=gdb@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