Opened 5 years ago
Last modified 5 years ago
#59084 assigned defect
nghttp2 does not build since updating to Xcode 11
Reported by: | ksze (Kal Sze) | Owned by: | Schamschula (Marius Schamschula) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.0 |
Keywords: | xcode11 | Cc: | |
Port: | nghttp2 |
Description
macOS Mojave 10.14.6 MacPorts 2.5.4 or 2.6.0 (both versions tried) Xcode 11
Like the title says, nghttp2 fails to build since updating to Xcode 11.
$ port installed nghttp2 The following ports are currently installed: nghttp2 @1.39.2_1+python37 (active)
$ sudo port upgrade nghttp2 ---> Computing dependencies for nghttp2 ---> Fetching archive for nghttp2 ---> Attempting to fetch nghttp2-1.39.2_2+python37.darwin_18.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/nghttp2 ---> Attempting to fetch nghttp2-1.39.2_2+python37.darwin_18.x86_64.tbz2 from http://kmq.jp.packages.macports.org/nghttp2 ---> Attempting to fetch nghttp2-1.39.2_2+python37.darwin_18.x86_64.tbz2 from http://nou.nc.packages.macports.org/pub/macports/packages.macports.org/nghttp2 ---> Fetching distfiles for nghttp2 ---> Verifying checksums for nghttp2 ---> Extracting nghttp2 ---> Applying patches to nghttp2 ---> Configuring nghttp2 ---> Building nghttp2 Error: Failed to build nghttp2: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_nghttp2/nghttp2/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Log attached.
Attachments (1)
Change History (7)
Changed 5 years ago by ksze (Kal Sze)
Attachment: | nghttp2_build.log added |
---|
comment:1 Changed 5 years ago by jmroot (Joshua Root)
Owner: | set to Schamschula |
---|---|
Status: | new → assigned |
comment:2 Changed 5 years ago by jmroot (Joshua Root)
Looks like the same underlying problem as #58659.
comment:3 Changed 5 years ago by Schamschula (Marius Schamschula)
Unfortunately, there are some issues with Xcode 11 under Mojave.
comment:4 Changed 5 years ago by jmroot (Joshua Root)
The build system needs to pass along CFLAGS in the environment when running setup.py, since it contains the correct -isysroot flag.
comment:5 Changed 5 years ago by mf2k (Frank Schima)
Keywords: | xcode11 added; build mojave xcode removed |
---|
comment:6 Changed 5 years ago by miken32 (Michael Newton)
It's trying to find header files in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
but MacOSX10.15.sdk
is the only one bundled with XCode 11. Before that failed command it is using /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk
without issue.
Worked around this by doing this:
sudo ln -s /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
build log