From pengyu.ut at gmail.com Sat Jul 4 13:59:35 2020 From: pengyu.ut at gmail.com (Peng Yu) Date: Sat, 4 Jul 2020 12:59:35 -0500 Subject: [pypy-dev] How to install pypy3 on Mac OS X? Message-ID: Hi, I got the following erorr when I use pypy3 from homebrew. How to solve the problem? Should I use pypy3 independent of homebrew? If so, could anybody let me know how to do so? The download link only show Python 3.6, does it work for other versions of Python? Thanks. https://www.pypy.org/download.html $ pypy3 -mpip install -U JPype1 Collecting JPype1 Using cached JPype1-0.7.5.tar.gz (645 kB) Installing collected packages: JPype1 Running setup.py install for JPype1 ... error ERROR: Command errored out with exit status 1: command: /usr/local/bin/pypy3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/tmp/mktemp/pip-install-6pnf_iup/JPype1/setup.py'"'"'; __file__='"'"'/private/tmp/mktemp/pip-install-6pnf_iup/JPype1/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/tmp/mktemp/pip-record-594dwb7h/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/Cellar/pypy3/7.3.1_1/libexec/include/JPype1 cwd: /private/tmp/mktemp/pip-install-6pnf_iup/JPype1/ Complete output (61 lines): running install running build running build_py creating build creating build/lib.macosx-10.7-x86_64-3.6 creating build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jcollection.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_classpath.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jio.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_pykeywords.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jproxy.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_gui.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jmethod.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/nio.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jstring.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/__init__.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/types.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/beans.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jvmfinder.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/imports.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jcustomizer.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_core.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jinit.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jarray.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jobject.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/pickle.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jclass.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jexception.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/reflect.py -> build/lib.macosx-10.7-x86_64-3.6/jpype copying jpype/_jpackage.py -> build/lib.macosx-10.7-x86_64-3.6/jpype running build_ext running build_java Using Jar cache creating build/lib creating build/lib/org creating build/lib/org/jpype creating build/lib/org/jpype/classloader copying native/jars/org/jpype/classloader/JPypeClassLoader.class -> build/lib/org/jpype/classloader copying native/jars/org.jpype.jar -> build/lib running build_thunk Building thunks including thunk build/lib/org/jpype/classloader/JPypeClassLoader.class including thunk build/lib/org.jpype.jar Call build extensions Call build ext building '_jpype' extension creating build/temp.macosx-10.7-x86_64-3.6 creating build/temp.macosx-10.7-x86_64-3.6/build creating build/temp.macosx-10.7-x86_64-3.6/build/src creating build/temp.macosx-10.7-x86_64-3.6/native creating build/temp.macosx-10.7-x86_64-3.6/native/python creating build/temp.macosx-10.7-x86_64-3.6/native/common gcc -pthread -arch x86_64 -DNDEBUG -O2 -fPIC -DMACOSX=1 -Inative/common/include -Inative/python/include -Ibuild/src -Inative/jni_include -I/usr/local/Cellar/pypy3/7.3.1_1/libexec/include -c build/src/jp_thunk.cpp -o build/temp.macosx-10.7-x86_64-3.6/build/src/jp_thunk.o -g0 -std=c++11 -ggdb warning: include path for stdlibc++ headers not found; pass '-stdlib=libc++' on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found] In file included from build/src/jp_thunk.cpp:1: In file included from build/src/jp_thunk.h:3: native/common/include/jpype.h:64:10: fatal error: 'map' file not found #include ^~~~~ 1 warning and 1 error generated. error: command 'gcc' failed with exit status 1 ---------------------------------------- ERROR: Command errored out with exit status 1: /usr/local/bin/pypy3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/tmp/mktemp/pip-install-6pnf_iup/JPype1/setup.py'"'"'; __file__='"'"'/private/tmp/mktemp/pip-install-6pnf_iup/JPype1/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/tmp/mktemp/pip-record-594dwb7h/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/Cellar/pypy3/7.3.1_1/libexec/include/JPype1 Check the logs for full command output. -- Regards, Peng From matt at vazor.com Tue Jul 7 12:04:57 2020 From: matt at vazor.com (Matt Billenstein) Date: Tue, 7 Jul 2020 16:04:57 +0000 Subject: [pypy-dev] macos buildbot offline Message-ID: <010101732a05eb56-650f26d0-6b70-4f60-aee4-6394b9a61ce9-000000@us-west-2.amazonses.com> I won't have physical access to this machine until mid-August now, so it probably won't be available again until then. m From matti.picus at gmail.com Tue Jul 7 16:18:57 2020 From: matti.picus at gmail.com (Matti Picus) Date: Tue, 7 Jul 2020 23:18:57 +0300 Subject: [pypy-dev] macos buildbot offline In-Reply-To: <010101732a05eb56-650f26d0-6b70-4f60-aee4-6394b9a61ce9-000000@us-west-2.amazonses.com> References: <010101732a05eb56-650f26d0-6b70-4f60-aee4-6394b9a61ce9-000000@us-west-2.amazonses.com> Message-ID: ?On 7/7/20 7:04 PM, Matt Billenstein via pypy-dev wrote: > I won't have physical access to this machine until mid-August now, so it > probably won't be available again until then. > > m Thanks for the heads up. Anyone else on the list with a mac we can run buildbot on? Matti From matti.picus at gmail.com Tue Jul 7 17:24:42 2020 From: matti.picus at gmail.com (matti picus) Date: Wed, 8 Jul 2020 00:24:42 +0300 Subject: [pypy-dev] macos buildbot offline In-Reply-To: <1479E3BA-79A9-479A-BEE5-63558CE223A0@shurup.com> References: <1479E3BA-79A9-479A-BEE5-63558CE223A0@shurup.com> Message-ID: They need 6-8 GB of RAM in order to translate On Wed, 8 Jul 2020 at 00:06, Yury V. Zaytsev wrote: > Hmmm... I?ve got a couple of spare Mac Minis that maybe could fit the > bill, but I would be a bit hesitant to host them on my private line... > although not impossible. Anyone with some rack space and Ethernet port in > K?ln / Aachen? > > Sent from my iPad > > > On 7. Jul 2020, at 22:19, Matti Picus wrote: > > > > ? On 7/7/20 7:04 PM, Matt Billenstein via pypy-dev wrote: > >> I won't have physical access to this machine until mid-August now, so it > >> probably won't be available again until then. > >> > >> m > > > > > > Thanks for the heads up. Anyone else on the list with a mac we can run > buildbot on? > > > > Matti > > > > _______________________________________________ > > pypy-dev mailing list > > pypy-dev at python.org > > https://mail.python.org/mailman/listinfo/pypy-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yury at shurup.com Tue Jul 7 17:28:55 2020 From: yury at shurup.com (Yury V. Zaytsev) Date: Tue, 7 Jul 2020 23:28:55 +0200 Subject: [pypy-dev] macos buildbot offline In-Reply-To: References: Message-ID: They must have at least 8G - I can?t imagine them having less than that, but I can check tomorrow to be sure. Sent from my iPad > On 7. Jul 2020, at 23:25, matti picus wrote: > > ? > They need 6-8 GB of RAM in order to translate > >> On Wed, 8 Jul 2020 at 00:06, Yury V. Zaytsev wrote: >> Hmmm... I?ve got a couple of spare Mac Minis that maybe could fit the bill, but I would be a bit hesitant to host them on my private line... although not impossible. Anyone with some rack space and Ethernet port in K?ln / Aachen? >> >> Sent from my iPad >> >> > On 7. Jul 2020, at 22:19, Matti Picus wrote: >> > >> > ? On 7/7/20 7:04 PM, Matt Billenstein via pypy-dev wrote: >> >> I won't have physical access to this machine until mid-August now, so it >> >> probably won't be available again until then. >> >> >> >> m >> > >> > >> > Thanks for the heads up. Anyone else on the list with a mac we can run buildbot on? >> > >> > Matti >> > >> > _______________________________________________ >> > pypy-dev mailing list >> > pypy-dev at python.org >> > https://mail.python.org/mailman/listinfo/pypy-dev >> > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From yury at shurup.com Tue Jul 7 17:06:16 2020 From: yury at shurup.com (Yury V. Zaytsev) Date: Tue, 7 Jul 2020 23:06:16 +0200 Subject: [pypy-dev] macos buildbot offline In-Reply-To: References: Message-ID: <1479E3BA-79A9-479A-BEE5-63558CE223A0@shurup.com> Hmmm... I?ve got a couple of spare Mac Minis that maybe could fit the bill, but I would be a bit hesitant to host them on my private line... although not impossible. Anyone with some rack space and Ethernet port in K?ln / Aachen? Sent from my iPad > On 7. Jul 2020, at 22:19, Matti Picus wrote: > > ? On 7/7/20 7:04 PM, Matt Billenstein via pypy-dev wrote: >> I won't have physical access to this machine until mid-August now, so it >> probably won't be available again until then. >> >> m > > > Thanks for the heads up. Anyone else on the list with a mac we can run buildbot on? > > Matti > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev From yury at shurup.com Wed Jul 8 02:50:53 2020 From: yury at shurup.com (Yury V. Zaytsev) Date: Wed, 8 Jul 2020 08:50:53 +0200 (CEST) Subject: [pypy-dev] macos buildbot offline In-Reply-To: References: Message-ID: On Tue, 7 Jul 2020, Yury V. Zaytsev wrote: > They must have at least 8G - I can?t imagine them having less than that, > but I can check tomorrow to be sure. At least one that is currently in use has 8G - I would assume the others also have 8G. Would that work or you need 16G? How much does the current buildbot slave has? -- Sincerely yours, Yury V. Zaytsev From matti.picus at gmail.com Wed Jul 8 04:12:45 2020 From: matti.picus at gmail.com (Matti Picus) Date: Wed, 8 Jul 2020 11:12:45 +0300 Subject: [pypy-dev] macos buildbot offline In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From yury at shurup.com Wed Jul 8 04:47:48 2020 From: yury at shurup.com (Yury V. Zaytsev) Date: Wed, 8 Jul 2020 10:47:48 +0200 (CEST) Subject: [pypy-dev] macos buildbot offline In-Reply-To: References: Message-ID: On Wed, 8 Jul 2020, Matti Picus wrote: > I think 8GB is fine. Tell me when you would like to give it a shot. I > have no idea what version of macOS is the minimum needed. You can set it > up following > https://foss.heptapod.net/pypy/buildbot/-/blob/branch/default/README_BUILDSLAVE OK, I can check the other Mac Minis now and see if I can use that. I will have to reset machine to the latest version of Mac OS, whatever it is. So what about an Ethernet port nearby, maybe someone at HHU has something available? I can also cross the river to the enemy territory (D?sseldorf) - anything in 50km radius is OK... -- Sincerely yours, Yury V. Zaytsev From matt at vazor.com Wed Jul 8 13:09:32 2020 From: matt at vazor.com (Matt Billenstein) Date: Wed, 8 Jul 2020 17:09:32 +0000 Subject: [pypy-dev] macos buildbot offline In-Reply-To: References: Message-ID: <010101732f67665f-9c490374-3975-49d0-bceb-ce573f53854e-000000@us-west-2.amazonses.com> On Wed, Jul 08, 2020 at 11:12:45AM +0300, Matti Picus wrote: > I think 8GB is fine. Tell me when you would like to give it a shot. I have no > idea what version of macOS is the minimum needed. You can set it up following > https://foss.heptapod.net/pypy/buildbot/-/blob/branch/default/README_BUILDSLAVE Here's the script I use to bootstrap the worker - note a few requirements in homebrew in the comments: https://gist.github.com/mattbillenstein/944a1ce60e8522405ecd014f651fe21c m -- Matt Billenstein matt at vazor.com http://www.vazor.com/ From yury at shurup.com Wed Jul 8 16:39:10 2020 From: yury at shurup.com (Yury V. Zaytsev) Date: Wed, 8 Jul 2020 22:39:10 +0200 (CEST) Subject: [pypy-dev] macos buildbot offline In-Reply-To: <010101732f67665f-9c490374-3975-49d0-bceb-ce573f53854e-000000@us-west-2.amazonses.com> References: <010101732f67665f-9c490374-3975-49d0-bceb-ce573f53854e-000000@us-west-2.amazonses.com> Message-ID: On Wed, 8 Jul 2020, Matt Billenstein wrote: > On Wed, Jul 08, 2020 at 11:12:45AM +0300, Matti Picus wrote: >> I think 8GB is fine. Tell me when you would like to give it a shot. I have no >> idea what version of macOS is the minimum needed. You can set it up following >> https://foss.heptapod.net/pypy/buildbot/-/blob/branch/default/README_BUILDSLAVE > > Here's the script I use to bootstrap the worker - note a few requirements in > homebrew in the comments: > > https://gist.github.com/mattbillenstein/944a1ce60e8522405ecd014f651fe21c Oh man, mac life is hard... just bricked one mini, trying to erase the hard drive and reinstall the OS :-/ Apparently something went wrong during the erase, and now everything including El Capitan panics upon booting the installer, probably due to a kernel bug in com.apple.driver.CoreStorage, which leads to the meltdown due to this particular evil type of disk corruption. I wonder which options do I have other than taking the thing apart and zeroeing the hard drive with Linux - just odered a Thunderbolt cable - maybe I could get to the drive using Target Disk mode and zero it without getting it out of the machine... Gonna try my luck with another mini tomorrow. -- Sincerely yours, Yury V. Zaytsev From matt at vazor.com Wed Jul 8 18:18:39 2020 From: matt at vazor.com (matt at vazor.com) Date: Wed, 8 Jul 2020 22:18:39 +0000 Subject: [pypy-dev] macos buildbot offline In-Reply-To: References: Message-ID: <01010173308268f3-fc487bfc-5067-4c73-82d0-5cd6a92d5996-000000@us-west-2.amazonses.com> Boot from a usb installer image and you can clear the disk and install to it. M -- Matt Billenstein matt at vazor.com > On Jul 8, 2020, at 2:18 PM, Yury V. Zaytsev wrote: > > ?On Wed, 8 Jul 2020, Matt Billenstein wrote: > >>> On Wed, Jul 08, 2020 at 11:12:45AM +0300, Matti Picus wrote: >>> I think 8GB is fine. Tell me when you would like to give it a shot. I have no >>> idea what version of macOS is the minimum needed. You can set it up following >>> https://foss.heptapod.net/pypy/buildbot/-/blob/branch/default/README_BUILDSLAVE >> >> Here's the script I use to bootstrap the worker - note a few requirements in >> homebrew in the comments: >> >> https://gist.github.com/mattbillenstein/944a1ce60e8522405ecd014f651fe21c > > Oh man, mac life is hard... just bricked one mini, trying to erase the hard drive and reinstall the OS :-/ > > Apparently something went wrong during the erase, and now everything including El Capitan panics upon booting the installer, probably due to a kernel bug in com.apple.driver.CoreStorage, which leads to the meltdown due to this particular evil type of disk corruption. > > I wonder which options do I have other than taking the thing apart and zeroeing the hard drive with Linux - just odered a Thunderbolt cable - maybe I could get to the drive using Target Disk mode and zero it without getting it out of the machine... > > Gonna try my luck with another mini tomorrow. > > -- > Sincerely yours, > Yury V. Zaytsev From yury at shurup.com Thu Jul 9 02:13:54 2020 From: yury at shurup.com (Yury V. Zaytsev) Date: Thu, 9 Jul 2020 08:13:54 +0200 (CEST) Subject: [pypy-dev] macos buildbot offline In-Reply-To: <01010173308268f3-fc487bfc-5067-4c73-82d0-5cd6a92d5996-000000@us-west-2.amazonses.com> References: <01010173308268f3-fc487bfc-5067-4c73-82d0-5cd6a92d5996-000000@us-west-2.amazonses.com> Message-ID: On Wed, 8 Jul 2020, matt at vazor.com wrote: > Boot from a usb installer image and you can clear the disk and install > to it. Of course, I've tried that already with an USB installer for Catalina (APFS support) and El Capitan (pre-APFS) - both installers panic on boot while probing local hardware because as soon as they find the disk and try to read the partition table something goes kaboom. Internet Recovery leads to the same results, because basically it's just another delivery way for the installer, but as soon as it starts booting were're at square one. Is there some way to zero the first blocks of the drive from EFI :) ? Like in the old good days when Sun still shined, I could enter OpenBoot by pressing the magic "Stop-A" button and enter the Forth interpreter to do stuff like that... -- Sincerely yours, Yury V. Zaytsev From matt at vazor.com Thu Jul 9 11:18:48 2020 From: matt at vazor.com (matt at vazor.com) Date: Thu, 9 Jul 2020 15:18:48 +0000 Subject: [pypy-dev] macos buildbot offline In-Reply-To: References: Message-ID: <010101733428603c-ff809329-e945-4c50-9310-048bdc66a78c-000000@us-west-2.amazonses.com> I?d try to boot something like the ubuntu installer and use dd... My oldest macbook pro stopped taking macos updates, so it runs ubuntu now - but i forget which installer image used to do that. M -- Matt Billenstein matt at vazor.com > On Jul 8, 2020, at 11:14 PM, Yury V. Zaytsev wrote: > > ?On Wed, 8 Jul 2020, matt at vazor.com wrote: > >> Boot from a usb installer image and you can clear the disk and install to it. > > Of course, I've tried that already with an USB installer for Catalina (APFS support) and El Capitan (pre-APFS) - both installers panic on boot while probing local hardware because as soon as they find the disk and try to read the partition table something goes kaboom. > > Internet Recovery leads to the same results, because basically it's just another delivery way for the installer, but as soon as it starts booting were're at square one. > > Is there some way to zero the first blocks of the drive from EFI :) ? Like in the old good days when Sun still shined, I could enter OpenBoot by pressing the magic "Stop-A" button and enter the Forth interpreter to do stuff like that... > > -- > Sincerely yours, > Yury V. Zaytsev From yury at shurup.com Fri Jul 10 17:50:28 2020 From: yury at shurup.com (Yury V. Zaytsev) Date: Fri, 10 Jul 2020 23:50:28 +0200 (CEST) Subject: [pypy-dev] macos buildbot offline In-Reply-To: <010101733428603c-ff809329-e945-4c50-9310-048bdc66a78c-000000@us-west-2.amazonses.com> References: <010101733428603c-ff809329-e945-4c50-9310-048bdc66a78c-000000@us-west-2.amazonses.com> Message-ID: Hey Matt, Awesome, it worked! Ubuntu 20.04 booted without skipping a beat and after zeroing the disk, Catalina installer was able to recreate the Fusion Drive and install the OS. Will try to see if I can get it set up as a buildbot slave according the the instructions you that you've posted earlier... -- Sincerely yours, Yury V. Zaytsev