From: "Dave Korn" <dave.korn@artimi.com>
To: <gdb@sources.redhat.com>
Subject: RE: error when building gdb?
Date: Thu, 09 Dec 2004 19:25:00 -0000 [thread overview]
Message-ID: <NUTMEGRseCaa23tt4LQ00000564@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <000901c4ddca$63be6190$f30210ac@backhaus>
> -----Original Message-----
> From: gdb-owner On Behalf Of Backhaus Willy
> Sent: 09 December 2004 08:38
> I'm trying to build Insight for arm-elf.
> I use the CVS version.
>
> following error message comes:
> 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?
The question you were asked on the insight list about this is still relevant:
these files are all supposed to have been automatically generated earlier on in
the build. Did those files (*-exp.c in the gdb subdirectory of your build dir)
get created? Do you have yacc installed and in your $PATH?
cheers,
DaveK
--
Can't think of a witty .sigline today....
prev parent reply other threads:[~2004-12-09 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 8:38 Backhaus Willy
2004-12-09 19:25 ` Dave Korn [this message]
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=NUTMEGRseCaa23tt4LQ00000564@NUTMEG.CAM.ARTIMI.COM \
--to=dave.korn@artimi.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