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/issues/3240 which only requires
> devop-level python skills to fix. Help is welcome.
I've made some progress on this
$ otool -L bin/libpypy3-c.dylib
bin/libpypy3-c.dylib:
@rpath/libpypy3-c.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libutil.dylib (compatibility version 1.0.0, current version 1.0.0)
@rpath/libintl.8.dylib (compatibility version 10.0.0, current version
10.7.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
1281.100.1)
@rpath/libexpat.1.dylib (compatibility version 7.0.0, current version 8.0.0)
@rpath/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5)
@rpath/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
@rpath/libffi.dylib (compatibility version 1.0.0, current version 26.0.0)
@rpath/libncurses.5.4.dylib (compatibility version 5.4.0, current version
5.4.0)
$ DYLD_PRINT_LIBRARIES=1 bin/pypy3 -c '1' 2>&1 | egrep 'expat|ffi'
dyld: loaded: <1ED53818-578C-3D17-8761-68792CCAD685>
/private/tmp/usession-unknown-35/build/mattb/bin/../lib/libexpat.1.dylib
dyld: loaded: <2AACAE86-FCF4-3613-89A4-5F822BD92AA9>
/private/tmp/usession-unknown-35/build/mattb/bin/../lib/libffi.dylib
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
--
Matt Billenstein
m...@vazor.com
http://www.vazor.com/
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
