From: Keith Seitz <keiths@redhat.com>
To: Backhaus Willy <w.backhaus@newage-avkseg.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: RE: Insight build error
Date: Wed, 08 Dec 2004 18:27:00 -0000 [thread overview]
Message-ID: <1102530411.2774.11.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <000301c4dd38$97e76d50$f30210ac@backhaus>
On Wed, 2004-12-08 at 07:14, Backhaus Willy wrote:
> ok.. I used --disable-nls, but now I got another error:
> undefined reference to `_f_parse'
> undefined reference to `_java_parse'
> undefined reference to `_java_error'
> undefined reference to `_c_error'
> undefined reference to `_pascal_parse'
[and a bunch more]
These are all language functions that come from yacc files. Did the C
files get generated on your machine? ["ls *-exp.c" in your gdb build
directory.]
If not, make sure that yacc is available and working.
If they did get generated, please ask on the gdb list for more help.
Keith
next prev parent reply other threads:[~2004-12-08 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 12:10 Backhaus Willy
2004-12-08 12:23 ` Dave Korn
2004-12-08 15:14 ` Backhaus Willy
2004-12-08 18:27 ` Keith Seitz [this message]
2004-12-14 17:54 ` Insight build error - success Backhaus Willy
2004-12-14 18:18 ` Keith Seitz
2005-05-02 13:16 Insight build error neuwald
2005-05-02 13:51 ` Fernando Nasser
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=1102530411.2774.11.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=w.backhaus@newage-avkseg.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).