From: nalaginrut <nalaginrut@gmail.com>
To: guile-devel Development <guile-devel@gnu.org>
Subject: [Fwd: Re: SCM_BOOL_T became #nil ?]
Date: Wed, 23 Feb 2011 12:40:08 +0800 [thread overview]
Message-ID: <1298436008.2832.6.camel@Renee-desktop> (raw)
> >>
> >> Well~I modified the include path and it's done.
> >> Thanks all!
> >
> > If you use `guile-config compile` (and `guile-config link`) in your Makefile it will come out right.
>
> Unless you're also using some other "foo-config" script for the same object file (defining Guile wrappers for the Foo API?), and that one is installed in /usr/local where the old version of Guile is, you don't get the command-line order right for your specific installation quirks, etc.
>
> I don't think there is a good answer to guarantee consistent versions; some additional technique to check for consistency doesn't seem like a horrible idea, though most packages I've worked with just seem to make do with the assumption that you'll figure out how to get this right if you're installing multiple versions.
>
> Ken
Definitely sure. I used `guile-config compile` in my Makefile. But the
header file still missing. So I modified the include path directly. I
think there're some manage/control work in Guile-2.0 need to be done.
--
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
reply other threads:[~2011-02-23 4:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1298436008.2832.6.camel@Renee-desktop \
--to=nalaginrut@gmail.com \
--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).