On Mon, Sep 23, 2019 at 04:50:23PM +0100, Edd Barrett wrote:
> On Sun, Sep 22, 2019 at 10:05:24PM +0200, Klemens Nanni wrote:
> > No PLIST change with the following diff, *if* I run update-plist with
> > UPDATE_PLIST_ARGS='-i MODPY_PY_PREFIX -i MODPY_PY0EXTENSION -i
> > MODPY_VERSION'
> > to escap
On Sun, Sep 22, 2019 at 10:05:24PM +0200, Klemens Nanni wrote:
> No PLIST change with the following diff, *if* I run update-plist with
> UPDATE_PLIST_ARGS='-i MODPY_PY_PREFIX -i MODPY_PY0EXTENSION -i MODPY_VERSION'
> to escape the massive churn.
Will I have to remember to set those args every time
On Sun, Sep 22, 2019 at 03:05:03PM +0100, Stuart Henderson wrote:
> ${PREFIX}/pypy/bin/pypy -m compileall ${PREFIX}/pypy/lib-python/2.7
Just that won't do because it'll fail with SyntaxErrors and what-not on
test files, but as of https://docs.python.org/2/library/compileall.html
there's `-x regex'
On Sun, Sep 22, 2019 at 03:05:03PM +0100, Stuart Henderson wrote:
> ${PREFIX}/pypy/bin/pypy -m compileall ${PREFIX}/pypy/lib-python/2.7
>
> but I know if I try a test build now it will make my workstation
> unusable for hours+ and I don't really want to tie it up atm :-)
I'll try that, thanks.
On 2019/09/22 15:37, Klemens Nanni wrote:
> On Sun, Sep 22, 2019 at 02:23:14PM +0200, Klemens Nanni wrote:
> > The bootstrap target uses xz(1) so add it as BDEP.
> sthen pointed out it's already there; indeed BOOTSTRAP-amd64 implicitly
> does by having the .xz extension.
>
> > Also use find(1)'s
On Sun, Sep 22, 2019 at 02:23:14PM +0200, Klemens Nanni wrote:
> The bootstrap target uses xz(1) so add it as BDEP.
sthen pointed out it's already there; indeed BOOTSTRAP-amd64 implicitly
does by having the .xz extension.
> Also use find(1)'s -delete and -exec commands and move variables before
>
The bootstrap target uses xz(1) so add it as BDEP.
Also use find(1)'s -delete and -exec commands and move variables before
targets while here.
OK?
Index: Makefile
===
RCS file: /cvs/ports/lang/pypy/Makefile,v
retrieving revision 1.3
