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

gcc11–gcc15 on 10.5.8, 10.6 PPC and 10.6.8 Rosetta (it works!)

saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany
strange, after a "sudo port self update" there were some new versions of installed ports. most ports did well but some of the ports can't be upgraded. it seems that my editing on gcc versions were maybe wrong or not sufficient.
you told me a "port sync" will overwrite the edited files. is that the case too when typing in "port self update"?

Code: 
port outdated
port outdated
The following installed ports are outdated:
chafa                          1.14.4_0 < 1.14.4_1       
exiftool                       12.960.0_0 < 12.970.0_0   
fastfetch                      2.24.0_0 < 2.25.0_0       
geeqie                         2.4_0 < 2.4_1             
ghostscript                    10.03.1_0 < 10.04.0_0     
gstreamer1                     1.24.7_0 < 1.24.8_0       
ImageMagick                    6.9.13-16_0 < 6.9.13-16_1   
libass                         0.17.2_0 < 0.17.3_0       
libical                        3.0.17_1 < 3.0.18_0       
libjpeg-turbo                  3.0.3_0 < 3.0.4_0         
libjxl                         0.10.3_0 < 0.11.0_0       
libspectre                     0.2.12_3 < 0.2.12_4       
netpbm                         11.07.00_0 < 11.07.01_0   
p5.34-image-exiftool           12.960.0_0 < 12.970.0_0   
p5.34-test-simple              1.302.203_0 < 1.302.204_1   
tiff                           4.6.0_0 < 4.7.0_0


most of the outdated ports depend on libjpeg-turbo, which is not installable.

Code: 
sudo port install libjpeg-turbo
sudo port install libjpeg-turbo
sudo: Zeitstempel aus der Zukunft wird ignoriert
Passwort:
--->  Computing dependencies for libjpeg-turbo
--->  Configuring libjpeg-turbo
Error: Failed to configure libjpeg-turbo: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_libjpeg-turbo/libjpeg-turbo/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port libjpeg-turbo failed

As i understand port want to use gcc 4.2 even gcc 10 and 14 are installed. Is THAT the problem?
 

Attachments

  • main.txt
    478.1 KB · Views: 15
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
strange, after a "sudo port self update" there were some new versions of installed ports. most ports did well but some of the ports can't be upgraded. it seems that my editing on gcc versions were maybe wrong or not sufficient.
you told me a "port sync" will overwrite the edited files. is that the case too when typing in "port self update"?

Code: 
port outdated
port outdated
The following installed ports are outdated:
chafa                          1.14.4_0 < 1.14.4_1      
exiftool                       12.960.0_0 < 12.970.0_0  
fastfetch                      2.24.0_0 < 2.25.0_0      
geeqie                         2.4_0 < 2.4_1            
ghostscript                    10.03.1_0 < 10.04.0_0    
gstreamer1                     1.24.7_0 < 1.24.8_0      
ImageMagick                    6.9.13-16_0 < 6.9.13-16_1  
libass                         0.17.2_0 < 0.17.3_0      
libical                        3.0.17_1 < 3.0.18_0      
libjpeg-turbo                  3.0.3_0 < 3.0.4_0        
libjxl                         0.10.3_0 < 0.11.0_0      
libspectre                     0.2.12_3 < 0.2.12_4      
netpbm                         11.07.00_0 < 11.07.01_0  
p5.34-image-exiftool           12.960.0_0 < 12.970.0_0  
p5.34-test-simple              1.302.203_0 < 1.302.204_1  
tiff                           4.6.0_0 < 4.7.0_0


most of the outdated ports depend on libjpeg-turbo, which is not installable.

Code: 
sudo port install libjpeg-turbo
sudo port install libjpeg-turbo
sudo: Zeitstempel aus der Zukunft wird ignoriert
Passwort:
--->  Computing dependencies for libjpeg-turbo
--->  Configuring libjpeg-turbo
Error: Failed to configure libjpeg-turbo: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_libjpeg-turbo/libjpeg-turbo/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port libjpeg-turbo failed

