From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: [ANN] guile-curl 0.7
Date: Mon, 4 Jan 2021 11:46:37 -0800 [thread overview]
Message-ID: <CA+XASoUVgDeOqMtPTHoqw-pAPQP1ySyvr56EAgydMbOB7eYWQQ@mail.gmail.com> (raw)
In-Reply-To: <20210104120736.GB1108816@spikycactus.com>
On Mon, Jan 4, 2021 at 4:07 AM Mike Gran <spk121@yahoo.com> wrote:
>
> On Mon, Jan 04, 2021 at 12:42:34PM +0100, Ricardo Wurmus wrote:
> >
> > Hi Mike,
> >
> > > On Mon, Jan 04, 2021 at 10:02:57AM +0100, Ricardo Wurmus wrote:
> > >>
> > >> Aleix Conchillo Flaqu� <aconchillo@gmail.com> writes:
> > >>
> > >> > I'm trying to add guile-curl to homebrew-guile but ran into
> > >> > compilation issues in type.c using the tarball from your email.
> > >>
> > >> I can confirm this. (I just tried to upgrade the guile-curl package in
> > >> Guix.)
> > >
> > > How embarassing. The tarball had a bit of unreverted commit. I've
> > > regenerated the tarball, and the code in the repo is unchanged.
> > >
> > > The corrected tarball is
> > > http://lonelycactus.com/tarball/guile_curl-0.7.tar.gz
> >
> > Thank you!
> >
> > Unfortunately, I'm getting test failures due to an undefined variable:
>
> Curious indeed. I can't reproduce, but, I think I know what it is
> complaining about. Let me see what I can do.
>
I actually have the same issue:
scheme@(guile-user)> (use-modules (curl))
While compiling expression:
Unbound variable: CURLOPT_HAPROXYPROTOCOL
This is the output after a first try. On the first try I get:
scheme@(guile-user)> (use-modules (curl))
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /usr/local/share/guile/site/3.0/curl.scm
;;; /usr/local/share/guile/site/3.0/curl.scm:370:2: warning: possibly
unbound variable `%curl-easy-init'
;;; /usr/local/share/guile/site/3.0/curl.scm:375:2: warning: possibly
unbound variable `%curl-easy-handle?'
;;; /usr/local/share/guile/site/3.0/curl.scm:384:2: warning: possibly
unbound variable `%curl-easy-cleanup'
;;; /usr/local/share/guile/site/3.0/curl.scm:392:2: warning: possibly
unbound variable `%curl-easy-reset'
;;; /usr/local/share/guile/site/3.0/curl.scm:395:2: warning: possibly
unbound variable `CURLOPT_VERBOSE'
.....
.....
Note that GUILE_SYSTEM_EXTENSIONS_PATH is properly set and
libguile-curl file are there. I don't recall if the warnings are an
issue or not in other libraries, but I don't remember seeing them
either.
Aleix
next prev parent reply other threads:[~2021-01-04 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210104043628.GA1092151.ref@spikycactus.com>
2021-01-04 4:36 ` [ANN] guile-curl 0.7 Mike Gran
2021-01-04 7:16 ` Aleix Conchillo Flaqué
2021-01-04 9:02 ` Ricardo Wurmus
2021-01-04 11:36 ` Mike Gran via General Guile related discussions
2021-01-04 11:42 ` Ricardo Wurmus
2021-01-04 12:07 ` Mike Gran via General Guile related discussions
2021-01-04 19:46 ` Aleix Conchillo Flaqué [this message]
2021-01-04 18:43 ` Aleix Conchillo Flaqué
2021-01-04 23:23 ` Aleix Conchillo Flaqué
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=CA+XASoUVgDeOqMtPTHoqw-pAPQP1ySyvr56EAgydMbOB7eYWQQ@mail.gmail.com \
--to=aconchillo@gmail.com \
--cc=guile-user@gnu.org \
--cc=spk121@yahoo.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).