MacPorts for 10.6 PowerPC with pre-built ports [unofficial]: testing welcomed

[barracuda156]

Fantastic to see the effort you’ve been putting into this is paying off @barracuda156! I will have a look at testing either tonight after I finish work or tomorrow hopefully. I’ll stick it on the upgraded Quicksilver.

I vaguely recall there could have been some issues with gnutls dependents.
That was due to incompatible libs API of gnutls vs gnutls-devel. Since I use the latter, it could have been broken with the former.

This is fixed in the latest update to the ports: I bumped gnutls version to the one compatible with gnutls-devel.
So now no related breakages are expected. I can switch locally between -devel and non-devel versions without causing a breakage.

I have uploaded new ports archive today with this and other updates and new packages.

 

[barracuda156]

[Guess no one is using this anyway, but] gcc-powerpc updated to the latest snapshot (gcc 15-20240901), all Pythons updated to the latest versions, some new pre-built ports added.

One may switch from gcc14 to gcc15 like this:

sudo port deactivate libgcc14 libgcc 
sudo port -v install libgcc-powerpc gcc-powerpc

Compilers can co-exist, runtime ports cannot (i.e. you can have both installed, but only one active: either standard libgcc14 with its wrapper libgcc port or libgcc-powerpc).
If someone builds MacPorts from source, you will need to borrow a few commits from my tree to be able to use this, since standard MacPorts won’t recognize gcc-powerpc as a legit name.

You could sort packages by date of being modified on macos-powerpc.org/packages to see what’s new and what has been updated recently.

There will probably be no major updates for some time, but there are about 10k+ ports available, all every-day needs should be covered (editors, e-mail, audio, multimedia, browser, discord client, photo processing etc.); there are also a lot of development tools, perhaps all compilers which could be supported (besides obvious C/C++/Fortran/Python/Perl we got Lisp, OCaml, Ruby, Scheme, Idris, Java, Algol, some older Haskell implementations etc.), various sorts of math software (R, maxima, octave, a lot of implementations of BLAS, theorem provers etc.), some science packages.

Some stuff is in WIP state, but likely gonna take a while (I hope to get X server updated to the latest version, fix some multimedia software and try doing something about Qt6; neither of these are expected too soon though).

Ping me for any bugs noticed.

One thing left is to add some instructions, that will be done next week.

 

[metallizer]

Got it working!

Been wanting to test it for a while. It's a quad that I solely used to build TFF, which is not necessary anymore with Aquafox around.

Thanks!

 

[barracuda156]

Got it working!

Been wanting to test it for a while. It's a quad that I solely used to build TFF, which is not necessary anymore with Aquafox around.

Thanks!

Great!

I will upload new archive for ports tomorrow. Currently what is actually available is several days ahead of what portfiles have.
I should force myself to update documentation also for all this LOL

There are some new ports added (build fine on powerpc):

lms | MacPorts

ports.macports.org

syslog-ng-devel | MacPorts

ports.macports.org

P. S. Try fastfetch, more output and some PPC fixes.

 

[barracuda156]

Got it working!

Been wanting to test it for a while. It's a quad that I solely used to build TFF, which is not necessary anymore with Aquafox around.

Thanks!

New ports tarball is up, a lot of updates.

(If something does not work, please ping me.

Also if something is really wanted but unavailable.)

 

[metallizer]

I ran sync and it all went smooth zero issues.

The only very minor issue that I'm having is that the export PATH command has to be issued in every terminal session to get macports working.

I'll have to open up this machine and clean up the ram sticks. It supposed to have 4 GB, had 3 in the previous printscreen and now is down to 2.

 

[barracuda156]

I ran sync and it all went smooth zero issues.

The only very minor issue that I'm having is that the export PATH command has to be issued in every terminal session to get macports working.

I'll have to open up this machine and clean up the ram sticks. It supposed to have 4 GB, had 3 in the previous printscreen and now is down to 2.

I am not sure how MacPorts does it automatically: in the documentation they in fact advise to set PATH in shell config manually when building MacPorts from source (which is what I have been doing myself always). That is only done once though, you do not need to export it every time (I only run export PATH when I want to hide MacPorts tree).

 

[barracuda156]

I am not sure how MacPorts does it automatically: in the documentation they in fact advise to set PATH in shell config manually when building MacPorts from source (which is what I have been doing myself always). That is only done once though, you do not need to export it every time (I only run export PATH when I want to hide MacPorts tree).

Perhaps post-install script, need to check it.

 

[Threaderr]

Ok, great. Thank you for checking this.

Now when you have time, I need two things to be checked:

1. Whether Qt4-based stuff works correctly (it should, but just in case). A good test will be to install QMPlay2 and try playing some video file (local one, YouTube works only via SMTube, not directly). The app will be in /Applications/MacPorts.

