[prev in list] [next in list] [prev in thread] [next in thread]
List: macports-dev
Subject: Re: 10.5 and gcc8 x86-64 ok but ppc bails with dlerror
From: Ken Cunningham <ken.cunningham.webuse () gmail ! com>
Date: 2024-03-29 18:33:06
Message-ID: 2AD6E906-25D9-4E10-8716-F7E7E82ECEFF () gmail ! com
[Download RAW message or body]
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 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.
And then — no more worries. Existing macports base infrastructure will just work as \
it is. Some fairly minor tweaking of what compilers are available on which systems \
will be done.
If we have to fix all the gcc versions between gcc8 and 12 — well that will take a \
bit more time to fix and to build.
For Riccardo's bug, we always knew the gcc JIT was fragile on 32 bit systems. It \
probably needs to be disabled there by tweaking this block in the gcc8 Portfile:
if {${subport} eq "gcc8"} {
# the jit is not building on i386 systems
# see https://trac.macports.org/ticket/61130
if {${build_arch} ne "i386"} {
lappend gcc_configure_langs jit
}
}
Maybe that's all it needs.
Ken
> On Mar 29, 2024, at 4:50 AM, Sergio Had <vital.had@gmail.com> wrote:
>
> Well, the PR is either merged or not merged :)
>
[Attachment #3 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
line-break: after-white-space;" class="">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.<div class=""><br class=""></div><div class="">My only \
question is whether to skip over gcc8-12, or include them.</div><div class=""><br \
class=""></div><div class="">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.</div><div \
class=""><br class=""></div><div class="">And then — no more worries. Existing \
macports base infrastructure will just work as it is. Some fairly minor tweaking of \
what compilers are available on which systems will be done.</div><div class=""><br \
class=""></div><div class="">If we have to fix all the gcc versions between gcc8 and \
12 — well that will take a bit more time to fix and to build.</div><div \
class=""><br class=""></div><div class="">For Riccardo's bug, we always knew the gcc \
JIT was fragile on 32 bit systems. It probably needs to be disabled there by tweaking \
this block in the gcc8 Portfile:</div><div class=""><br class=""></div><div \
class=""><pre style="font-variant-ligatures: normal; orphans: 2; widows: 2; \
text-decoration-thickness: initial; overflow-wrap: break-word; white-space: \
pre-wrap;" class="">if {${subport} eq "gcc8"} {
# the jit is not building on i386 systems
# see <a href="https://trac.macports.org/ticket/61130" \
class="">https://trac.macports.org/ticket/61130</a> if {${build_arch} ne "i386"} {
lappend gcc_configure_langs jit
}
}</pre><div class=""><br class=""></div></div><div class="">Maybe that's all it \
needs.</div><div class=""><br class=""></div><div class=""><br class=""></div><div \
class=""><br class=""></div><div class=""><br class=""></div><div \
class="">Ken</div><div class=""><br class=""></div><div class=""><br \
class=""></div><div class=""><br class=""></div><div class=""><div><br \
class=""><blockquote type="cite" class=""><div class="">On Mar 29, 2024, at 4:50 AM, \
Sergio Had <<a href="mailto:vital.had@gmail.com" \
class="">vital.had@gmail.com</a>> wrote:</div><br \
class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" \
content="text/html; charset=utf-8" class=""><div style="overflow-wrap: break-word; \
-webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div \
class="">Well, the PR is either merged or not merged :)</div><div class=""><br \
class=""></div></div></div></blockquote></div><br class=""></div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic