socat @1.8.0.0 fails to build with ccache

[emrecio]

Specifically procan.o fails with makefile redefining CC in the makefile on procan.c

ccache /usr/bin/clang -pipe -I/opt/local/libexec/openssl3/include -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk -arch arm64 -D_GNU_SOURCE -Wall -Wno-parentheses  -DHAVE_CONFIG_H -I. -I/opt/local/libexec/openssl3/include -isystem/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk -c -D CC=\"ccache /usr/bin/clang\" -o procan.o procan.c
clang: error: no such file or directory: '/usr/bin/clang"'
gmake: *** [Makefile:113: procan.o] Error 1

In the makefile

procan.o: procan.c
    $(CC) $(CFLAGS) -c -D CC=\"$(CC)\" -o $@ procan.c

Remove « -D CC=\"$(CC)\" » from line 113 in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_socat/socat/work/socat-1.8.0.0/Makefile

Rerun make from that directory

cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_socat/socat/work/socat-1.8.0.0
make

Rerun « sudo port install socat »

How does that CC get in there, and just remove it?

[ryandesign (Ryan Carsten Schmidt)]

Replying to emrecio:

How does that CC get in there,

It's there in Makefile.in as distributed by socat's developers.

and just remove it?

If you've confirmed that removing it fixes the problem, then yes, you should suggest to the developers of socat that they remove that.