whatmask @1.2: error: unknown type name 'uint32'

[breiter (Brian Reiter)]

The gist of the error appears to be uint32 is not a defined type in the macOS 11 SDK.

whatnet.c:61:2: error: unknown type name 'uint32'; did you mean 'uint32_t'?
        uint32          myIp,           /* ip address */
        ^~~~~~
        uint32_t
/Library/Developer/CommandLineTools/SDKs/MacOSX11.1.sdk/usr/include/_types/_uint32_t.h:31:22: note: 'uint32_t' declared here
typedef unsigned int uint32_t;
                     ^
1 warning and 15 errors generated.
1 warning and 14 errors generated.
whatnet.c:76:2: error: unknown type name 'uint32'; did you mean 'uint32_t'?
        uint32          usableIps;      /* number of usable ips addresses */
        ^~~~~~
        uint32_t

This patch to blacklist XCode clang in macOS Big Sur fixed it for me.

--- Portfile.orig	2020-12-18 10:38:09.000000000 +0200
+++ Portfile	2020-12-18 10:50:11.000000000 +0200
@@ -4,7 +4,7 @@
 
 name            whatmask
 version         1.2
-revision        1
+revision        2
 platforms       darwin
 categories      net
 license         GPL-2+
@@ -37,6 +37,12 @@
                 sha256  7dca0389e22e90ec1b1c199a29838803a1ae9ab34c086a926379b79edb069d89 \
                 size    170183
 
+
+# don't use the xcode compiler on Big Sur
+if {${os.major} > 15} {
+    compiler.blacklist clang
+}
+
 configure.args  --mandir=${prefix}/share/man
 
 post-destroot {

[ryandesign (Ryan Carsten Schmidt)]

Thank you for reporting the issue but we do not want to blacklist clang, nor would increasing the revision be necessary when fixing a build failure. There will be a way to fix this port so that it can build with Xcode clang and we should seek that solution instead.

[ryandesign (Ryan Carsten Schmidt)]

In c2b524ae5a5a16185f848b937e492d12c0e383df/macports-ports (master):

whatmask: Fix implicit declaration of functions

Closes: #61859