On 6/2/20 1:46 AM, Matt Billenstein wrote:
I've made some progress on this
...
thx
m
Just to follow up here: thanks to Matt we have a "portable build"
candidate available here http://buildbot.pypy.org/nightly/issue3240 It
would be nice if someone who could not use the 7.3.1 release tarbal
On 6/2/20 1:46 AM, Matt Billenstein wrote:
Trying to commit changes to make_portable.py -- I cloned the pypy repo, but
getting stuck at 'hg topic issue3240' -- do I need a newer version of mercurial
or something?
thx
m
You need to install the "topic" extension:
https://heptapod.net/pages/
On Mon, Jun 01, 2020 at 08:49:29AM +0300, Matti Picus wrote:
> I think porting the current make_portable to macOS would not be so
> terrible. Since most of the work has been done for linux64/linux32, it is
> "just" a matter of adjusting the workflow. I opened
> https://foss.heptapod.net/pypy/pypy/i
On 6/1/20 12:39 AM, Yury V. Zaytsev wrote:
On Sun, 31 May 2020, Matt Billenstein via pypy-dev wrote:
I think if you want to ship portable binary packages, they should be
self-contained - you can't really know what Apple is going to include
or remove from release to release.
I think this pri
Attempting a custom build outside of the buildbot and I'm linking system
libffi, but it's not picking up gettext out of /usr/local - is there any way to
tell the toolchain to not link anything in /usr/local?
$ otool -L libpypy3-c.dylib
libpypy3-c.dylib:
@rpath/libpypy3-c.dylib (compatibility v
On Sun, May 31, 2020 at 11:39:31PM +0200, Yury V. Zaytsev wrote:
> On Sun, 31 May 2020, Matt Billenstein via pypy-dev wrote:
>
> > I think if you want to ship portable binary packages, they should be
> > self-contained - you can't really know what Apple is going to include or
> > remove from relea
On Sun, 31 May 2020, Matt Billenstein via pypy-dev wrote:
I think if you want to ship portable binary packages, they should be
self-contained - you can't really know what Apple is going to include or
remove from release to release.
I think this principle holds on the various Linux distros as
On Sun, May 31, 2020 at 01:09:11AM +0300, Matti Picus wrote:
> It seems the pypy 7.3.1 tarball is broken on macOS since it links to an
> installation of libffi in the non-standard location
> `/usr/local/opt/libffi/lib/
> libffi.6.dylib`, see issue 3229[0].
I'm going to remove the homebrew ffi fro
On Sun, 31 May 2020, Matti Picus wrote:
This is due to macOS 10.15.3 not shipping its own libffi (is this
true?), so the buildbot owner (CC) had to install it via homebrew. I
don't know anything about macOS:
It still seems to be included with the Command Line Tools, which can be
installed us
It seems the pypy 7.3.1 tarball is broken on macOS since it links
to an installation of libffi in the non-standard location
`/usr/local/opt/libffi/lib/libffi.6.dylib`, see issue 3229[0].
This is due to macOS 10.15.3 not
shipping its own libffi (is this tru
10 matches
Mail list logo
