sorry to sound impatient, but would someone mind running the buildbot on my pull request (nodejs) again?
it should check out fine this time. i had no idea newer OS X versions had issues with without these flags as well. Thanks, Gagan > On Sep 29, 2024, at 2:44 PM, Gagan Sidhu <[email protected]> wrote: > > (sorry for the dupe email ryan) > > “how do i do that?” (submit a pull request) lol i remember our beloved ppc > crank barracuda told me to do the same thing for folly and i didn’t know how. > > i’m just kidding on expecting you to answer that here though, as i > know/hope/suspect bing will tell me how to do it. > - and i’m pretty sure you guys will have some documentation, probably > from like 20 years ago (and is still probably current haha) that explains how > to do it. > > but yes i think my proposed changes for nodejs14-nodejs18 should probably be > upstreamed sooner rather than later. > > i want to test on nodejs19+ but i’m super-paranoid after moving from a MacPro > 5,1 (velociraptor raid) to an iMacPro, and don’t want to incur another > \gtrsim 150gigs (maybe more, probably more) from building. > > even though smartctl tells me i have 99% life, i’ve used a few terabytes in > the couple of weeks from going hard on firefox and also rebuilding node a few > times (filled my VM disk as the build files showed haha) > > so i am planning to get a sata ssd to ease that, and i wanted to test my > changes by building them once-over to be sure before the upstream. > > Thanks, > Gagan > >> On Sep 29, 2024, at 2:28 PM, Ryan Carsten Schmidt <[email protected]> >> wrote: >> >> On Sep 29, 2024, at 07:13, Gagan Sidhu wrote: >> >>> you are correct that users are able to build “any software you want”, but >>> only with some involved _EDITS_ of the _CURRENT_ portfiles of the >>> aforementioned ports. >> >>> are we expecting the macports user to know how to do all of this? >> >>> with some maintenance of existing portfiles for popular software, i think >>> macports popularity could increase significantly >> >> Certainly it is not expected for *every user* to need to know how to build a >> given piece of software. The whole point of MacPorts is that only *one user* >> needs to figure it out. They encode that knowledge into a portfile so that >> then every other user can build that software by just asking MacPorts to do >> it. So if you know of any problem in any port and know how to fix it, please >> submit a pull request so that everyone can benefit. That's how this whole >> thing works. Nothing gets done unless someone contributes it. >> >> >