As i understand port want to use gcc 4.2 even gcc 10 and 14 are installed. Is THAT the problem?
Click to expand...

Looks like you got a broken CMake installation:
Code: 
:info:configure dyld: lazy symbol binding failed: Symbol not found: __ZNSo9_M_insertIeEERSoT_
:info:configure   Referenced from: /opt/local/bin/cmake-orig
:info:configure   Expected in: /opt/local/lib/libgcc/libstdc++.6.dylib
:info:configure dyld: Symbol not found: __ZNSo9_M_insertIeEERSoT_
:info:configure   Referenced from: /opt/local/bin/cmake-orig
:info:configure   Expected in: /opt/local/lib/libgcc/libstdc++.6.dylib
:info:configure sh: line 1: 44458 Trace/BPT trap

This should not happen, of course, but I have no idea how did you build it. Assuming you have gcc14 and libgcc14 now, and change needed settings so that 10.5 behaves like 10.6 on ppc, you can rebuild CMake and see if that helps:
Code: 
sudo port -v -n upgrade --force cmake

I never use selfupdate and recommend to avoid it; port sync is less disruptive and at least won’t damage the basic setup.
 
  • Like
Reactions: saxfun
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
strange, after a "sudo port self update" there were some new versions of installed ports. most ports did well but some of the ports can't be upgraded. it seems that my editing on gcc versions were maybe wrong or not sufficient.
you told me a "port sync" will overwrite the edited files. is that the case too when typing in "port self update"?

Code: 
port outdated
port outdated
The following installed ports are outdated:
chafa                          1.14.4_0 < 1.14.4_1      
exiftool                       12.960.0_0 < 12.970.0_0  
fastfetch                      2.24.0_0 < 2.25.0_0      
geeqie                         2.4_0 < 2.4_1            
ghostscript                    10.03.1_0 < 10.04.0_0    
gstreamer1                     1.24.7_0 < 1.24.8_0      
ImageMagick                    6.9.13-16_0 < 6.9.13-16_1  
libass                         0.17.2_0 < 0.17.3_0      
libical                        3.0.17_1 < 3.0.18_0      
libjpeg-turbo                  3.0.3_0 < 3.0.4_0        
libjxl                         0.10.3_0 < 0.11.0_0      
libspectre                     0.2.12_3 < 0.2.12_4      
netpbm                         11.07.00_0 < 11.07.01_0  
p5.34-image-exiftool           12.960.0_0 < 12.970.0_0  
p5.34-test-simple              1.302.203_0 < 1.302.204_1  
tiff                           4.6.0_0 < 4.7.0_0


most of the outdated ports depend on libjpeg-turbo, which is not installable.

Code: 
sudo port install libjpeg-turbo
sudo port install libjpeg-turbo
sudo: Zeitstempel aus der Zukunft wird ignoriert
Passwort:
--->  Computing dependencies for libjpeg-turbo
--->  Configuring libjpeg-turbo
Error: Failed to configure libjpeg-turbo: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_libjpeg-turbo/libjpeg-turbo/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port libjpeg-turbo failed

As i understand port want to use gcc 4.2 even gcc 10 and 14 are installed. Is THAT the problem?
Click to expand...

BTW, this is an illustration to my earlier point of why it makes sense to build everything as it is set-up and avoid randomly switching compilers etc. Unless, of course, existing set-up is wrong (which happens), and then it should be fixed in MacPorts master, preferably, for everyone.

If you built some ports against libgcc7 and then possibly some other libgcc version, and now against libgcc14, that may not always work. While a few recent libgcc versions seem to be compatible, AFAIK, perhaps no one ever tried to switch between libgcc7 and libgcc14. Usually rebuilding affected ports fixes such problems.
 
saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany
cmake failed.

BTW: I did not compile ports with configure.compiler option, I TRIED (but it failed regarding one port). though I have to admit I tried to build gcc10, gcc14 later on, and compiled later on with your suggestions you gave for editing files.

campe error:
 

