[MacPorts] #59951: ossp-uuid +perl5_26: fatal error: 'sys/types.h' file not found (was: ossp-uuid +perl5_26 fails to build on Catalina 10.15)

MacPorts noreply at macports.org
Thu Jan 16 15:13:58 UTC 2020


#59951: ossp-uuid +perl5_26: fatal error: 'sys/types.h' file not found
------------------------+----------------------
  Reporter:  essandess  |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  catalina
      Port:  ossp-uuid  |
------------------------+----------------------
Changes (by ryandesign):

 * cc: ryandesign (removed)
 * keywords:   => catalina


Comment:

 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 [comment:5 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/59951#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list