[MacPorts] #69153: prelude-manager @5.2.0: clang: error: unknown argument: '-80fd-11ee-8227-6aecfccc70fe/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.Internal.sdk/System/Library/Frameworks/'

MacPorts noreply at macports.org
Mon Jan 22 05:16:30 UTC 2024


#69153: prelude-manager @5.2.0: clang: error: unknown argument: '-80fd-
11ee-8227-6aecfccc70fe/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.Internal.sdk/System/Library/Frameworks/'
------------------------------+-------------------------------------
  Reporter:  ryandesign       |      Owner:  ctreleaven
      Type:  defect           |     Status:  accepted
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.8.1
Resolution:                   |   Keywords:  monterey ventura sonoma
      Port:  prelude-manager  |
------------------------------+-------------------------------------
Changes (by ryandesign):

 * keywords:  ventura sonoma => monterey ventura sonoma


Comment:

 I also see `-iwithsysroot /usr/local/libressl/include` and
 `-I/usr/local/include` in the log which we do not want.

 I see that this is happening when building the bundled version of libev.
 Could we use the MacPorts libev port instead?

 I see the same problem on my macOS 12 system:

 {{{
 clang: error: unknown argument: '-3cda-11ee-b8ac-
 16228a05f5d2/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.7.Internal.sdk/System/Library/Frameworks/'
 }}}

 however we had successful builds on macOS 12 on the buildbot back in March
 2022 so maybe something has changed with the dependencies.

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


More information about the macports-tickets mailing list