|laziness, impatience, and hubris
Re^7: weird problem with macports perl on apple m1/m2 based systemby perltux (Monk)
|on Jun 17, 2023 at 05:21 UTC
Rob, I really appreciate your effort but the problem is that as I said before I do not have direct access to the problem machine.
I had started this thread with the hope that among the many Perl experts here on Perlmonks there would be somebody using a M1/M2 Mac with MacPorts Perl who could run my test script and confirm or disprove the issue so that in case the issue is confirmed I could then open a bug report at macports.
What you are suggesting is more back and forth between me and the user of my application which is exactly what I wanted to avoid as I feel I'm straining his willingness to help.
Before asking the user of my application to test any further variants of the test script (which certainly would make sense to narrow down further the root cause) I first of all need confirmation that my test script included in the first post of this thread does trigger the issue also on other M1/M2 Macs, i.e. that it's not a unique issue with his particular setup.
I'm starting to realize that it was a bad idea to add macOS (or at least macOS on ARM cpus, for macOS on Intel I can set up a hackintosh if necessary) to the supported platforms for my application, as I have no way to reproduce any platform related issues. I was naive in thinking that since macOS is Unix based Perl would work just the same as on Linux, but apparently that's not really the case.