> On 24 Mar 2026, at 7:09 pm, Riccardo Mottola <[email protected]> > wrote: > > Hi, > > Sergey Fedorov wrote: >> Well, I can be wrong about MacPorts defaults here, but from the log in the >> original report shows that libc++ headers are used: >> /opt/local/libexec/gcc15/libc++/include/c++/v1 >> Perhaps it was locally configured that way then. >> >> In any case, my point was that the cause of the error is libc++’s headers, >> not gcc as such. > > I didn't "force" anything except the compiler. Indeed, it is interesting for > gcc15 to pick up other headers and then dying.. perhaps something else in the > port file hints to it. Will check... if then it would be a mismatch against > rebuilt gpgmepp
Its completely intentional. When building gcc with support for libc++ you are required to supply the libc++ headers to be used yourself. This is what the gcc ports do via the gccX-libcxx subports https://github.com/macports/macports-ports/blob/df439d72d132dabd56258c597027d2d69ddb7a41/lang/gcc15/Portfile#L267 Gcc really offers no guidance on what version they support, so it’s completely hit or miss as to what works here. > > as said, this is a rather clumsy attempt to see if that is the only poppler > issue, but apparently it causes more trouble than it is worth. > > -R
