Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac version after 2.200 not working with error "Attempt to reload DynaLoader.pm aborted." #428

Open
KingKarlo opened this issue Dec 9, 2023 · 6 comments
Assignees

Comments

@KingKarlo
Copy link

Hi, the Mac version was running fine until 2.200.

If I try to run a version after that (2.229 or 2.264, imapsync_bin_Darwin_x86_64) with the same command, I get the following error messages:

Attempt to reload DynaLoader.pm aborted.
Compilation failed in require at /XSLoader.pm line 118.
Compilation failed in require at /IO/Handle.pm line 268.
BEGIN failed--compilation aborted at /IO/Handle.pm line 268.
Compilation failed in require at /IO/Seekable.pm line 100.
BEGIN failed--compilation aborted at /IO/Seekable.pm line 100.
Compilation failed in require at /IO/File.pm line 132.
BEGIN failed--compilation aborted at /IO/File.pm line 132.
Compilation failed in require at -e line 154.

I'm running the latest Sonoma version on a M1 Mac. Anything I'm missing?

@gilleslamiral
Copy link
Member

Hi KingKarlo

Does the 2.200 run well on your latest Sonoma version on a M1 Mac?

Some context: I'm not good at Mac

@KingKarlo
Copy link
Author

Hi Gilles,

Yes, it runs perfectly. The error started with 2.229.

I did some research before posting here to not look too stupid for missing something, but couldn't figure it out. Most errors I've found are on Linux, related to missing Perl modules. But I couldn't figure out how that relates to my specific error.

Did some modules/binary/etc. requirements change significantly from 2.220 to 2.229?

Maybe it's just unique to my installation. Otherwise, you might have heard from other Mac users already.

Happy to provide you with any additional information you might need.

@gilleslamiral
Copy link
Member

Which binary do you use?

@KingKarlo
Copy link
Author

imapsync_bin_Darwin_x86_64

The i386 isn't working due to the M1 CPU "bad CPU type in executable: ./imapsync_bin_Darwin_i386"

@gilleslamiral
Copy link
Member

gilleslamiral commented Dec 14, 2023

Effectively, the binaries are not the same type:

# 2.200
gilles@petite:~/public_html/prepa_dist/imapsync-2.200 7$ file imapsync_bin_Darwin
imapsync_bin_Darwin: Mach-O universal binary with 2 architectures: [x86_64: Mach-O 64-bit x86_64 executable] [i386] []
# 2.264
gilles@petite:~/public_html/prepa_dist/imapsync-2.264 12$ file imapsync_bin_Darwin*
imapsync_bin_Darwin_i386:   Mach-O i386 executable
imapsync_bin_Darwin_x86_64: Mach-O 64-bit x86_64 executable

But I don't know how I built the first one differently. I use the same commands.
But I somehow remember an upgrade from the host that I use to build the binaries.

I'll try to find out how to build multi-arch binaries

The old releases are usually good enough anyway.

@KingKarlo
Copy link
Author

Thank you, Gilles, for looking into it!

Yes, truly agree, the old releases are more than good enough. It was more me wondering if I'm doing something wrong.

Please let me know in case I can provide any additional information or if I should test something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants