Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ChrisCharman

macrumors 6502a
May 10, 2020
517
675
Bournemouth, UK
After discussing the matter with Iain, I came to conclusion that ppc64 for 10.6 is a lost case: https://github.com/iains/darwin-toolchains-start-here/discussions/5#discussioncomment-1953839

What he instead suggested is trying to make 10.6.8 bootable and working on ppc, since it has full support for ppc32 for Rosetta. (If I don’t mistake, you want to do something like that?)

As for MP, I will write a post, probably soon. Need to figure out some stuff.
Interesting.

Yes, i would like to do that at some point in order to speed up compilation time by cross-compiling.

I look forward to reading the new MacPorts thread, as I haven’t had any time to play with it for a long time and would appreciate following the steps you’ve taken.
 

barracuda156

macrumors 68020
Sep 3, 2021
2,322
1,534
Don’t worry yourself too much over it, unless you’re wanting/planning to use irssi for yourself. If so, then go for it.

Well, it was failing on 10.6.8, but it built with no tweaks on 10A190:

Code:
36-47:~ svacchanda$ port -v installed irssi
The following ports are currently installed:
  irssi @1.2.3_1+perl (active) requested_variants='' platform='darwin 10' archs='ppc' date='2022-01-28T18:28:38+0800'
 

barracuda156

macrumors 68020
Sep 3, 2021
2,322
1,534
I am not sure pkg is correct, since packaging did not work via Macports for me (missing productbuild utility) and I just packaged files from destroot with PackageMaker, but try it. You may probably install manually too.
Either should be done outside of Macports tree.
 

Attachments

  • destroot.zip
    728.2 KB · Views: 75
  • irssi.pkg.zip
    638.2 KB · Views: 149
  • Like
Reactions: ChrisCharman

barracuda156

macrumors 68020
Sep 3, 2021
2,322
1,534
Ah I see. Let me try to build it. (I can confirm it fails to build as-is, but fix may not be hard.)

UPD. It does build on 10.6.8 (Rosetta) for ppc, however with newer Xcode tools. I dunno from which exactly Xcode it gonna start working, but Xcode 3.2 from 10A433 built it:

Code:
~ svacchanda$ port -v installed irssi
The following ports are currently installed:
  irssi @1.2.3_1+perl (active) requested_variants='' platform='darwin 10' archs='ppc' date='2022-01-29T22:14:05+0800'

On 10.6 PPC it builds with Xcode tools from 10A222.
 
  • Like
Reactions: ChrisCharman

barracuda156

macrumors 68020
Sep 3, 2021
2,322
1,534
After updating openssl to v. 3.2 I had to rebuild quite a number of ports now, and I can confirm that irssi still builds on 10A190 with no trickery:
Code:
36-47% port -v installed irssi
The following ports are currently installed:
  irssi @1.2.3_1+perl (active) requested_variants='' platform='darwin 10' archs='ppc' date='2022-02-10T23:15:02+0800'
 

alphaer

macrumors newbie
Oct 6, 2021
12
1
hello!
I have ppc 10.5.8
xcode with gcc 4.2
Please help - how to build cctools or avoid this dependence
May be anybody have binary packet cctools-949.0.1_2.darwin_9.ppc.tbz2

cctools-949.0.1/misc'
/usr/bin/g++-4.2 -Os -arch ppc -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/other -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/include -c -o \
./PruneTrie.o ./PruneTrie.cpp
In file included from ./PruneTrie.cpp:26:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1660: error: ‘build_version_command’ does not name a type
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp: In member function ‘uint32_t macho_build_version_command<P>::cmd() const’:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1639: error: ‘fields’ was not declared in this scope
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp: In member function ‘void macho_build_version_command<P>::set_cmd(uint32_t)’:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1640: error: ‘fields’ was not declared in this scope
 
  • Like
Reactions: barracuda156

B S Magnet

macrumors 603
Original poster
hello!
I have ppc 10.5.8
xcode with gcc 4.2
Please help - how to build cctools or avoid this dependence
May be anybody have binary packet cctools-949.0.1_2.darwin_9.ppc.tbz2

