Re: Recent events ...

Hey Ken, sorry to see you go. I wish you'd stay, but I get it, it's tough keeping these old machines working and is a thankless job. Best of luck to you! —Mark On Tue, Feb 4, 2025, at 12:44 PM, Ken Cunningham wrote: > First of all, I’ve been pretty strongly attacked, as you can see. > > Gagan h

Qt5 and 6 deployment target

According to this bug and comment: https://bugreports.qt.io/browse/QTBUG-128900?focusedId=823817&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-823817 The deployment target that Qt5/6 shoots for is macOS 12 - perhaps that's what we should standardize on for all m

Re: Any downside to turning off SIP in a VM?

I'll give that a try, since it's a throwaway-ish VM. —Mark On Fri, Oct 4, 2024, at 7:08 PM, Ken Cunningham wrote: > > On 2024-10-04, at 3:22 PM, Mark E Anderson wrote: > >> I thought that bug was related to SIP, but it doesn't seem to be. That's >

Re: Any downside to turning off SIP in a VM?

arsten Schmidt wrote: > > On Oct 4, 2024, at 15:57, Mark E Anderson wrote: >> >> Because I refuse to let qt5-qtwebengine beat me, I've been running macports >> in VMs to test what the heck is going on with patching ninja files. Trace >> mode will work bett

Any downside to turning off SIP in a VM?

Because I refuse to let qt5-qtwebengine beat me, I've been running macports in VMs to test what the heck is going on with patching ninja files. Trace mode will work better if I turn SIP off, correct? But if I do, will things succeed that should fail? Or should I worry about that later, since the

macOS 15 runner is available

Github seems to have a macOS 15 runner in beta, which might help out on our quest to squash macOS 15 bugs. Although, I have noticed the CI can be a little fickle when doing something big like qt. —Mark

Re: macOS 15 runner is available

Oof yeah I forgot about that part. I remember the days where everything just timed out. —Mark On Mon, Sep 30, 2024, at 7:51 PM, Ryan Carsten Schmidt wrote: > > On Sep 30, 2024, at 18:47, Mark E Anderson wrote: > > > > Github seems to have a macOS 15 runner in beta, which mig

Re: Weird lint behavior

rts, but one subport has to > change it back to 'darwin'. In general, lint warnings (as opposed to > lint errors) should not be assumed to mean that something is definitely > wrong. It's more like a suggestion to double check. > > - Josh > > On 21/9/202

Re: Weird lint behavior

Yep, here is one from a recent PR: https://github.com/macports/macports-ports/pull/25825/files no platforms line, but a bunch of warnings. —Mark On Fri, Sep 20, 2024, at 2:54 PM, Ryan Carsten Schmidt wrote: > > On Sep 20, 2024, at 13:49, Mark E Anderson wrote: > > > > Ye

Re: Weird lint behavior

rning. I think it's > trivial put that's where the warning comes from. > > [1]: > https://github.com/macports/macports-ports/pull/20062#issuecomment-1700057721 > > On Fri, Sep 20, 2024 at 2:07 PM Mark E Anderson wrote: >> __ >> I've been getting this

Weird lint behavior

I've been getting this error, in files that don't have a platform line. I assume this error is in a port group? My question is, is it the lint that's wrong or the portgroups? Warning: Unnecessary platforms line as darwin is the default Thanks, Mark

Re: Sequoia vs SuiteSparse

Yeah - clang 18 builds just fine on Sequoia - and it's got the OpenMP you'd need. Clang 17 is failing due to a weird overlapping symbol error that's broken from upstream. —Mark On Wed, Sep 18, 2024, at 8:10 AM, Chris Jones via macports-dev wrote: > > > I am puzzled as to why SuiteSparse_GraphB

Re: Caution: CLTs appear to be broken on Sequoia

Mine have been working - but I remember needing an update from Apple - also, I just got one yesterday, which means I was never using them, I was using Xcode maybe? —Mark On Tue, Sep 17, 2024, at 8:30 AM, Joshua Root wrote: > See for the details

Contribution question for macports stuff that isn't ports

For a few decades now, I've been pretty comfortable with how contributing to the ports aspect of MacPorts work, but I've recently looked at macports-base, macports-webapp, and macports-guide PRs and I have very little idea of how the PR process should work. I see a number of PRs open on base tha

Re: QT Problems on macOS 15

Side note - Fred, can you send me some ports where I can find the Float16 bug? —Mark On Sun, Aug 25, 2024, at 10:57 PM, Fred Wright wrote: > > On Thu, 15 Aug 2024, Mark E Anderson wrote: > > > Just a heads up, `CGDisplayCreateImageForRect` is no longer supported in >

Re: QT Problems on macOS 15

t work with types. > > Anyone with a paid developer account should feel free to file bugs about > those. Those of us who don't pay Apple for the privilege of telling them > what they're doing wrong don't have that option. > > On Fri, 16 Aug 2024, Mark E Anderson

AsciiDoc Guide Test Repo

With the help of pandoc, the old stuff that got deleted and just some elbow grease I was able to create a basic facsimile of the guide. It's in the same order with a table of contents. Default asciidoc styling and not a lot of real changes. Take a look if you're interested, I'm going to try and

Re: QT Problems on macOS 15

I do! I'll look into that. Yeah, I don't even have the 14 SDK on this machine since Xcode 15 won't run. Thanks, Mark On Fri, Aug 16, 2024, at 9:40 AM, Ryan Carsten Schmidt wrote: > > On Aug 15, 2024, at 16:58, Mark E Anderson wrote: >> >> One workaround sugg

QT Problems on macOS 15

Just a heads up, `CGDisplayCreateImageForRect` is no longer supported in the macOS 15 SDK. One workaround suggested was setting the minimum SDK to macOS 14 on macOS 15 - https://github.com/microsoft/vcpkg/issues/40372 I want to do this, but the qt Portfiles are beyond my understanding at the m

Re: Has this made it through?

to do some experimenting on the side first, because honestly I like the guide a lot and use it a ton, but my first crack at trying to add to it has been a bit of a slog. Mark On Sun, Aug 11, 2024, at 6:46 PM, Joshua Root wrote: > On 12/8/2024 06:59, Mark E Anderson wrote: > > Sorry for

Has this made it through?

Sorry for this, but my m...@macports.org email has been bouncing from the list with a weird error, so I've subscribed with another - I can still send and receive email from the the MacPorts email but not to the lists. *Things that bounced that I wanted to talk about:* 1. Giving the guide some l