Attachments

  • main.txt
    29.1 KB · Views: 14
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
cmake failed.

BTW: I did not compile ports with configure.compiler option, I TRIED (but it failed regarding one port). though I have to admit I tried to build gcc10, gcc14 later on, and compiled later on with your suggestions you gave for editing files.

campe error:
Click to expand...

From the log it follows that you try using gcc7. I suggest you do not use gcc7 at all for now.

Unfortunately, port sync (or selfupdate) overwrites changes in port groups, compiler settings and portfiles (the latter can be avoided by a local overlay repo), so you need to make those again. (An easier way would be to have fixed versions locally and just replace those files with a few terminal commands.)

Once that is done, CMake will not use gcc7. Given it does use it, something has been missed, which is why it fails now.

I.e. if you maintain correct settings, nothing ever should by default pick any other gcc besides either Xcode one or gcc14 (or whichever is set as the main one). There are two systemic exceptions, R ports will use gcc13 and the same is true for fpm-using Fortran ports. That is fine, gcc13 works with libgcc14.
 
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
cmake failed.

BTW: I did not compile ports with configure.compiler option, I TRIED (but it failed regarding one port). though I have to admit I tried to build gcc10, gcc14 later on, and compiled later on with your suggestions you gave for editing files.

campe error:
Click to expand...

If it is helpful, I can make a GH tree with just fixes for MacPorts on 10.5 (or rather update the existing gcc_move one).
 
saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany
i edited ALL the 4 files you suggested again after "port sync"

now port recognizes gcc14 as compiler and it is running (for some hours I think ;) )

maybe I can fix this but thanks for all your help!
 
saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany
cmake make failed.

two logs attached.
 

Attachments

  • cmake_bootstrap.txt
    27.9 KB · Views: 15
  • main.txt
    356 KB · Views: 13
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
i edited ALL the 4 files you suggested again after "port sync"

now port recognizes gcc14 as compiler and it is running (for some hours I think ;) )

maybe I can fix this but thanks for all your help!
Click to expand...

