Opened 5 years ago
Closed 5 years ago
#59376 closed defect (fixed)
x265 @3.2_0: unable to upgrade to 3.2_1, build error
Reported by: | thomasrussellmurphy (Thomas Russell Murphy) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.1 |
Keywords: | Cc: | ||
Port: | x265 |
Description
Similar to #59342. Appears to be a setup error with accessing 10.14 SDK resources.
Attachments (1)
Change History (12)
Changed 5 years ago by thomasrussellmurphy (Thomas Russell Murphy)
Attachment: | x265_3.2_1_failure.log added |
---|
comment:1 Changed 5 years ago by jmroot (Joshua Root)
Different to #59342. There it wasn't finding the right SDK, whereas here it find the SDK but can't parse the .tbd files.
comment:2 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
What variant of the ld64 port is installed? Try using the +ld64_xcode variant.
comment:3 Changed 5 years ago by thomasrussellmurphy (Thomas Russell Murphy)
I currently have ld64 @3_1 (active). ld64_xcode is the default variant; the other variants appear to be legacy checkpoints for compatibility with older OSs.
comment:4 Changed 5 years ago by mf2k (Frank Schima)
Error is:
:info:configure /opt/local/bin/clang-mp-9.0 -pipe -Os -DNDEBUG -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.14 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk CMakeFiles/cmTC_f788c.dir/testCCompiler.c.o -o cmTC_f788c :info:configure ld: unexpected token: !tapi-tbd-v3 file '/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib/libSystem.tbd' for architecture x86_64 :info:configure clang: error: linker command failed with exit code 1 (use -v to see invocation)
comment:5 Changed 5 years ago by kencu (Ken)
something local to your system, it appears:
$ sudo port -v destroot x265 ---> Computing dependencies for x265. ---> Fetching distfiles for x265 ---> x265_3.2.tar.gz does not exist in /opt/local/var/macports/distfiles/x265 ---> Attempting to fetch x265_3.2.tar.gz from https://distfiles.macports.org/x265 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1392k 100 1392k 0 0 943k 0 0:00:01 0:00:01 --:--:-- 943k ---> Verifying checksums for x265 ---> Checksumming x265_3.2.tar.gz ---> Extracting x265 ---> Extracting x265_3.2.tar.gz Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_x265/x265/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/x265/x265_3.2.tar.gz' | /usr/bin/tar -xf - ---> Configuring x265 Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_x265/x265/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.14" -DCMAKE_OSX_SYSROOT="/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_x265/x265/work/x265_3.2/source -- cmake version 3.15.4 -- The C compiler identification is Clang 9.0.0 -- The CXX compiler identification is Clang 9.0.0 -- Check for working C compiler: /opt/local/bin/clang-mp-9.0 -- Check for working C compiler: /opt/local/bin/clang-mp-9.0 -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done
perhaps check those ld64
parts again, as you seem to be getting an ld64
-related error in linking.
$ port -v installed x265 The following ports are currently installed: x265 @3.2_1 (active) platform='darwin 18' archs='x86_64' date='2019-10-21T20:29:04-0700'
comment:6 Changed 5 years ago by kencu (Ken)
I have:
$ port -v installed | grep ld64 ld64 @3_1+ld64_xcode (active) platform='darwin 18' archs='x86_64' date='2019-10-21T20:27:38-0700' ld64-xcode @2_1 (active) platform='darwin 18' archs='x86_64' date='2019-10-21T20:27:37-0700'
comment:7 Changed 5 years ago by thomasrussellmurphy (Thomas Russell Murphy)
$ port -v installed | grep ld64 ld64 @3_1 (active) platform='darwin 18' archs='x86_64' date='2018-11-29T20:56:22-0600' ld64-latest @274.2_2+llvm80 (active) platform='darwin 18' archs='x86_64' date='2019-07-08T21:25:23-0500' ld64-xcode @2_1 (active) platform='darwin 18' archs='x86_64' date='2019-08-26T16:57:37-0500'
comment:8 Changed 5 years ago by kencu (Ken)
so do this:
sudo port -f uninstall ld64 sudo port -v install ld64 +ld64_xcode
and you should be good to go.
comment:9 Changed 5 years ago by kencu (Ken)
BTW, IMHO, until Apple releases the full source code for the current ld64
with the tapi3
drop in it, we should just have ld64
be a "no-op" on Xcode 9+, installing a nothing file or similar.
This keeps happening to people over and over, and it's not terribly obvious how to fix it for folks...
Having said that, I know there will 10 responses why that is not going to happen, and so we'll just keep getting these tickets until ld64
gets a tapi3
drop from Apple. But anyway...
Edit: maybe there is some reason it can't happen -- macports-clang/llvm hardwiring in the ld64
path or something. I haven't looked into every aspect of this issue.
comment:10 Changed 5 years ago by thomasrussellmurphy (Thomas Russell Murphy)
That would be helpful, particularly to reduce ticket volume. I'll need to consult my other XCode-resource-error related tickets after this rev-upgrade
finishes to see if this fixed my other problems.
build failure log