[MacPorts] #65887: clang-15 builds for multiple archs even without the universal variant which fails

MacPorts noreply at macports.org
Fri Sep 23 12:25:02 UTC 2022


#65887: clang-15 builds for multiple archs even without the universal variant which
fails
-------------------------+-----------------------
  Reporter:  ryandesign  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.7.2
Resolution:              |   Keywords:  elcapitan
      Port:  llvm-15     |
-------------------------+-----------------------

Comment (by ryandesign):

 Replying to [comment:1 cjones051073]:
 > Compilers are a bit different to regular ports, in that its normal for a
 single platform build of a compiler to support targeting multiple
 architectures. So the above is actually expected, its normal for the
 compiler to support targeting i386, within a x86_64 build of the compiler,
 to support cross compilation.

 Certainly...

 > Note though, its not clear if the message above is a red-herring for
 legacy-support, as it anyway doesn't provide
 `__dyld_get_shared_cache_range`. The warning is just saying its ignored
 the static lib, not that it would actually have helped.

 Ah, you are probably right that I have mistakenly attributed the problem
 to legacysupport.


 Replying to [comment:2 cjones051073]:
 > b.t.w. we have had issues with i386 support in the llvm-devel builds.
 Which is why we have
 >
 > https://github.com/macports/macports-
 ports/blob/e3d8b60d1feaa6cc3794460ee139a74243900d9b/lang/llvm-
 devel/Portfile#L131
 >
 > It might be something similar is needed with llvm-15..

 I don't think that's relevant exactly, since changing `supported_archs`
 would just prevent MacPorts from requesting that the port be built for
 i386, but as I said, in this case, the build system has decided to build
 for i386 all on its own without MacPorts' involvement.

 There is a note at the bottom of the llvm-12 Portfile that may be relevant
 however?
 {{{
 # Note 1:

 # lldb-12 build fails on 10.11 with this link error at 98% of the build:
 #Undefined symbols for architecture x86_64:
 #  "__dyld_get_shared_cache_range", referenced from:
 #
 lldb_private::HostInfoMacOSX::GetSharedCacheImageInfo(llvm::StringRef) in
 liblldbHostMacOSXObjCXX.a(HostInfoMacOSX.mm.o)
 #  "__dyld_get_shared_cache_uuid", referenced from:
 #
 lldb_private::HostInfoMacOSX::GetSharedCacheImageInfo(llvm::StringRef) in
 liblldbHostMacOSXObjCXX.a(HostInfoMacOSX.mm.o)
 #  "_dyld_shared_cache_iterate_text", referenced from:
 #
 lldb_private::HostInfoMacOSX::GetSharedCacheImageInfo(llvm::StringRef) in
 liblldbHostMacOSXObjCXX.a(HostInfoMacOSX.mm.o)

 # This appears related to this commit in the lldb build tree, which would
 appear to be non-trivial to work around:
 # https://github.com/llvm/llvm-
 project/commit/8113a8bb793453832301e2684dc2b8cebec331b0
 # building against a newer SDK may or may not be an option for someone
 motivated to have lldb-12 on < 10.12
 }}}

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


More information about the macports-tickets mailing list