My comment was solely based on the log of CMake build which you included. That has the following:
Code: 
:notice:configure --->  Configuring cmake
:debug:configure Preferred compilers: macports-gcc-7 macports-gcc-6 macports-gcc-5
:debug:configure Using compiler 'MacPorts GCC 7'
:debug:configure Executing org.macports.configure (cmake)
:debug:configure Environment: 
:debug:configure CC='/opt/local/bin/gcc-mp-7'
:debug:configure CC_PRINT_OPTIONS='YES'
:debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/.CC_PRINT_OPTIONS'
:debug:configure CFLAGS='-pipe -Os -arch ppc'
:debug:configure CMAKE_INCLUDE_PATH='/opt/local/include/ncurses'
:debug:configure CMAKE_LIBRARY_PATH='/opt/local/lib'
:debug:configure CMAKE_OSX_DEPLOYMENT_TARGET='10.5'
:debug:configure CMAKE_PREFIX_PATH='/opt/local'
:debug:configure CPATH='/opt/local/include'
:debug:configure CPLUS_INCLUDE_PATH='/opt/local/include/LegacySupport'
:debug:configure CPPFLAGS='-isystem/opt/local/include/LegacySupport -I/opt/local/include'
:debug:configure CXX='/opt/local/bin/g++-mp-7'
:debug:configure CXXFLAGS='-pipe -Os -D_GLIBCXX_USE_CXX11_ABI=0 -arch ppc'
:debug:configure C_INCLUDE_PATH='/opt/local/include/LegacySupport'
:debug:configure DEVELOPER_DIR='/Developer'
:debug:configure DYLD_LIBRARY_PATH='/opt/local/lib/libgcc'
:debug:configure F77='/opt/local/bin/gfortran-mp-7'
:debug:configure F90='/opt/local/bin/gfortran-mp-7'
:debug:configure F90FLAGS='-pipe -Os -m32'
:debug:configure FC='/opt/local/bin/gfortran-mp-7'
:debug:configure FCFLAGS='-pipe -Os -m32'
:debug:configure FFLAGS='-pipe -Os -m32'
:debug:configure INSTALL='/usr/bin/install -c'
:debug:configure LDFLAGS='-Wl,-headerpad_max_install_names -latomic -L/opt/local/lib -lMacportsLegacySupport -arch ppc'
:debug:configure LIBRARY_PATH='/opt/local/lib'
:debug:configure MACOSX_DEPLOYMENT_TARGET='10.5'
:debug:configure MACPORTS_LEGACY_SUPPORT_CPPFLAGS='-isystem/opt/local/include/LegacySupport'
:debug:configure MACPORTS_LEGACY_SUPPORT_ENABLED='1'
:debug:configure MACPORTS_LEGACY_SUPPORT_LDFLAGS='-L/opt/local/lib -lMacportsLegacySupport'
:debug:configure OBJC='/opt/local/bin/gcc-mp-7'
:debug:configure OBJCFLAGS='-pipe -Os -arch ppc'
:debug:configure OBJCPLUS_INCLUDE_PATH='/opt/local/include/LegacySupport'
:debug:configure OBJCXX='/opt/local/bin/g++-mp-7'
:debug:configure OBJCXXFLAGS='-pipe -Os -D_GLIBCXX_USE_CXX11_ABI=0 -arch ppc'
:debug:configure OBJC_INCLUDE_PATH='/opt/local/include/LegacySupport'
:debug:configure SDKROOT='/'
:debug:configure SOURCE_DATE_EPOCH='1726716017'
:info:configure Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.29.5" && ./bootstrap --prefix=/opt/local --docdir=share/doc/cmake --parallel=1 --init=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.29.5/macports.cmake --system-libs --no-qt-gui --no-system-jsoncpp --no-system-librhash --no-system-libuv --no-system-cppdap -- 
:debug:configure system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.29.5" && ./bootstrap --prefix=/opt/local --docdir=share/doc/cmake --parallel=1 --init=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.29.5/macports.cmake --system-libs --no-qt-gui --no-system-jsoncpp --no-system-librhash --no-system-libuv --no-system-cppdap -- 
:info:configure ---------------------------------------------
:info:configure CMake 3.29.5, Copyright 2000-2024 Kitware, Inc. and Contributors
:info:configure ---------------------------------------------
:info:configure Error when bootstrapping CMake:
:info:configure Cannot find appropriate C compiler on this system.
:info:configure Please specify one using environment variable CC.
:info:configure See cmake_bootstrap.log for compilers attempted.
:info:configure ---------------------------------------------
:info:configure Log of errors: /opt/local/var/macports/build/

As you can see, that has gcc7 picked. That can happen only in two cases:
1. gcc7 is set somewhere as the main compiler when C11/C++11 or higher standard is required (for example, for CMake) or Xcode gcc blacklisted.
2. gcc7 is forced as a compiler first choice either in the portfile or on a command line.

I apologize, if I happened to miss some place which needs a tweak for 10.5. But I think this is it:
1. gcc7 portfile (remove special case).
2. gcc14 portfile (remove platform restriction, add gcc10-bootstrap block, remove gcc-4.2 from blacklist).
3. libgcc portfile (set libgcc14 to be used).
4. gcc_compilers.tcl and gcc_dependencies.tcl in compilers directory (set gcc14 and libgcc14 to be used).
5. compilers.tcl port group (set gcc14 to be used).
6. If needed: change defaults likewise in R and fortran port groups, in mpich port, in fortran-stdlib port and possibly a couple of others. Most likely none of these are of concern for you at the moment.
 
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
cmake make failed.

two logs attached.
Click to expand...

Ok, thank you, this is what we needed. Gimme a sec, I give a fix for this.

UPD. So this is the issue: https://gitlab.kitware.com/cmake/cmake/-/issues/26223
A quick fix is to add the following into CMake portfile:

Code: 
configure.cflags-append -Wno-error=incompatible-pointer-types

