From: Marius Bakke <mbakke@fastmail.com>
To: "Wiktor Żelazny" <wz@freeshell.de>, 38178@debbugs.gnu.org
Subject: [bug#38178] [WIP v2] gnu: Add grass.
Date: Sat, 21 Mar 2020 21:21:23 +0100 [thread overview]
Message-ID: <875zex5uik.fsf@devup.no> (raw)
In-Reply-To: <20191114153036.scgoex7zqc5r53cu@wz.localdomain>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
Wiktor Żelazny <wz@freeshell.de> writes:
> A new version of GRASS GIS got released, which gave me an opportunity
> to bump the version in the old definition and recompile. The errors are
> there, but do not hinder the successful build. Apparently, they have
> been there from the beginning; I just didn’t notice — both bad and
> good news.
>
> The real error (for now) is
>
> In unknown file:
> 0 (%resolve-variable (7 . wxpython) #<directory (g…>)
>
> ERROR: In procedure %resolve-variable:
> Unbound variable: wxpython
>
> I tried changing “wxpython” to “python-wxpython”, but this also
> is not recognized. So there’s something wrong with the way I defined
> the wrapping.
Did you get anywhere with this patch? Can you rebase it on the current
master branch for easier testing? TIA!
By the way, sorry for the sloooooow responses...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-03-21 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 11:31 [bug#38150] [WIP] gnu: Add grass Wiktor Żelazny
2019-11-09 22:46 ` Marius Bakke
2019-11-12 15:04 ` [bug#38178] [WIP v2] " Wiktor Żelazny
[not found] ` <handler.38178.B.15735711166598.ack@debbugs.gnu.org>
2019-11-14 15:30 ` Wiktor Żelazny
2020-03-21 20:21 ` Marius Bakke [this message]
2020-03-22 8:57 ` Guillaume Le Vaillant
2020-03-24 10:57 ` bug#38178: " Guillaume Le Vaillant
2020-03-24 21:16 ` [bug#38178] " Wiktor Żelazny
2020-03-24 21:19 ` Wiktor Żelazny
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=875zex5uik.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=38178@debbugs.gnu.org \
--cc=wz@freeshell.de \
/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).