From: "Thompson, David" <dthompson2@worcester.edu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Cannot build guile-chickadee.
Date: Wed, 20 Jun 2018 08:23:12 -0400 [thread overview]
Message-ID: <CAJ=Rwfb7fRBn+npvG+m_FXWwV1ZLB=s0mxG7sUfmf1-zcQZRWA@mail.gmail.com> (raw)
In-Reply-To: <87o9g5u7sf.fsf@elephly.net>
Hey Ricardo,
On Wed, Jun 20, 2018 at 5:27 AM, Ricardo Wurmus <rekado@elephly.net> wrote:
>
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>> Yes, last time I tried I had a similar issue: this is because you need
>>> the latest guile-sdl2 and guile-opengl.
>>
>> There does not seem to be a more recent guile-opengl. I have added
>> guile-sdl2-devel, which is built from the latest git commit.
>>
>> I also updated guile-chickadee to use the latest version from git.
>> Unfortunately, it still won’t build.
>>
>>> As I mentioned in an e-mail I've sent recently, I'd like to update the 2
>>> package definitions in Guix and add Chickadee to the Guix repo.
>>> What do you think?
>>
>> I’d prefer to use only released versions in Guix unless it cannot be
>> avoided to use development versions.
>
> Turns out that the Makefile of guile-sdl2 needed to be patched. After
> the patch Chickadee can be built with the release tarball.
>
> I’ll push the package definition shortly.
Could you tell me the commit id when you push it? I'd like to just
sort out the issues you were having and make new releases of
guile-sdl2 and chickadee so that Guix can have clean packages with no
hackery involved.
Thanks,
- Dave
next prev parent reply other threads:[~2018-06-20 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 1:03 Cannot build guile-chickadee Ricardo Wurmus
2018-06-20 7:00 ` Pierre Neidhardt
2018-06-20 9:01 ` Ricardo Wurmus
2018-06-20 9:27 ` Ricardo Wurmus
2018-06-20 12:23 ` Thompson, David [this message]
2018-06-20 12:37 ` Ricardo Wurmus
2018-06-20 12:44 ` Thompson, David
2018-06-20 14:43 ` Joshua Branson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ=Rwfb7fRBn+npvG+m_FXWwV1ZLB=s0mxG7sUfmf1-zcQZRWA@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.