From: "Backhaus Willy" <w.backhaus@newage-avkseg.com>
To: <gdb@sources.redhat.com>
Subject: error when building gdb?
Date: Thu, 09 Dec 2004 08:38:00 -0000 [thread overview]
Message-ID: <000901c4ddca$63be6190$f30210ac@backhaus> (raw)
hello,
I'm trying to build Insight for arm-elf.
I use the CVS version.
following error message comes:
rm -f gdb.exe
/bin/gcc -g -O2 -Wl,--subsystem,console \
-o gdb.exe gdb.o libgdb.a \
rdi-share/libangsd.a ../sim/arm/libsim.a ../bfd/libbfd.a
../readline/libreadline.a ../opcodes/libopcodes.a ../libiberty/libiberty.a
../libgui/src/libgui.a -L/home/backhaus/itcl/itcl -litcl32 -L/home/backhaus/
itcl/itk -litk32 -L/home/backhaus/tk/win -ltk84 -L/home/backhaus/tcl/win -lt
cl84 -lgdi32 -lcomdlg32 -limm32 -lcomctl32 -lshell32 -ltermcap -lm -licon
v ../libiberty/libiberty.a -luser32 -lshell32 -lgdi32 -lcomdlg32 -ladvapi32
libgdb.a(f-lang.o)(.rdata+0x460): In function `f_create_fundamental_type':
/ecos-c/gnutools/src/insight_cvs/src/gdb/f-lang.c:258: undefined reference
to `_f_parse'
[and a bunch more]
any ideas?
I'm using cygwin and Win2000.
thanks in advance.
regards,
Willy
next reply other threads:[~2004-12-09 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 8:38 Backhaus Willy [this message]
2004-12-09 19:25 ` Dave Korn
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='000901c4ddca$63be6190$f30210ac@backhaus' \
--to=w.backhaus@newage-avkseg.com \
--cc=gdb@sources.redhat.com \
/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