I think there is no issues with installing pre-built ports. Works normally for me on a new installation with no tweaks to config.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MacPorts for 10.6 PowerPC with pre-built ports [unofficial]: testing welcomed
- Thread starter barracuda156
- Start date
-
- Tags
- macports powerpc snowleopard
- Sort by reaction score
Getting closer
port -v -b install utdns
---> Fetching archive for utdns
---> utdns-1.2_0.darwin_10.ppc.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
---> Attempting to fetch utdns-1.2_0.darwin_10.ppc.tbz2 from http://macos-powerpc.org/packages/utdns
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 10202 100 10202 0 0 13584 0 --:--:-- --:--:-- --:--:-- 13584
---> Attempting to fetch utdns-1.2_0.darwin_10.ppc.tbz2.rmd160 from http://macos-powerpc.org/packages/utdns
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 0 0 740 0 --:--:-- --:--:-- --:--:-- 739
Warning: Failed to verify signature for archive!
Error: Failed to archivefetch utdns: version @1.2_0
Getting closer
port -v -b install utdns
---> Fetching archive for utdns
---> utdns-1.2_0.darwin_10.ppc.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
---> Attempting to fetch utdns-1.2_0.darwin_10.ppc.tbz2 from http://macos-powerpc.org/packages/utdns
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 10202 100 10202 0 0 13584 0 --:--:-- --:--:-- --:--:-- 13584
---> Attempting to fetch utdns-1.2_0.darwin_10.ppc.tbz2.rmd160 from http://macos-powerpc.org/packages/utdns
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 0 0 740 0 --:--:-- --:--:-- --:--:-- 739
Warning: Failed to verify signature for archive!
Error: Failed to archivefetch utdns: version @1.2_0
I guess you either do not have the pem key in /opt/local/etc/macports/pubkeys.conf (path to it) or the key file in a location which is pointed to.
This may happen if you had MacPorts conf files before installing my version. I think MacPorts does not overwrite existing configs.
This is the assumed path: /opt/local/share/macports/macos-powerpc-pubkey.pem
I hope the file itself gets installed anyway, so the problem is likely with the pubkeys.conf.
I will add this to instructions later, but just in case so that these are not forgotten, some – rather random – notes:
0. Installing PPCPorts / MacPorts from a pkg does port sync with indexing in the end of the installation. This is not an optimal way to do it, honestly, but until I hack the script, it is like that. On a slow G4 that gonna take hours. (This is not a waste of time, since port sync is a required step for the thing to be usable, it is just silly that it is done in a voodoo manner without any sensible output.)
1. xorg-server-legacy works but requires reboot upon installation and may take time starting up. Do not immediately kill the app; once reboot has been done, it is supposed to be functional. (I use FileZilla to upload files to the server, and FileZilla app cannot start without xorg-server, so I know for the fact that it works.)
2. For Qt4: please install qt4-mac-devel, not the regular port. For now at least.
3. I am dropping pre-historic gcc, old pythons, rubies and perls and advise doing the same. Recommended versions are:
– gcc14 (gcc10-bootstrap will be installed as a requirement, other versions are unneeded, avoid them);
– perl5.34 (default one atm);
– python310+ (unless a specific port requires an older one);
– ruby31+
4. KDE has been semi-broken on 10a190 and currently untested on 10.6.8. I will give it a try when I have time to waste, but unless you really need something from it, just don’t bother with it for now.
5. For video: the best option is QMPlay2. VLC, mpv and mplayer are a waste of time.
6. I disabled the old archive of 10a190 packages by default; if wanted, add it to archives.conf: https://macos-powerpc.org/packages_legacy (it has a lot more stuff, but w/e is available in the new one is to be preferred on 10.6.8).
0. Installing PPCPorts / MacPorts from a pkg does port sync with indexing in the end of the installation. This is not an optimal way to do it, honestly, but until I hack the script, it is like that. On a slow G4 that gonna take hours. (This is not a waste of time, since port sync is a required step for the thing to be usable, it is just silly that it is done in a voodoo manner without any sensible output.)
1. xorg-server-legacy works but requires reboot upon installation and may take time starting up. Do not immediately kill the app; once reboot has been done, it is supposed to be functional. (I use FileZilla to upload files to the server, and FileZilla app cannot start without xorg-server, so I know for the fact that it works.)
2. For Qt4: please install qt4-mac-devel, not the regular port. For now at least.
3. I am dropping pre-historic gcc, old pythons, rubies and perls and advise doing the same. Recommended versions are:
– gcc14 (gcc10-bootstrap will be installed as a requirement, other versions are unneeded, avoid them);
– perl5.34 (default one atm);
– python310+ (unless a specific port requires an older one);
– ruby31+
4. KDE has been semi-broken on 10a190 and currently untested on 10.6.8. I will give it a try when I have time to waste, but unless you really need something from it, just don’t bother with it for now.
5. For video: the best option is QMPlay2. VLC, mpv and mplayer are a waste of time.
6. I disabled the old archive of 10a190 packages by default; if wanted, add it to archives.conf: https://macos-powerpc.org/packages_legacy (it has a lot more stuff, but w/e is available in the new one is to be preferred on 10.6.8).
I did not find a convenient and streamlined way to make ports sources tarball. What I was doing until now was convenient, however GitHub resets mtime of files when checking out a branch etc. This triggeres port reindexing, and that is a huge time waste.
Any opinions re using two sources repos, mine as an override (for changed ports) plus official for everything else? This is what MacStrop does and this is how it is usually being set locally (myself I use an overlay repo above MacPorts upstream one).
I initially decided to use a single source which combines both into one, which was supposed to be simpler and ensured that users do not get random breakages from MacPorts upstream. However that also means that users do to get fixes from there on time either, and updates will be systemically delayed.
I probably can avoid all this mtime indexing hell by simply supplying only my ports and portgroups, and then you have standard MacPorts for everything else. Initial sync still gonna take forever, but once that done, it should work smoothly.
It will also make easier to remove my overlay ports at any moment, temporarily or permanently, and use standard ports, since both sources are set up and index exists.
How about that?
Any opinions re using two sources repos, mine as an override (for changed ports) plus official for everything else? This is what MacStrop does and this is how it is usually being set locally (myself I use an overlay repo above MacPorts upstream one).
I initially decided to use a single source which combines both into one, which was supposed to be simpler and ensured that users do not get random breakages from MacPorts upstream. However that also means that users do to get fixes from there on time either, and updates will be systemically delayed.
I probably can avoid all this mtime indexing hell by simply supplying only my ports and portgroups, and then you have standard MacPorts for everything else. Initial sync still gonna take forever, but once that done, it should work smoothly.
It will also make easier to remove my overlay ports at any moment, temporarily or permanently, and use standard ports, since both sources are set up and index exists.
How about that?
It is clearly evidenced across the internet, your continued efforts to engage upstream developers and maintainers to support the Mac PowerPC platform on behalf of all of us in this community.
This is admirable but also it’s clear that many of those projects simply refuse to be supportive, even when you’ve demonstrated that minimal changes are required to continue to support our old hardware in some cases. Most fixes and patches will not be upstreamed.
It seems to me that as you have taken on the burden of maintaining 3rd party port support for Mac PowerPC, without reward and little support, the decision on which path to take moving forward should be ‘whichever path has the least maintenance burden’ for yourself.
I think as time goes on your PowerPC ports tree and MacPorts upstream will continue to diverge and more PowerPc users will switch from stock MacPorts to the only Ports fork that actually still supports them.
This is admirable but also it’s clear that many of those projects simply refuse to be supportive, even when you’ve demonstrated that minimal changes are required to continue to support our old hardware in some cases. Most fixes and patches will not be upstreamed.
It seems to me that as you have taken on the burden of maintaining 3rd party port support for Mac PowerPC, without reward and little support, the decision on which path to take moving forward should be ‘whichever path has the least maintenance burden’ for yourself.
I think as time goes on your PowerPC ports tree and MacPorts upstream will continue to diverge and more PowerPc users will switch from stock MacPorts to the only Ports fork that actually still supports them.
You were correct. The path to the pubkey for your repository was in default file but not the conf file. I added it to the conf file and it works now. I was also able to get my ethernet speed working at 100MB by disabling autonegotiation. Got utdns starting as a launchdaemon and am upgrading all of my existing ports now. Hopefully most from binary packages
You were correct. The path to the pubkey for your repository was in default file but not the conf file. I added it to the conf file and it works now. I was also able to get my ethernet speed working at 100MB by disabling autonegotiation. Got utdns starting as a launchdaemon and am upgrading all of my existing ports now. Hopefully most from binary packages
Make sure you have noticed Qt4 point above. If you just install something which uses Qt4, it will pull in a regular port, which a) will build from source, since it is not in the archive, and b) may not be compatible with dependents (untested, as of now; it is known that “official” port with “official” portgroups are not fully compatible, at least in some cases).
(I mean, nothing horrible happens if you ignore this, you may just end up having to reinstall a few Qt4 ports.)
Sure enough, I prefer to avoid doing avoidable work here, since there are more things in a pipeline to fix, but at the same time it will be pointless to settle on a solution which 0 people find acceptable besides myself )
Lumme think through again today; I tend to prefer a way to keep stuff more up-to-date (not only with MacPorts upstream but also with my own fixes, so that I can pick them on another machine automatically), but it will be good to have a stable fallback if something gets broken in the upstream.
P. S. I had some concerns I could have messed up the sources’ tarball yesterday when making it in a rush before leaving, but no, it actually works fine, and I avoided another reindexing on a testing system.
Everything is up to date when when I try to install QMPlay2 I run into issues.
$ sudo port -vb install QMPlay2
Warning: depends_libs change: path:lib/libQtCore.4.dylib:qt4-mac
Warning: Using the mainstream/official Qt4 portgroup
---> Computing dependencies for QMPlay2.Warning: Using the mainstream/official Qt4 portgroup
Warning: depends_libs change: path:lib/libQtCore.4.dylib:qt4-mac
Warning: Using the mainstream/official Qt4 portgroup
..........^CError: Aborted: SIGINT received.
I can't seem to get qt4-mac-devel to install no matter what I do. I tried:
$ sudo port -vb install qt4-mac-devel
Error: Port qt4-mac-devel not found
I put a downloaded copies into incoming/verified and software. Nothing works. Debug doesn't print out anything either. Not sure what's up.
Well, do you have the port itself? What `port file qt4-mac-devel` shows? It is definitely existing in the ports sources (I mean, from macos-powerpc). If the command shows nothing, then either you did not sync ports or something prevented this port from parsing (if so, this is my issue to fix). Check if the port folder exists in ports/aqua.
You can see location of standard qt4-mac first, `port file qt4-mac`, go to that folder and see if `qt4-mac-devel` is also there or not.
@ChrisCharman BTW, let me see how huge will be a bootstrap installation which includes git and not just curl. Would be handy to have git working right-away.
Links on the website updated, here is the bootstrap git package: http://macos-powerpc.org/PPCPorts/bootstrap-git-powerpc-darwin10.zip (everything updated to current versions, rebuilt on 10.6.8).
Tested locally as such (git works neatly), not yet tested as a clean installation.
This already includes curl as a dependency.
Tested locally as such (git works neatly), not yet tested as a clean installation.
This already includes curl as a dependency.
Last edited:
$ port file qt4-mac
/opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac/Portfile
$ ls -ld /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4*
drwxrwxr-x 5 root wheel 170 Jan 14 08:00 /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac
drwxrwxr-x 5 root wheel 170 Jan 12 13:56 /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac-devel
sudo port -vb install qt4-mac
Warning: Using the mainstream/official Qt4 portgroup
---> Computing dependencies for qt4-mac........
The following dependencies will be installed:
dbus
lcms2
lerc
libdeflate
libjpeg-turbo
libmng
tiff
Continue? [Y/n]: n
So I don't continue because of the Warning
Please do not continue with qt4-mac (it won’t even build right now, and reaching to the point of error takes quite some time). I am dealing with it now, but it is preferable to use qt4-mac-devel even if the regular version works.
What do you get with `port -vd info /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac-devel`?
port -vd info /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac-devel
DEBUG: Opening port in directory: /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac-devel
DEBUG: OS darwin/10.8.0 (macOS 10.6.8) arch powerpc
DEBUG: NB:
Qt4 has been or will be installed in concurrent mode
DEBUG: Sourced PortGroup qt4 1.0 from /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/_resources/port1.0/group/qt4-1.0.tcl
DEBUG: Sourced PortGroup xcodeversion 1.0 from /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/_resources/port1.0/group/xcodeversion-1.0.tcl
DEBUG: Sourced PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
DEBUG: Sourced PortGroup compiler_wrapper 1.0 from /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/_resources/port1.0/group/compiler_wrapper-1.0.tcl
DEBUG: Sourced PortGroup openssl 1.0 from /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/_resources/port1.0/group/openssl-1.0.tcl
Error: qt4-mac-devel: PortGroup compress_workdir 1.0 could not be located. compress_workdir-1.0.tcl does not exist.
Trees checked: rsync://macos-powerpc.org/macos-powerpc/PPCPorts/ports.tar
DEBUG: PortGroup not found
while executing
"PortGroup compress_workdir 1.0"
(file "/opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac-devel/Portfile" line 59)
invoked from within
"source /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac-devel/Portfile"
invoked from within
"$workername eval [list source $portfilepath]"
DEBUG: PortGroup not found
while executing
"error $result"
(procedure "mportopen" line 54)
invoked from within
"mportopen $url"
Error: Port /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/aqua/qt4-mac-devel not found
Ok, thank you, now I know the problem.
Let me push a fix.
Do not run port sync, I will just handle a fixed version and you can do `portindex` instead, to save time.
UPD. Could you please open your `qt4-mac-devel` portfile and just replace its text with https://raw.githubusercontent.com/m...91140a1ebdbfeeb43/aqua/qt4-mac-devel/Portfile
I removed usage of that portgroup, but used an earlier version of this portfile in some of recent updates when trying to handle rsync and indexing. Sorry.
Then `cd /opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports` and `sudo portindex`. (This will avoid syncing ports from online sources and just add the missing one locally.)
Last edited:
That did it. I have QMPlay running!
I ran into one issue along the way.
./opt/local/var/run/dbus/.turd_dbus
Error: Failed to activate dbus: could not set group for file "/opt/local/var/run/dbus": group "_messagebus" does not exist
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_macos-powerpc.org_macos-powerpc_PPCPorts_ports_devel_dbus/dbus/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port qt4-mac-devel failed
However installing a couple of the other dependencies that WERE going to get installed and restarting the install of qt4-mac-devel skipped past the dbus group issue somehow.
I keep getting an error every time when I install a port which needs to create user/group. However it is a bogus error, groups are created but get recognized only after reboot.
This seems to be a problem specific to our 10.6.8 image and has to reported in the 10.6.8 development thread, I believe. This was not happening on 10a190.
BTW, does YouTube work from within the app? (Low resolution on streaming playback is expected at the moment, it is not a PowerPC issue.)
It doesn't. I can see them in the list but they won't play. That yt-dl thing is constantly being updated.
Did you do what is written in the port notes?
You should delete a copy of yt-dlp from ~/.qmplay2 and make a symlink to MacPorts version instead.
rm ~/.qmplay2/yt-dlp
cd ~/.qmplay2
ln -s /opt/local/bin/yt-dlp .
Writing this from memory, but I think it is correct.
I did that. It can't open the files. If I run yt-dl on a URL I can play on my macbook it fails as well.
$ yt-dlp BtV_nQKhkdY[/MEDIA]
[youtube] Extracting URL: BtV_nQKhkdY[/MEDIA]
[youtube] BtV_nQKhkdY: Downloading webpage
[youtube] BtV_nQKhkdY: Downloading ios player API JSON
[youtube] BtV_nQKhkdY: Downloading mweb player API JSON
[youtube] BtV_nQKhkdY: Downloading player 0b866fa6
[youtube] BtV_nQKhkdY: Downloading m3u8 information
[info] BtV_nQKhkdY: Downloading 1 format(s): 397+251
ERROR: unable to download video data: HTTP Error 403: Forbidden
Last edited:
Sorry, I do not really understand what “It can't open the files” means exactly. Could you make a screenshot of the error you get from QMPlay2, when you try opening some YouTube video (from within the app itself)?
Also, the output of `port -v installed QMPlay2 yt-dlp ffmpeg | grep active`.