public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Dave Brolley <brolley@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Problem running cgen for opcodes
Date: Mon, 16 Jun 2003 21:47:00 -0000	[thread overview]
Message-ID: <16110.15078.658988.526976@casey.transmeta.com> (raw)
In-Reply-To: <3EEE39BA.2030802@redhat.com>

Dave Brolley writes:
 > I'm getting the following when trying to regenerate the opcodes sources 
 > for xstormy16. I haven't run cgen for opcodes in a while, so perhaps I'm 
 > missing something which has changed:
 > 
 > My guile is
 > 
 >  >> guile -v
 > Guile 1.4
 > Copyright (c) 1995, 1996, 1997, 2000 Free Software Foundation
 > Guile may be distributed under the terms of the GNU General Public Licence;
 > certain other uses are permitted as well.  For details, see the file
 > `COPYING', which is included in the Guile distribution.
 > There is no warranty, to the extent permitted by law.
 > 
 >  >> make stamp-xstormy16
 > make run-cgen arch=xstormy16 prefix=xstormy16 options= extrafiles=
 > make[1]: Entering directory 
 > `/notnfs/brolley/sources/build/i686-pc-linux-gnu/xstormy16-elf/opcodes'
 > /bin/sh /home/brolley/sources/src/opcodes/cgen.sh opcodes 
 > /home/brolley/sources/src/opcodes `if test -f ../guile/libguile/guile ; 
 > then echo ../guile/libguile/guile; else echo guile ; fi` \
 >   /home/brolley/sources/src/opcodes/../cgen "-v" xstormy16 xstormy16 \
 >   ""
 > guile: Unable to find file "rtl-traverse" in load path
 > make[1]: *** [run-cgen] Error 2

cvs update cgen # should fix things

rtl-traverse.scm is a new file, and I just checked, I did remember
to check it in :-)

      reply	other threads:[~2003-06-16 21:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16 21:40 Dave Brolley
2003-06-16 21:47 ` Doug Evans [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=16110.15078.658988.526976@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=brolley@redhat.com \
    --cc=cgen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).