cctools-949.0.1/misc'
/usr/bin/g++-4.2 -Os -arch ppc -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/other -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/include -c -o \
./PruneTrie.o ./PruneTrie.cpp
In file included from ./PruneTrie.cpp:26:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1660: error: ‘build_version_command’ does not name a type
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp: In member function ‘uint32_t macho_build_version_command<P>::cmd() const’:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1639: error: ‘fields’ was not declared in this scope
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp: In member function ‘void macho_build_version_command<P>::set_cmd(uint32_t)’:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1640: error: ‘fields’ was not declared in this scope

Hi @alphaer — you need to make a new topic post with the problem you’re having.

This thread is specific to issues relating to macports on Snow Leopard 10.6 on PPC — not issues relating to Leopard 10.5.8 on PPC.

Also, you may want to post this on the macports support pages.
 
  • Like
Reactions: Amethyst1

B S Magnet

macrumors 603
Original poster
It seems I cant make a new topics

You can.

1652457901608.png


Use the “Post thread” button (in red) on the forum index page.
 
  • Like
Reactions: Amethyst1

barracuda156

macrumors 68020
Sep 3, 2021
2,322
1,534
hello!
I have ppc 10.5.8
xcode with gcc 4.2
Please help - how to build cctools or avoid this dependence
May be anybody have binary packet cctools-949.0.1_2.darwin_9.ppc.tbz2

cctools-949.0.1/misc'
/usr/bin/g++-4.2 -Os -arch ppc -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/other -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/include -c -o \
./PruneTrie.o ./PruneTrie.cpp
In file included from ./PruneTrie.cpp:26:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1660: error: ‘build_version_command’ does not name a type
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp: In member function ‘uint32_t macho_build_version_command<P>::cmd() const’:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1639: error: ‘fields’ was not declared in this scope
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp: In member function ‘void macho_build_version_command<P>::set_cmd(uint32_t)’:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/../ld64-530/src/abstraction/MachOFileAbstraction.hpp:1640: error: ‘fields’ was not declared in this scope
Your original choice of the thread was better.

You should not need any tweaks on 10.5.8. Do you try to build something custom with modified portfile?
 

barracuda156

macrumors 68020
Sep 3, 2021
2,322
1,534
You can.

View attachment 2004635

Use the “Post thread” button (in red) on the forum index page.

BTW are you in touch with Moderators here? If we make a sticky thread for Macports-related support, I can take that on myself (unless someone more competent is willing to do that). Then a) we won’t get random queries in unrelated threads and b) people are more likely to actually get some support.
 

g_rettke

macrumors newbie
Jul 22, 2022
1
0
I originally was pulled in here by the question of whether a newer gcc would build on this system, and I have indeed been successful in so doing, using the script I posted and a couple of small, single-digit changes in gcc/config/darwin.h:

$ ./gcc -v
Using built-in specs.
COLLECT_GCC=./gcc
COLLECT_LTO_WRAPPER=/opt/gcc7/libexec/gcc/powerpc-apple-darwin10.0.0d2/7.5.0/lto-wrapper
Target: powerpc-apple-darwin10.0.0d2
Configured with: ../configure --prefix=/opt/gcc7 --enable-languages=c,c++,fortran,lto,objc,obj-c++ --with-system-zlib --disable-nls --disable-multilib --with-dwarf2
Thread model: posix
gcc version 7.5.0 (GCC)
✄SNIP✄SNIP✄SNIP✄SNIP✄SNIP✄SNIP✄SNIP✄SNIP✄SNIP✄SNIP✄SNIP✄SNIP
zlib @1.2.11_0 (active) requested_variants='' platform='darwin 10' archs='ppc' date='2021-08-23T11:35:18-0700'

All of them are proper PPC binaries, of course, no i386 binaries in this mix, and so far, at least, they all seem to work just fine.

I'll think about how to make these MacPorts changes available. I don't want to cause too much confusion in so doing. Probably I'll make a repo with the macports-base changes integrated, and a custom ports tree overlay like I do with TigerPorts, LeopardPorts, SnowLeopardPorts, and LionPorts, and people can use it if they so choose to do so.

@kencu Are your TigerPorts still available?

I see it in the Wayback Machine here but no longer on GitHub.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.