2. Whether X11 ports work. A bit more tricky, but I hope it will. What is needed here:
– wipe out Apple X11 (see above);
– install xorg-server-legacy, reboot the machine;
– install some X11 or GTK app, for example transmission-x11, try launching it.
If the app starts normally with GUI, that’s a success.

What extremely interesting timing on all this, i just put this up when i found it and it might be og use, i'll see during the weekend that the repo is completete and that i got everything. You could use XSDLXserver maybe? https://sourceforge.net/projects/li...XSDL/XServer-XSDL-1.20.51-src.tar.xz/download

Leaving ' my huge cache of old project files and half compiled mid working on whatever i was trying to do back then '
https://github.com/threader/xnu_gcc_libc_etc_darwin

I might see if i can boot 10.6.x of usb or something to test with when i get around to it. Cheers

 

[barracuda156]

You could use XSDLXserver maybe? https://sourceforge.net/projects/li...XSDL/XServer-XSDL-1.20.51-src.tar.xz/download

That appears to be some port of X11 for Android. What could we do with that?

X server works on macOS, including powerpc. In MacPorts install `xorg-server-legacy`.
(I could build a much newer version with some hacks, but it crashes on launch, and I had no time to get back to fixing it.)

I might see if i can boot 10.6.x of usb or something to test with when i get around to it. Cheers

That should work. At least works fine via FireWire.

 

[Threaderr]

That appears to be some port of X11 for Android. What could we do with that?

X server works on macOS, including powerpc. In MacPorts install `xorg-server-legacy`.
(I could build a much newer version with some hacks, but it crashes on launch, and I had no time to get back to fixing it.)



That should work. At least works fine via FireWire.

Just a quick reply while i read up: read trough the sources. It should build on linux, bsd, and something else, ive not built it in ages. I remembered the sources i had cloned for my github to work with i fell into doubt with. And im sure there was an SVN on sourceforge for that project. I'll need to read up.

I was reading trough the rest of the thread just now and saw that xorg-legacy was built after 'a day'. I'll have some time to read now and maybe even fire up a laptop, if not just for heating.

Edit:

xserver-xsdl/configure-xsdl.sh at xsdl2 · pelya/xserver-xsdl

XSDL - X.Org server ported to Android using SDL. Contribute to pelya/xserver-xsdl development by creating an account on GitHub.

github.com

It seems i built it two years ago

GitHub - threader/xserver-xsdl: XSDL - X.Org server using SDL.

XSDL - X.Org server using SDL. Contribute to threader/xserver-xsdl development by creating an account on GitHub.

github.com

 

[barracuda156]

Just a quick reply while i read up: read trough the sources. It should build on linux, bsd, and something else, ive not built it in ages. I remembered the sources i had cloned for my github to work with i fell into doubt with. And im sure there was an SVN on sourceforge for that project. I'll need to read up.

Ok, but what is the benefit of having it? While SDL2 works via X11, it does not work amazingly well. What do we get from having xserver-xsdl as compared to the existing and working xorg-server-legacy?

P. S. I mean, if you or someone is interested to add `xserver-xsdl` to MacPorts, that’s great, having options never hurts, but if you expect me to deal with this, I need to understand what is the supposed advantage of using it.

 

[Doq]

Okay, so correct me if this isn't right, but I believe this is not an implementation SDL on X, rather it's an implementation of X on SDL.

I don't know what the advantage is though. Speed? Compatibility?

 

[barracuda156]

Okay, so correct me if this isn't right, but I believe this is not an implementation SDL on X, rather it's an implementation of X on SDL.

I don't know what the advantage is though. Speed? Compatibility?

I get that, but SDL itself (as long as we talk about SDL2+) uses X11 and X server (because Cocoa has been broken since 2.0.3 or so). How this even gonna work, in fact?

 

[Threaderr]

I get that, but SDL itself (as long as we talk about SDL2+) uses X11 and X server (because Cocoa has been broken since 2.0.3 or so). How this even gonna work, in fact?

It's and X11 server running in SDL. So basically you get what the apple x11 already does, no hw accel and all that. The thought is compile and link against the osx libsdl.dylib . I've not done much testing here as i had questions about the sources, years ago, they contained hardlinks that would circle everywhere and all so i decided i need to check more but i still haven't dug up the sourceforge svn i was sure i spotted, years ago noting its origins/compatibility with bsd etc. Been busy with other stuff for a while. I'll get back to this as i get around to looking into it again. I've only built it twice and played with it a bit, read some docs and that too was years ago.

How i mostly use it, on android, is say, launch the XSDLXserver, jump to a Termux session and point to the x11 server running in the native android env.