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
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
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
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
supporting all the gcc versions between gcc 8 and 12 on older systems will be
quite a bit of work and require a lot of build time for poor users of these
systems.
To have libgcc7, the way it is now, you need to build libgcc13, 12, 11, 10, 9,
8, and then 7.
That is -- a lot of gcc building for
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,
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 Ma
Well, the PR is either merged or not merged :)
I think my proposal addresses all possible rational concerns.
If irrational concerns will happen to dominate, well, I can’t do anything about
that.
> On Mar 29, 2024, at 7:47 PM, Ken Cunningham
> wrote:
>
> I am not a MacPorts admin, however I b
In general, the more a given system deviates from the main herd of ports, the
more likely there are to be problems and the less likely they are to be fixed.
To be honest, I don’t see why a new gcc port to be used only for powerpc is
needed.
My only question is whether to skip over gcc8-12, or i
Hi,
Sorry - I missed these replies, ended up in the wrong mail folder. Was
about to re-write!
We had discussions in many points, tickets, ecc... lots of different
opinions.
Sergio Had wrote:
You should not need gcc8. I had gcc11 working on 10.5 ppc (and ppc64
too). I have seen people using
Hi,
Ken Cunningham wrote:
My only question is whether to skip over gcc8-12, or include them.
If we skip over gcc8-12, we can probably have a new release that uses
gcc13 as the primary gcc on all systems in macports done by Monday.
Less maybe. Last time I jumped the version, it took me an hour
Hi,
Ken Cunningham wrote:
To have libgcc7, the way it is now, you need to build libgcc13, 12, 11, 10, 9,
8, and then 7.
That is -- a lot of gcc building for a questionable benefit.
on my PowerMac dual-G4 about a week of compilation, given the time to
build gcc8...
But I understand we alwa
It’s important you understand how the libgcc ports work now, to see how this
libgcc chain is set up and the problems it might cause on slower older systems
that have no buildbot.
Go to an Intel system like 10.7, uninstall all ports.
Disable the buildbot by clearing archive_sites in sources.conf
Hi,
On 05/04/2024 12:30 pm, Ken Cunningham wrote:
It’s important you understand how the libgcc ports work now, to see how this
libgcc chain is set up and the problems it might cause on slower older systems
that have no buildbot.
Go to an Intel system like 10.7, uninstall all ports.
Disable t
On Apr 5, 2024, at 03:52, Riccardo Mottola wrote:
>
> I propose to keep even versions, because they are stable ones
Do you have a source for this claim? It's the first I've heard of it. As far as
I know, all gcc version numbers are stable.
On 05/04/2024 1:45 pm, Ryan Schmidt wrote:
On Apr 5, 2024, at 03:52, Riccardo Mottola wrote:
I propose to keep even versions, because they are stable ones
Do you have a source for this claim? It's the first I've heard of it. As far as
I know, all gcc version numbers are stable.
They ar
Hi,
Ryan Schmidt wrote:
I propose to keep even versions, because they are stable ones
Do you have a source for this claim? It's the first I've heard of it. As far as
I know, all gcc version numbers are stable.
I did a quick search and couldn't find one. It is something I pked up
years ago
> On 5 Apr 2024, at 7:03 PM, Riccardo Mottola via macports-dev
> wrote:
>
> Hi,
>
> Ryan Schmidt wrote:
>>> I propose to keep even versions, because they are stable ones
>> Do you have a source for this claim? It's the first I've heard of it. As far
>> as I know, all gcc version numbers a
On Apr 5, 2024, at 13:03, Riccardo Mottola wrote:
>
> Odd/Even was an old practice, possibly not followed anymore.
It was an old practice of GNOME abandoned in 2020. Graphviz, Cairo, Pango,
Pixman, Glib2 are examples, from ports I maintain(ed). The MacPorts "gnome"
livecheck recipe still follow
Two of the libgccs are stubs, the rest are not.
so it is pretty much as bad as it looks.
Once gcc13 is the default gcc used on older systems, it would be hoped that it
would cover off most needs.
Up to now, though, older systems have used gcc7, and in a few cases gcc5 or
gcc48 are used for specific issues. So those gcc versions may still be needed
... time will tell.
If the whole
Hi,
Ken Cunningham wrote:
Up to now, though, older systems have used gcc7, and in a few cases gcc5 or
gcc48 are used for specific issues. So those gcc versions may still be needed
... time will tell.
for me it is gcc48 (or apple 4.2 on tiger or such) for old software.
gcc6 covers most needs
> On Apr 7, 2024, at 11:24 PM, Riccardo Mottola
> wrote:
>
> Hi,
>
> Ken Cunningham wrote:
>> Up to now, though, older systems have used gcc7, and in a few cases gcc5 or
>> gcc48 are used for specific issues. So those gcc versions may still be
>> needed ... time will tell.
>
> for me it i
Hi,
I actually agreed with you, just skip from gcc7 to gcc13.
Ken Cunningham wrote:
Just yesterday I fixed gcc10-bootstrap to build on Tiger PPC and pushed that to
master, which required YA new bootstrap compiler. So the parts are now in place
for the attempt.
ohhh :) it took me 4 days to g
24 matches
Mail list logo