From: Torsten Mohr <tmohr@s.netic.de>
To: gdb@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: simulator for v850-unknown-elf (V850E)
Date: Wed, 10 May 2006 07:15:00 -0000 [thread overview]
Message-ID: <200605100015.13759.tmohr@s.netic.de> (raw)
In-Reply-To: <20060509214758.GA18775@nevyn.them.org>
Hi,
thanks for your hint.
> What sort of Linux host is this? It sounds like either this is an
> Insight-specific problem, or else there is something strange about your
> version of Bison/yacc. Every one of the undefined symbols is supposed
> to be handled with a #define in the generated parsers. And if you're
> building from a release tarball they shouldn't be regenerated at all.
basically i have a standard installation of the german distribution
SuSE 9.3 with a changed kernel. There's nothing really strange
about it.
schleim:~ # uname -a
Linux schleim 2.6.14.3 #2 SMP Tue Dec 13 23:55:17 CET 2005 i686 \
i686 i386 GNU/Linux
You are right, i have no "bison" installed on my system.
I just installed and re-configured and compiled.
All worked fine, i have a working v850-unknown-elf-insight
with simulator now.
Thanks for your hint,
Torsten.
prev parent reply other threads:[~2006-05-09 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 22:13 Torsten Mohr
2006-05-09 23:01 ` Daniel Jacobowitz
2006-05-10 7:15 ` Torsten Mohr [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=200605100015.13759.tmohr@s.netic.de \
--to=tmohr@s.netic.de \
--cc=drow@false.org \
--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