From: Dave Brolley <brolley@redhat.com>
To: cgen@sources.redhat.com
Subject: Problem with obj->string Change in sid-cpu.scm
Date: Tue, 09 May 2006 17:57:00 -0000 [thread overview]
Message-ID: <4460D7F3.2020706@redhat.com> (raw)
I'm having a problem with the change below. Guile is complaining that
obj->string is not bound. My version of guile is:
>> guile --version
Guile 1.3
Copyright (c) 1995, 1996, 1997 Free Software Foundation
Should I be using something newer or is there a way to accomplish the
same thing more portably?
Thanks,
Dave
------------------------------------------------
2005-12-28 Nathan Sidwell <nathan@codesourcery.com>
* sid-cpu.scm (-gen-hw-stream-and-destream-fns): Stringize mode
for concatenation.
(-hw-gen-write-stack-decl): Likewise.
next reply other threads:[~2006-05-09 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 17:57 Dave Brolley [this message]
[not found] ` <20060509180030.GB13413@redhat.com>
[not found] ` <4460DEBE.801@redhat.com>
2006-05-09 18:44 ` Problem with object->string " Frank Ch. Eigler
2006-05-09 19:04 ` Problem with object->string Change in sid-cpu.scm -- patch committed Dave Brolley
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=4460D7F3.2020706@redhat.com \
--to=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).