Support older macOS (including PowerPC systems) [upd: it works now] #153
Replies: 12 comments 19 replies
-
I saw you added a port for nmail in MacPorts - thanks btw! - so I guess you already got your answer w.r.t. the current state. I tried setting up To answer the question - I don't mind fixing nmail to build for those version (assuming it can be addressed within nmail code base and with reasonable effort) - but yeah they would not be officially supported nor tested on ongoing basis.. |
Beta Was this translation helpful? Give feedback.
-
@d99kris Yeah, I have to rely on buildbots at the moment (but I will be back to my testing hardware in a week or so), so cannot check for PowerPC, but overall it looks very good, and given that on 10.6–10.7 build fails only at linking due to a non-existing framework (CFNetwork introduced in 10.8), chances are high
I install Macports from source normally, that should work fine. I never tried to install Lion, but I have 10.4.11, 10.5.8, 10.6, 10.6.8 and 10.8.5, the latter two in Parallels, and source installation works reliably, AFAICT. You can also set Macports in a way to use a modern
Unless you build for Rosetta, just running Let me know if building from source works. (If something still fails, we can find a solution, I hope.)
That would be awesome! Once I am back to my machines, I can test on PowerPC too. |
Beta Was this translation helpful? Give feedback.
-
@d99kris Could you refer me to the config for macOS 10.6 for UTM, if you have it installed? If that works on Apple Silicon, I will see what is going on with Macports installation and whether everything works as expected. |
Beta Was this translation helpful? Give feedback.
-
@d99kris On 10.5 we get this error (not my log, I just requested someone to try it):
Looks like |
Beta Was this translation helpful? Give feedback.
-
@d99kris Update re build on 10.5. In essence, if fixing What is left to be addressed is It fails only at linking:
|
Beta Was this translation helpful? Give feedback.
-
@d99kris There is a single file which explicitly uses nmail/ext/libetpan/src/data-types/mailstream_cfstream.c Lines 34 to 43 in 6d85323 nmail/ext/libetpan/src/data-types/mailstream_cfstream.c Lines 500 to 508 in 6d85323
Tbh, I do not see anything in the build to define |
Beta Was this translation helpful? Give feedback.
-
@d99kris It could be that indeed we break the build merely by forcing the non-existent framework linkage. |
Beta Was this translation helpful? Give feedback.
-
@d99kris Well, I can confirm that
. . .
|
Beta Was this translation helpful? Give feedback.
-
Very nice 👍 Assuming |
Beta Was this translation helpful? Give feedback.
-
Thanks again for the PR to make the Regarding As for my OS X Lion system, I finally managed to use MacPorts and install nmail using it - very neat. 👍 I wasn't able to get Xcode fully installed, but it wasn't needed. It turns out the MacPorts installer (used
Sync:
And install nmail:
Edit: FYI - I've updated the README in f44803e with the above command for installing using MacPorts, hope it's correct. |
Beta Was this translation helpful? Give feedback.
-
@d99kris We need one more fix for PowerPC systems: what we have builds fine but does not work.
P. S. This is not an arch issue, I think, but a consequence of duplicate |
Beta Was this translation helpful? Give feedback.
-
@d99kris Did not yet set Gmail account to work with |
Beta Was this translation helpful? Give feedback.
-
@d99kris Could you say if older macOS versions may potentially be supported? Without any commitment to an ongoing support, of course.
README mentions only Sonoma, but from dependencies list it looks like this may build back to 10.4/10.5. However I have no idea if there are any core features relying on newer SDKs (and if yes, then whether those could be given fallbacks not requiring newer SDKs).
Specifically, I am interested in 10.5–10.6 on PowerPC (but if that works, anything newer on Intel can be made to work as well).
Beta Was this translation helpful? Give feedback.
All reactions