ossp-uuid +perl5_26: fatal error: 'sys/types.h' file not found

[essandess (Steve Smith)]

The standard port install ossp-uuid fails to build on Catalina 10.15.

Changing to perl 5.28 works:

sudo port install ossp-uuid +perl5_28

A bunch of ports have this as a dependency, so it breaks a bunch of migrated ports when running sudo ./restore_ports.tcl myports.txt from wiki:Migration

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log file showing how it failed.

[mf2k (Frank Schima)]

WFM

$ port -v installed ossp-uuid
The following ports are currently installed:
  ossp-uuid @1.6.2_11+perl5_28 (active) platform='darwin 19' archs='x86_64' date='2019-12-07T11:20:10-0700'

[mf2k (Frank Schima)]

+perl5_28 is the default variant. So I guess you are reporting that using +perl5_26 is failing.

[ryandesign (Ryan Carsten Schmidt)]

It builds fine for me with the +perl5_26 variant on High Sierra. If it fails on Catalina, please attach the main.log so that we can see what went wrong.

[loomiverse (Dennis)]

Attached main.log is taken after I added /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk as a symlink to /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

[ryandesign (Ryan Carsten Schmidt)]

The log says:

:info:build /usr/bin/clang -c  -I. -I.. -fno-common -DPERL_DARWIN -mmacosx-version-min=10.15 -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -fno-strict-aliasing -fstack-protector-strong -I/opt/local/include -DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  "-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
:info:build In file included from uuid.xs:30:
:info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
:info:build #include <sys/types.h>
:info:build          ^~~~~~~~~~~~~
:info:build 1 error generated.

This certainly doesn't sound like a problem specific to a variant of a port; it sounds like your headers are missing. But you say they aren't:

Replying to loomiverse:

Attached main.log is taken after I added /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk as a symlink to /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

I can't explain why the error would exist if you did that, nor why you had to do that; the command line tools installer should have installed the SDK as MacOSX10.15.sdk, and MacOSX.sdk should have been a symlink to it. We have had reports from other users whose SDK was installed as the unversioned MacOSX.sdk; we don't know why that happens for some users.

Maybe try uninstalling the command line tools (I don't know what the official/correct way is to do that) and then reinstall them.

I'm going to un-Cc myself since this is not my port and I don't know how to help further.

[djlambert (Derek J. Lambert)]

I also encountered this issue. I had to manually download the command-line tools for my version of Xcode and reinstall them.

​https://developer.apple.com/download/more/?=for%20Xcode

I presume this was because I waited upgrading to Catalina and had already updated Xcode.

[mouse07410 (Mouse)]

Immediately after upgrading the latest Mojave to Catalina, same experience as Derek had: re-installing CommandLineTools solved the problem. Somehow, the upgrade wiped out the SDKs subdirectory of the CommandLineTools.

[cignoni (Paolo Cignoni)]

Encountered the same issue and same error message (failing to build ossp-uuid) Also for me this was solved by reinstalling the CommandLineTools by launching from the command line:

xcode-select --install

[jmroot (Joshua Root)]

This seems a lot like a duplicate of #62440 / #62227.