From: Arun Isaac <arunisaac@systemreboot.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>,
27003@debbugs.gnu.org
Subject: bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python.
Date: Sun, 28 May 2017 00:34:32 +0530 [thread overview]
Message-ID: <2703649c.AEUAKjf8hTsAAAAAAAAAAAPFd4YAAAACwQwAAAAAAAW9WABZKc3G@mailjet.com> (raw)
In-Reply-To: <87pof35lc6.fsf@fastmail.com>
>> It implements a general `wrap` phase that can be used in individual build
>> systems to make sure binaries in those languages have access to all their
>> propagated inputs at runtime, by setting an appropriate environment variable.
>
> CCing Arun who was working on something similar.
I haven't actually worked on this problem for a long while. I'll test
Alex's patches, and get back to you soon.
> AFAICT this is also subject to <https://bugs.gnu.org/25235>. Can you
> have a look at it?
Yes, that's the python wrap phase bug report. And this is the one for
perl: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26275
next prev parent reply other threads:[~2017-05-27 19:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 9:37 bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python Alex Sassmannshausen
2017-05-20 9:40 ` bug#27003: [PATCH 1/3] build/utils: Add 'program-wrapper' Alex Sassmannshausen
2017-05-20 9:40 ` bug#27003: [PATCH 2/3] build/perl-build-system: Add 'wrap' phase Alex Sassmannshausen
2017-05-20 9:40 ` bug#27003: [PATCH 3/3] build/python-build-system: Refactor 'wrap' Alex Sassmannshausen
2017-05-20 20:23 ` bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python Marius Bakke
2017-05-27 19:04 ` Arun Isaac [this message]
2017-05-28 19:08 ` Arun Isaac
2017-05-29 13:45 ` Alex Sassmannshausen
2017-05-30 13:45 ` Arun Isaac
[not found] ` <ef869600.AEMAK2iO_jkAAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZLXea@mailjet.com>
2017-05-30 15:17 ` Marius Bakke
2020-03-21 14:23 ` Brice Waegeneire
2020-03-21 16:32 ` Ludovic Courtès
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=2703649c.AEUAKjf8hTsAAAAAAAAAAAPFd4YAAAACwQwAAAAAAAW9WABZKc3G@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=27003@debbugs.gnu.org \
--cc=alex.sassmannshausen@gmail.com \
--cc=mbakke@fastmail.com \
/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.