From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: guile-devel@gnu.org
Subject: Re: GUILE 1.6 CVS doesn't compile
Date: Sun, 10 Jul 2005 13:56:37 +0200 [thread overview]
Message-ID: <42D10CF5.7070405@xs4all.nl> (raw)
In-Reply-To: <877jfz2zzx.fsf@zip.com.au>
Kevin Ryde wrote:
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
>>I have changed it to use a pointer. It seems to work, and it seems to
>>compile.
>
>
> That can't be right can it? It's supposed to be an array of structs,
> not a pointer.
make check
isn't complaining.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-07-10 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 12:33 GUILE 1.6 CVS doesn't compile Han-Wen Nienhuys
2005-06-10 12:34 ` Han-Wen Nienhuys
2005-06-10 21:34 ` Kevin Ryde
2005-06-14 1:01 ` Han-Wen Nienhuys
2005-06-19 13:21 ` Han-Wen Nienhuys
2005-07-10 1:47 ` Kevin Ryde
2005-07-10 11:56 ` Han-Wen Nienhuys [this message]
2005-07-11 0:10 ` Kevin Ryde
2005-07-11 10:39 ` Han-Wen Nienhuys
2005-07-11 23:41 ` Kevin Ryde
2005-07-11 10:51 ` Han-Wen Nienhuys
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42D10CF5.7070405@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).