Opened 5 years ago
Closed 4 years ago
#59305 closed defect (fixed)
cctools @921_4+llvm70: Looking for MacOSX 10.14 SDK within Xcode 11.0/11.1 on Mojave
| Reported by: | iqgrande | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.6.1 |
| Keywords: | Cc: | jmroot (Joshua Root), larryv (Lawrence Velázquez), SpikeLightfoot, kencu (Ken) | |
| Port: | llvm-7.0 |
Description
Greetings,
I tried building cctools and encountered errors where it could not find simple libraries like stdio.h because it was looking for MacOSX10.14.sdk which isn't there anymore since Xcode 11.0. I ended up creating a symlink to work around this (since the issue is similar to #59078) for the time being. However, the issue is still present. Thank you for all of your help with this.
=Workaround=
cd /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs sudo ln -s /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk MacOSX10.14.sdk
=Error=
clang: warning: no such sysroot directory: '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk' [-Wmissing-sysroot]
Kind regards, Anthony
Attachments (1)
Change History (8)
comment:1 Changed 5 years ago by jmroot (Joshua Root)
| Cc: | jmroot added; jeremyhu@… removed |
|---|---|
| Owner: | set to jeremyhu |
| Status: | new → assigned |
Changed 5 years ago by iqgrande
log from sudo port install cctools +llvm70
comment:2 Changed 5 years ago by iqgrande
I attached a log. It looks as if the problem may not occur with the default +llvm80 variant. I never specified +llvm70 upon initial installation (that must've been the default when it was installed as a dependency for something I wanted). Anyways, when I build without specifying +llvm70 and let it choose the default, it appears to build fine.
comment:3 Changed 5 years ago by jmroot (Joshua Root)
| Cc: | larryv added |
|---|---|
| Port: | llvm-7.0 added; cctools removed |
Ah, I remember seeing this before. The SDK path is coming from llvm-config-mp-7.0. Not sure if there was an existing ticket.
comment:4 Changed 5 years ago by kencu (Ken)
hopefully will be fixed by making sure commandline tools are installed on buildbot and revbumping (probably all of them!)
comment:5 Changed 5 years ago by SpikeLightfoot
| Cc: | SpikeLightfoot added |
|---|
comment:6 Changed 4 years ago by kencu (Ken)
| Cc: | kencu added |
|---|
comment:7 Changed 4 years ago by kencu (Ken)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This has been fixed by a revbump to llvm-7.0 after the command line tools were installed on all the buildbots:
llvm-config-mp-7.0 --cxxflags -I/opt/local/libexec/llvm-7.0/include -pipe -Os -std=c++11 -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -DNDEBUG -fno-exceptions -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
Attach the log please.