From: Nala Ginrut <nalaginrut@gmail.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: configuring guile packages [was: GNU Guile 2.9.8 Released [beta]]
Date: Wed, 8 Jan 2020 22:21:18 +0800 [thread overview]
Message-ID: <CAPjoZoeWxHdpMU5AyqwPBhb0_JBncUpP40ciidyZ_zhv-S+Zow@mail.gmail.com> (raw)
In-Reply-To: <CAPjoZocw4CACiKUcCCTTpe_Fq9kEtAK468vdgRi3jzuWN0Ckzw@mail.gmail.com>
Finally I found the problem is that I left a m4/guile.m4 in Artanis for
some reasons. It's solved by remove it.
Thanks for all the helps!
Best regards
On Mon, Jan 6, 2020 at 2:56 PM Nala Ginrut <nalaginrut@gmail.com> wrote:
> Hi Matt!
> Thanks for the help.
> However, it seems doesn't work for me. I think your solution is to solve
> mixed guile version detection issue, right?
> I'm building it in docker, a pure clean Debian10 environment. Hmm...
>
> On Sat, Jan 4, 2020 at 7:29 AM Matt Wette <matt.wette@gmail.com> wrote:
>
>>
>>
>> On 1/3/20 10:44 AM, Matt Wette wrote:
>> > On 1/3/20 6:53 AM, Matt Wette wrote:
>> >>> I am running into other issues, however, when there is a
>> >>> guile in my path that appears before anything else, but a guile-2
>> >>> that appears from another directory. I am working to add
>> >>> --with-guile to fix that. I'm having problems checking against
>> >>> 2.0.14, for example.
>> > I have been working on my configures. I have separate guile-2.0.14,
>> > -2.2.4 and -2.9.8 installs.
>> > To get everything to work I ended up with the following configure.ac
>> > and nyacc.m4. Not beautiful
>> > but it's working for 2.0.14, 2.2.X and 2.9.8.
>> >
>> > ===== snip from configure.ac =====
>> > m4_include([./pkg.m4])
>> > m4_include([./guile.m4])
>> > m4_include([./nyacc.m4])
>> >
>> > AC_ARG_WITH(guile, [ --with-guile path to binary],
>> > ,with_guile=unspecified)
>> >
>> > if test "_$with_guile" != "_unspecified"; then
>> > GUILE=$with_guile
>> > GUILE_EFFECTIVE_VERSION=`$GUILE -c "(display (effective-version))"`
>> > guile_libdir=`$GUILE -c "(display (assq-ref %guile-build-info
>> > 'libdir))"`
>> > PKG_CONFIG_LIBDIR=$guile_libdir/pkgconfig
>> > PKG_CONFIG=pkg-config
>> > export PKG_CONFIG_LIBDIR
>> > else
>> > GUILE_PKG([3.2 3.0 2.9 2.2 2.0])
>> > GUILE_PROGS
>> > fi
>> >
>> > GUILE_SITE_DIR
>> > GUILE_SITE_GO_DIR
>> > GUILE_DATA_DIR
>> >
>> > ==========================
>>
>> So I changed configure arg from "--with-guile=/path/to/guile" to
>> "GUILE=/path/to/guile"
>> AC_ARG_VAR([GUILE],[path to guile binary])
>> if test "x$ac_env_GUILE_set" = "xset"; then
>> GUILE_EFFECTIVE_VERSION=`$GUILE -c "(display (effective-version))"`
>> guile_libdir=`$GUILE -c "(display (assq-ref %guile-build-info
>> 'libdir))"`
>> PKG_PROG_PKG_CONFIG
>> PKG_CONFIG_LIBDIR=$guile_libdir/pkgconfig
>> export PKG_CONFIG_LIBDIR
>> else
>> GUILE_PKG([3.0 2.9 2.2 2.0])
>> GUILE_PROGS
>> fi
>>
>>
>>
>>
>>
>>
>>
next prev parent reply other threads:[~2020-01-08 14:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 13:36 GNU Guile 2.9.8 Released [beta] Andy Wingo
2020-01-03 5:34 ` Nala Ginrut
2020-01-03 9:02 ` tomas
2020-01-03 14:29 ` Matt Wette
2020-01-03 14:53 ` Matt Wette
2020-01-03 18:44 ` configuring guile packages [was: GNU Guile 2.9.8 Released [beta]] Matt Wette
2020-01-03 23:29 ` Matt Wette
2020-01-06 6:56 ` Nala Ginrut
2020-01-08 14:21 ` Nala Ginrut [this message]
2020-01-08 18:24 ` Jason Earl
2020-01-08 18:43 ` Nala Ginrut
2020-01-05 10:41 ` GNU Guile 2.9.8 Released [beta] Andy Wingo
2020-01-07 20:00 ` Stefan Israelsson Tampe
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=CAPjoZoeWxHdpMU5AyqwPBhb0_JBncUpP40ciidyZ_zhv-S+Zow@mail.gmail.com \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@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).