Re: weird problem with macports perl on apple m1/m2 based system

Firstly, I don't have M1/M2 so can't do any testing.

One thing that did stand out for me was "use POSIX;". I don't suppose that has anything to do with your problem; however, this usage is strongly discouraged — see "POSIX: CAVEATS".

It's good that you're checking here before raising a bug report. Attendence is typically less on the weekends; I've front-paged your post to hopefully gain a wider audience.

— Ken

Comment on Re: weird problem with macports perl on apple m1/m2 based system Download Code

Replies are listed 'Best First'.
Re^2: weird problem with macports perl on apple m1/m2 based system by perltux (Monk) on Jun 10, 2023 at 23:15 UTC
Ok I found why I originally added "use POSIX", it was for the strftime function, therefore I will change that to "use POSIX qw(strftime)" in my application.	[reply]
Re^3: weird problem with macports perl on apple m1/m2 based system by Anonymous Monk on Jun 11, 2023 at 18:41 UTC
Off-topic to the original question, but relevant to `use POSIX`. Time::Piece provides equivalent functionality to `POSIX::strftime`, and has been core since 5.10.0. Read the docs carefully before using, though, because by default it replaces the core `gmtime()` and `localtime()` functions with ones that return an object if called in scalar context.	[reply] [d/l] [select]
Re^2: weird problem with macports perl on apple m1/m2 based system by perltux (Monk) on Jun 10, 2023 at 22:01 UTC
Thanks for the front-pageing and for the advice with regards to "use POSIX", I can't remember why I added that, there must have been a reason because I don't normally use that by default, but I will look into it again.	[reply]