On Fri, Apr 18, 2025 at 5:07 PM Ryan Carsten Schmidt < [email protected]> wrote:
> On Apr 18, 2025, at 14:46, Dave Allured - NOAA Affiliate wrote: > > David, please apply this fix for PostgreSQL 16/17. I am tripping over > this while trying to fix https://trac.macports.org/ticket/72215, the > certsync problem, which itself is breaking other things. Thank you. > > Maybe I missed it... what fix are you proposing? > Ryan, for trac #72215, certsync, I am proposing only the workaround that you suggested there. "change postgresql16 and postgresql17 to match the other ports and to avoid the base bug". I am not addressing the base issue that was mentioned. This will not pass CI until strchrnul is fixed. https://github.com/Dave-Allured/macports-ports/commit/d16afa579a8de34ad7aa3b41d560a89fb51bf7e0 > On Tue, Apr 8, 2025 at 2:04 PM Ryan Carsten Schmidt wrote: > >> On macOS 15, MacPorts will set MACOSX_DEPLOYMENT_TARGET to 15.0. Similar >> for any other macOS version. (The minor macOS version is not included in >> the deployment target.) > > > > On Tue, Apr 8, 2025 at 11:03 AM David Gilman wrote: > >> Note that macOS 15.4 added strchrnul to the C standard library. It's >> behind the MACOSX_DEPLOYMENT_TARGET of 15.4 or greater, however, in at >> least some cases a configure script could find strchrnul only to have >> failures at build time when MACOSX_DEPLOYMENT_TARGET is defined. If >> there are any ports, or the builders/the port system itself is >> definining MACOSX_DEPLOYMENT_TARGET to 15.0 they are at risk of >> tripping this when building on 15.4. >> >> This happened in PostgreSQL, there is a patch to their configure.ac >> and a discussion here. >> >> https://www.postgresql.org/message-id/flat/E1tziZ6-002AW9-2C%40gemulon.postgresql.org >> I can fix the issue in the PostgreSQL ports in MacPorts but giving you >> all a notice if you see it elsewhere. >> >
