I am not a MacPorts admin, however I believe they were pretty clear that 10.6-ppc-specific fixes belong in an overlay repo, not in macports code.
If you want that changed, take it up with them. I personally agree with that decision, so I abide by it, until such time as it changes. K > On Mar 29, 2024, at 04:00, Sergio Had <vital....@gmail.com> wrote: > > > Ken, the last time you objected to having gcc10-bootstrap building for ppc on > 10.6 in gcc13 port. > Because that was extra 10 characters of code in the macro, which was too ugly > to tolerate, apparently. > (It was needed for 10.6.8 Rosetta just as much, of course: we cannot use > clangs on any powerpc, be it released macOS or pre-released.) > > Anyway, what I suggest is the following: > > 1. Keep Rosetta and 10.6 ppc stuff out of existing gcc ports. Those will be > only for 10.4–10.5 on PowerPC, which is what you want, AFAIU. No “spaghetti > code”, which you dislike. > 2. I make a separate gcc-powerpc port, analogous to gcc-devel, where I can > add tweaks I want, and restrict that port to PowerPC. Throw away everything > unneeded from there, make it easy to maintain. > > To that separate port I can add support for libc++ on PowerPC, fix IEEE > arithmetic in Fortran, support 10.6 ppc and Rosetta, and whats not. Which > will not land into any other gcc ports, unless someone else – not me – > decides to pick that. > > As I bonus I (and whomever decides to use it) can avoid unnecessary revbumps, > wasting many hours of compilation time for nothing, and on the other hand > revbump powerpc port without causing pain to anyone else. > > I honestly hope this can keep everyone satisfied. > > I also hope you can cooperate with me then to move 10.4–10.5 to libgcc13, > since we should not have a disagreement anymore. > > >> On Mar 29, 2024, at 5:34 AM, Ken Cunningham >> <ken.cunningham.web...@gmail.com> wrote: >> >> I was not aware that supporting the bootleg crippled 10.6 PPC pre-beta had >> anything to do with why nobody had gotten around to updating the gcc version >> used on older systems. >> >> At least, it was not anywhere on my radar. >> >> Just -- nobody did the legwork. >> >> Ken >> >> >>> On 2024-03-28, at 11:47 AM, Sergio Had wrote: >>> >>> Let me make another, final attempt to sort this out once for all and for >>> everyone on old systems. >>> >>> I got an idea how to satisfy Ken’s preference of not supporting ppc builds >>> on 10.6 in gcc ports and my need to support those. >>> >>> That was the stopper so far, not allowing an agreement to merge. >>> >>> I may do this today itself: I have everything working for months, just need >>> to sort commits to make it readable and implement a solution for what I >>> want. >>> >>> As a bonus, you will get IEEE intrinsics in Fortran – something that never >>> existed on ppc. >>>> On Mar 29, 2024 at 02:36 +0800, Sergio Had <vital....@gmail.com>, wrote: >>>> You should not need gcc8. I had gcc11 working on 10.5 ppc (and ppc64 too). >>>> I have seen people using gcc13 on 10.5 ppc following my instructions from >>>> the PR. >>>> >>>> What is the point of gcc8? >>>> >>>> You build gcc10-bootstrap and then use it to build gcc13. Nothing else >>>> needed in between. >>>>> On Mar 28, 2024 at 23:58 +0800, Riccardo Mottola via macports-dev >>>>> <macports-dev@lists.macports.org>, wrote: >>>>> Hi, >>>>> >>>>> after all the talk about gcc versions, I tried to build gcc 8 here. >>>>> Officially it says "gcc8 is known to fail". >>>>> >>>>> I first did just "build" on Intel 64bit and PPC 32bit - Intel 32bit >>>>> later, I fear my MacBook has fan issues. >>>>> >>>>> Intel 64bit finished build! Took several hours. I thus tried to install >>>>> it... and it says again >>>>> "libgcc8 is known to fail. Try to install anyway?" and yes, it just built! >>>>> >>>>> However then it asks about libgcc9.... but I want to stay on libgcc8, >>>>> that was the point... am Inheriting that it will go up to gcc13? >>>>> >>>>> >>>>> On PowerPC instead build fails (and ultimate goal is to enable newer >>>>> gccs on PPC too, where it is needed) >>>>> >>>>> :info:build cc1plus: warning: '-mdynamic-no-pic' overrides '-fpic', >>>>> '-fPIC', '-fpie' or '-fPIE' >>>>> :info:build >>>>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc8/gcc8/work/gcc-8.5.0/gcc/jit/jit-playback.c: >>>>> In member function 'gcc::jit::result* >>>>> gcc::jit::playback::context::dlopen_built_dso()': >>>>> :info:build >>>>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc8/gcc8/work/gcc-8.5.0/gcc/jit/jit-playback.c:2599:3: >>>>> error: 'dlerror' was not declared in this scope >>>>> :info:build dlerror (); >>>>> :info:build ^~~~~~~ >>>>> >>>>> >>>>> Already seen this? Full build log is 6.7MB >>>>> Should I open a ticket on this or is there already one for gcc8 efforts? >>>>> didn't find it. >>>>> >>>>> Riccardo >> >
