From: brettg@posteo.net
To: Brett Gilio <brettg@posteo.net>
Cc: Guix-patches <guix-patches-bounces+brettg=posteo.net@gnu.org>,
34932@debbugs.gnu.org
Subject: [bug#34932] [PATCH] gnu: godot: Update to 3.1.
Date: Thu, 21 Mar 2019 02:20:51 +0100 [thread overview]
Message-ID: <d97a3eee7d71fb868c65152790a01a89@posteo.net> (raw)
In-Reply-To: <87d0mlgh9q.fsf@posteo.net>
This patch is definitely not finished. I need some help. I know that the
openssl directory is being deleted in favor of it being compiled using
the openssl version from the inputs. However, with this line in the
recipe, it fails to compile. Is it perhaps a version compatibility with
openssl?
On 21.03.2019 02:14, Brett Gilio wrote:
>
next prev parent reply other threads:[~2019-03-21 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 1:14 [bug#34932] [PATCH] gnu: godot: Update to 3.1 Brett Gilio
2019-03-21 1:20 ` brettg [this message]
2020-01-30 11:40 ` bug#34932: " Marius Bakke
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d97a3eee7d71fb868c65152790a01a89@posteo.net \
--to=brettg@posteo.net \
--cc=34932@debbugs.gnu.org \
--cc=guix-patches-bounces+brettg=posteo.net@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).