Leo Famulari <l...@famulari.name> writes:

> 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?= <iyzs...@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.

Pushed, thanks for the confirming :-)

Reply via email to