> On Mar 12, 2024, at 19:46, Dave Allured wrote:
>
>
> I am getting an unusual builder error that is blocking my recent port update
> on all of the builders. Go to console view on build.macports.org, find port
> `gjs-devel`, and look at the stdio logs below the commit message.
>
> `fatal:
I am getting an unusual builder error that is blocking my recent port
update on all of the builders. Go to console view on build.macports.org,
find port `gjs-devel`, and look at the stdio logs below the commit message.
`fatal: unable to access '
> On Mar 13, 2024, at 4:07 AM, René J.V. Bertin wrote:
>
>> Building against libstdc++ is broken for Intel
>
> Not from what I can tell; I test built an OLD libxmlxx copy against libstdc++
> from GCC13 and that works.
What I rather meant is that Macports cannot handle that properly, since
On Wednesday March 13 2024 03:44:17 Sergio Had wrote:
>Which OS are we talking about?
10.9.5 but that what matters here is that it's a libc++-based OS version.
>Building against libstdc++ is broken for Intel
Not from what I can tell; I test built an OLD libxmlxx copy against libstdc++
from
Which OS are we talking about?
Building against libstdc++ is broken for Intel and arm64, I believe, though it
should be fixable. But the problem is not passing the flag, but broken Apple
headers, it seems.
I managed to build some ports like CMake and a few others against libstdc++ on
Sonoma
Hi,
I've been tinkering a bit with a personal GCC12 build patched to use libc++ by
default, and now find myself unable to build against libstdc++.
`configure.cxxflags-append -stdlib=libstdc++` appears to be filtered out
somewhere in the "base" bowels, and `configure.cxx_stdlib libstdc++`
On Mar 12, 2024, at 10:00, Jonathan Stickel wrote:
>
> command not found: jlpm
>
> Recommendations for how to resolve this issue?
One solution is to figure out where this program is being called in the source
code, then patch it to use the program name as it appears in MacPorts (e.g. in
this
I think I may have run into a similar issue with how tests have
changed in CI with 2.9.x MacPorts and the OpenSSH 9.7p1 PR I submitted
yesterday:
https://github.com/macports/macports-ports/pull/22981
Going back to reverting to 9.6p1 locally and running port -d -v test I
see that it fails with
I'm trying to update the port `py-jupytext` since the recent updates to
Jupyterlab. The jupytext package now uses node.js and jlpm to build. The
port `py-jupyterlab` provides jlpm, but it is in the path as
`jlpm-{python.branch}`, and consequently jupytext cannot find it. I
tried patching