Just add this line somewhere around other configure arguments. Since you are fixing this locally, no need to do it conditionally on compiler version etc. (the issue affects gcc14, since it became stricter with warnings/errors).

P. S. The fix has been added to cmake-devel port, but not to regular cmake: https://github.com/macports/macports-ports/commit/8b3057d5dd133fcef99eac242c3a15c5aaadd59a
 
Last edited:
saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany
barracuda156 said:
My comment was solely based on the log of CMake build which you included. That has the following:
Code: 
:notice:configure --->  Configuring cmake
:debug:configure Preferred compilers: macports-gcc-7 macports-gcc-6 macports-gcc-5
:debug:configure Using compiler 'MacPorts GCC 7'
:debug:configure Executing org.macports.configure (cmake)
:debug:configure Environment:
:debug:configure CC='/opt/local/bin/gcc-mp-7'
:debug:configure CC_PRINT_OPTIONS='YES'
:debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/.CC_PRINT_OPTIONS'
:debug:configure CFLAGS='-pipe -Os -arch ppc'
:debug:configure CMAKE_INCLUDE_PATH='/opt/local/include/ncurses'
:debug:configure CMAKE_LIBRARY_PATH='/opt/local/lib'
:debug:configure CMAKE_OSX_DEPLOYMENT_TARGET='10.5'
:debug:configure CMAKE_PREFIX_PATH='/opt/local'
:debug:configure CPATH='/opt/local/include'
:debug:configure CPLUS_INCLUDE_PATH='/opt/local/include/LegacySupport'
:debug:configure CPPFLAGS='-isystem/opt/local/include/LegacySupport -I/opt/local/include'
:debug:configure CXX='/opt/local/bin/g++-mp-7'
:debug:configure CXXFLAGS='-pipe -Os -D_GLIBCXX_USE_CXX11_ABI=0 -arch ppc'
:debug:configure C_INCLUDE_PATH='/opt/local/include/LegacySupport'
:debug:configure DEVELOPER_DIR='/Developer'
:debug:configure DYLD_LIBRARY_PATH='/opt/local/lib/libgcc'
:debug:configure F77='/opt/local/bin/gfortran-mp-7'
:debug:configure F90='/opt/local/bin/gfortran-mp-7'
:debug:configure F90FLAGS='-pipe -Os -m32'
:debug:configure FC='/opt/local/bin/gfortran-mp-7'
:debug:configure FCFLAGS='-pipe -Os -m32'
:debug:configure FFLAGS='-pipe -Os -m32'
:debug:configure INSTALL='/usr/bin/install -c'
:debug:configure LDFLAGS='-Wl,-headerpad_max_install_names -latomic -L/opt/local/lib -lMacportsLegacySupport -arch ppc'
:debug:configure LIBRARY_PATH='/opt/local/lib'
:debug:configure MACOSX_DEPLOYMENT_TARGET='10.5'
:debug:configure MACPORTS_LEGACY_SUPPORT_CPPFLAGS='-isystem/opt/local/include/LegacySupport'
:debug:configure MACPORTS_LEGACY_SUPPORT_ENABLED='1'
:debug:configure MACPORTS_LEGACY_SUPPORT_LDFLAGS='-L/opt/local/lib -lMacportsLegacySupport'
:debug:configure OBJC='/opt/local/bin/gcc-mp-7'
:debug:configure OBJCFLAGS='-pipe -Os -arch ppc'
:debug:configure OBJCPLUS_INCLUDE_PATH='/opt/local/include/LegacySupport'
:debug:configure OBJCXX='/opt/local/bin/g++-mp-7'
:debug:configure OBJCXXFLAGS='-pipe -Os -D_GLIBCXX_USE_CXX11_ABI=0 -arch ppc'
:debug:configure OBJC_INCLUDE_PATH='/opt/local/include/LegacySupport'
:debug:configure SDKROOT='/'
:debug:configure SOURCE_DATE_EPOCH='1726716017'
:info:configure Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.29.5" && ./bootstrap --prefix=/opt/local --docdir=share/doc/cmake --parallel=1 --init=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.29.5/macports.cmake --system-libs --no-qt-gui --no-system-jsoncpp --no-system-librhash --no-system-libuv --no-system-cppdap --
:debug:configure system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.29.5" && ./bootstrap --prefix=/opt/local --docdir=share/doc/cmake --parallel=1 --init=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.29.5/macports.cmake --system-libs --no-qt-gui --no-system-jsoncpp --no-system-librhash --no-system-libuv --no-system-cppdap --
:info:configure ---------------------------------------------
:info:configure CMake 3.29.5, Copyright 2000-2024 Kitware, Inc. and Contributors
:info:configure ---------------------------------------------
:info:configure Error when bootstrapping CMake:
:info:configure Cannot find appropriate C compiler on this system.
:info:configure Please specify one using environment variable CC.
:info:configure See cmake_bootstrap.log for compilers attempted.
:info:configure ---------------------------------------------
:info:configure Log of errors: /opt/local/var/macports/build/

As you can see, that has gcc7 picked. That can happen only in two cases:
1. gcc7 is set somewhere as the main compiler when C11/C++11 or higher standard is required (for example, for CMake) or Xcode gcc blacklisted.
2. gcc7 is forced as a compiler first choice either in the portfile or on a command line.

I apologize, if I happened to miss some place which needs a tweak for 10.5. But I think this is it:
1. gcc7 portfile (remove special case).
2. gcc14 portfile (remove platform restriction, add gcc10-bootstrap block, remove gcc-4.2 from blacklist).
3. libgcc portfile (set libgcc14 to be used).
4. gcc_compilers.tcl and gcc_dependencies.tcl in compilers directory (set gcc14 and libgcc14 to be used).
5. compilers.tcl port group (set gcc14 to be used).
6. If needed: change defaults likewise in R and fortran port groups, in mpich port, in fortran-stdlib port and possibly a couple of others. Most likely none of these are of concern for you at the moment.
Click to expand...
How to archive 2 exactly? Where to edit and how? Can you post your config?
regarding 5.: I edited this, maybe I did smith wrong? please post your edits.
 
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
How to archive 2 exactly? Where to edit and how? Can you post your config?
regarding 5.: I edited this, maybe I did smith wrong? please post your edits.
Click to expand...

github.com

gcc7–8: do away with redundant isLastSupported · macports/macports-ports@4e4961e

The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.
github.com github.com
github.com

gcc_dependencies.tcl: adjust to the changes · macports/macports-ports@4ddbd82

The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.
github.com github.com
github.com

libgcc: update to pick up changes · macports/macports-ports@1361957

The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.
github.com github.com
github.com

compilers PG: update compilers · macports/macports-ports@6271d40

The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.
github.com github.com
github.com

gcc8+: build with gcc10-bootstrap on < 10.6 · macports/macports-ports@3a4faf4

The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.
github.com github.com
github.com

gcc_compilers.tcl: update compilers · macports/macports-ports@bc7f7e7

The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.
github.com github.com

You can ignore all gcc* portfiles besides gcc7 and gcc14. Obviously, use 14 wherever there is 13 here (it is an old tree).
These will not apply automatically now, so please edit manually. Everything should be obvious: the only thing done here is to change default behavior of 10.5 to match 10.6 (and use gcc10-bootstrap to build other gccs).

From you last log it looks like compiler choice worked correctly. And you only need this to CMake: https://github.com/macports/macports-ports/commit/8b3057d5dd133fcef99eac242c3a15c5aaadd59a
Alternatively, you can install cmake-devel, it works as a replacement for cmake.
 
  • Like
Reactions: bkmoore773
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
This is not strictly “my config”, because I do not need most of these on 10.6. But this is what should work on 10.5.

My config is close to the default branch here: https://github.com/barracuda156/powerpc-ports
I use both ld64-97 and cctools with +llvmppc (which is available in the tree but not forced as the default).
 
saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany
Thanks a lot!

