From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: doc libdir and C code modules
Date: Tue, 07 Feb 2006 11:03:39 +1100 [thread overview]
Message-ID: <87d5i0m3vo.fsf@zip.com.au> (raw)
In-Reply-To: <87acd716ds.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 04 Feb 2006 15:38:23 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> I didn't realize that Autoconf could do @libdir@ substitutions so
> conveniently.
Actually I had it a bit wrong, the usual autoconf $(libdir) value
needs to get expanded by some shell/make. That'd be why I've been
using that way I guess :-). I updated the manual.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-07 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 0:28 doc libdir and C code modules Kevin Ryde
2006-02-04 15:38 ` Neil Jerram
2006-02-05 23:21 ` Kevin Ryde
2006-02-07 0:03 ` Kevin Ryde [this message]
2006-02-09 9:49 ` Neil Jerram
2006-02-14 19:47 ` Greg Troxel
2006-02-06 9:31 ` Ludovic Courtès
2006-02-07 0:11 ` Kevin Ryde
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=87d5i0m3vo.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).