From: Leo Famulari <leo@famulari.name>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: wrap-python3: Use a bash wrapper for 'python3-config'. (was: python-pycairo in core-updates)
Date: Sun, 16 Oct 2016 14:14:07 -0400 [thread overview]
Message-ID: <20161016181407.GA5150@jasmine> (raw)
In-Reply-To: <87k2d9ou6u.fsf_-_@member.fsf.org>
On Sun, Oct 16, 2016 at 11:21:13AM +0800, 宋文武 wrote:
> >> Hi, python-wrapper has a broken `python3-config', which
> >> output cflags to the wrapper instead of the origin python3,
> >> leading the build failure of python-pycairo.
> >
> > So it appears to resolve the CFLAGS it returns relative to its own
> > argv[0] or /proc/self/exe, right?
> >
> > Eventually we should fix this and reinstate this commit, but reverting
> > it was the right thing in the short term.
>
> Here is a fix:
>
> From b7badcf695fcb245224ffdf51cdb016b45f9a2a5 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?=E5=AE=8B=E6=96=87=E6=AD=A6?= <iyzsong@gmail.com>
> Date: Sun, 16 Oct 2016 10:44:29 +0800
> Subject: [PATCH] gnu: wrap-python3: Use a bash wrapper for 'python3-config'.
>
> See <http://lists.gnu.org/archive/html/guix-devel/2016-07/msg00008.html>
> for details.
>
> * gnu/packages/python.scm (wrap-python3)[arguments]: Use a bash wrapper
> instead of a symlink for python3-config.
I can confirm that python-pycairo builds with this patch applied to
core-updates.
next prev parent reply other threads:[~2016-10-16 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 9:02 core-updates! Ludovic Courtès
2016-07-01 11:33 ` python-pycairo in core-updates (Re: core-updates!) 宋文武
2016-07-01 15:33 ` Andreas Enge
2016-07-01 21:06 ` Leo Famulari
2016-07-02 13:12 ` Ludovic Courtès
2016-10-16 3:21 ` [PATCH] gnu: wrap-python3: Use a bash wrapper for 'python3-config'. (was: python-pycairo in core-updates) 宋文武
2016-10-16 18:14 ` Leo Famulari [this message]
2016-10-17 10:58 ` [PATCH] gnu: wrap-python3: Use a bash wrapper for 'python3-config' 宋文武
2016-07-01 20:59 ` core-updates! Leo Famulari
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=20161016181407.GA5150@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.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 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.