cmake did build successfully! After daily work I just ran "sudo port upgrade outdated", first port "libjpeg-turbo" built! Great. Downs and ups with MP . . .
 
saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany

Attachments

  • main.txt
    94.2 KB · Views: 13
Last edited:
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
libass, again, is the problem. the two fixes, which helps me with last version of libass, came through upstream into the two files ass_coretext.c and ass_compat.h.
i double checked it, fixed were there. log attached, it seems that some 10.6 checks are responsible for the error.

EDIT: at the end I fixed it with your tip:

Click to expand...

The error looks like the same which occurred earlier. No idea why it is back again, supposedly should have been fixed by those upstream commits, which are now added into the portfile. Cannot help with this at the moment, no access to hardware, but I guess you can survive for now with a local hack. Result is expected to be identical.
 
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany
10a190 won't get my PBs sleep and wifi (wifi maybe fixable). That's a real showstopper for me. Maybe some day sleep will be fixed (beyond my knowledge) or the new shared 10a222 from e. Kovacs will be fixed. I'm eagerly waiting.
 
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
10a190 won't get my PBs sleep and wifi (wifi maybe fixable). That's a real showstopper for me. Maybe some day sleep will be fixed (beyond my knowledge) or the new shared 10a222 from e. Kovacs will be fixed. I'm eagerly waiting.
Click to expand...

Wifi certainly is fixable (I have it working on 10a190 and 10a222). Sleep, I think, does not work on any existing build. (I think it also does not work on OpenBSD and others.)
 
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
now ports is up to date again!
Click to expand...

Btw if you have a chance, could you check if oneTBB and folly compile on 10.5 in their current versions?

folly | MacPorts

ports.macports.org ports.macports.org

onetbb | MacPorts

ports.macports.org ports.macports.org

Folly pulls in a number of dependencies, so this is not a 5 min task. Though possibly you already have boost181, and other dependencies should not be too heavy.

If you have X11 working (as I understand, you do), it would be nice to know if abaddon builds.

abaddon | MacPorts

ports.macports.org ports.macports.org

(It it is troublesome to check, just ignore this, no big deal.)
 
saxfun

saxfun

macrumors regular
Mar 14, 2016
139
25
Germany
folly: strange error, ad hoc.

Code: 
--->  Computing dependencies for folly
Error: Cannot install libgcc for the archs 'i386 ppc' because
Error: its dependency libgcc14 cannot build for the required archs.
Error: Follow https://guide.macports.org/#project.tickets if you believe there
is a bug.
Error: Processing of port folly failed


onetbb: error log attached

abaddon:

long list of dependencies, compiling over night.

Code: 
sudo port install abaddon
--->  Computing dependencies for abaddon
The following dependencies will be installed:
 atkmm-1.6
 cairomm
 cairomm-1.0
 doxygen
 glade
 glibmm
 glibmm-2.4
 gtkmm3
 ixwebsocket
 libfmt10
 libhandy
 libmetalink
 libsigcxx2
 libsigcxx3
 libsodium
 mm-common
 nlohmann-json
 pangomm-1.4
 py311-build
 py311-cairo
 py311-cython
 py311-flit_core
 py311-gobject3
 py311-installer
 py311-packaging
 py311-pyproject_hooks
 py311-setuptools
 py311-wheel
 rnnoise
 spdlog
 wget
 

Attachments

  • onetbb.txt
    118 KB · Views: 14
B

barracuda156

macrumors 68020
Original poster
Sep 3, 2021
2,326
1,535
saxfun said:
abbadon error log attached
Click to expand...

Thank you very much.

1. The error you see with `folly` looks familiar and is certainly not specific to `folly`, but I don’t recall what causes that. Probably I need to try reproducing this locally in order to make sure it works correctly.

2. `onetbb` failure should be fixable, it is an actual problem with its source code. I have opened a ticket for that now: https://trac.macports.org/ticket/71035

3. For `abaddon`, turned out, there is a ticket, which I totally forgot about (because it was not assigned to me): https://trac.macports.org/ticket/70289
I will address this in a while.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom