From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Adding New C Files
Date: Tue, 15 Jun 2010 22:34:55 +0200 [thread overview]
Message-ID: <m3y6eghw5s.fsf@pobox.com> (raw)
In-Reply-To: <AANLkTimwcOldR-o2SnOvCa0WKTrJG7xgAgFiY2dggPrd@mail.gmail.com> (Noah Lavine's message of "Tue, 15 Jun 2010 10:06:29 -0400")
On Tue 15 Jun 2010 16:06, Noah Lavine <noah.b.lavine@gmail.com> writes:
> I've tried this, but I still get the error. Currently my files are in
> every long list of files (.c, .doc, .x, and .h), and I don't see any
> other places where source files for the main Guile program are listed.
> Is there anything else I can try?
Perhaps I misstated:
>> If you don't use SCM_DEFINE et al, you
>> might not need to copy the .doc or .x lines.
That should be, "you might need not to copy ..." :) Try removing the
.doc and/or .x forms.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-06-15 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 14:26 Adding New C Files Noah Lavine
2010-06-14 21:39 ` Andy Wingo
2010-06-15 14:06 ` Noah Lavine
2010-06-15 20:34 ` Andy Wingo [this message]
2010-06-18 2:14 ` Noah Lavine
2010-06-18 8:45 ` Andy Wingo
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=m3y6eghw5s.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.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).