libgcc12: build failure: error: use of undeclared identifier 'PTR'

[i0ntempest]

This is on macOS 13 with Xcode/CLT 14.1 RC. I think there's a conflict with another port somewhere, because on another one of my macs with a lot fewer ports installed, libgcc12 was able to be built.

:info:build /usr/bin/clang -arch x86_64 -c -DHAVE_CONFIG_H -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/work/gcc-12.2.0/libiberty/../include  -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -Wshadow=local -pedantic  -D_GNU_SOURCE  /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/work/gcc-12.2.0/libiberty/lrealpath.c -o lrealpath.o
:info:build checking for vfork... /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/work/gcc-12.2.0/libiberty/objalloc.c:95:18: error: use of undeclared identifier 'PTR'
:info:build   ret->chunks = (PTR) malloc (CHUNK_SIZE);
:info:build     

[kencu (Ken)]

I think someone noted something like this when binutils was installed.

[i0ntempest]

binutils it is. Should we add it into gcc port file as a build conflict?

[kencu (Ken)]

I can't, unfortunately, think of anything more elegant to do about it.

But who knows how many ports might be affected by this? Could be many. It would be kinda nice to see just what is pulling that binutils header and if we could, figure how to stop that from happening for all of them....

so for now conflicting the ones we do find is all I can come up with.

[i0ntempest]

In 4bb33070d9d7f3676d395a90342ea0be4efd18e0/macports-ports (master):

gcc12: declare build conflict with binutils

Closes: #66062

[jmroot (Joshua Root)]

Installing binutils in a separate prefix might be the approach to use to stop things from accidentally using it.

[cooljeanius (Eric Gallager)]

Replying to jmroot:

Installing binutils in a separate prefix might be the approach to use to stop things from accidentally using it.

Yeah, cross-referencing against #37921 which was kind of about the same thing