Apologies if I am mis-reading this request… My trust in the macports pre-built binaries is because it is my understanding / belief that they are built by the build bots. I would be uncomfortable with an externally built binary, on an unknown machine, being pushed into the macports distribution.
-Frank > On Jul 30, 2025, at 4:45 AM, Gagan Sidhu via macports-dev > <[email protected]> wrote: > > > Anybody? Please? > > > Thanks, > Gagan > > Sent from my (Inferior Android) BlackBerry—the (second-)most secure mobile > device—via the Rogers Network. Long Live QNX > > > > Original Message > > > From: [email protected] > Sent: July 23, 2025 8:35 PM > To: [email protected] > Reply to: [email protected] > Subject: PR 28819/28834 review > > > https://github.com/macports/macports-ports/pull/28834 > https://github.com/macports/macports-ports/pull/28819 > > need someone to review these PRs. > > clang doesn't finish within the 6 hour timer, but will build and work > properly on 10.6+ for intel macs if someone decides to evaluate it. > -it takes about 2 hours in a 10.6 VM with 16 cores and 16GB of ram. > > would appreciate pushing these, though i'm not sure how buildbot will distill > the PRs to ready-made libraries for macports-libcxx, which will spare the > leechers from having to endure what i have in testing and building the > compiler (probably) 30+ times.
