[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Fwd: Re: SCM_BOOL_T became #nil ?]
From: |
nalaginrut |
Subject: |
[Fwd: Re: SCM_BOOL_T became #nil ?] |
Date: |
Wed, 23 Feb 2011 12:40:08 +0800 |
> >>
> >> 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Fwd: Re: SCM_BOOL_T became #nil ?],
nalaginrut <=