Opened 2 years ago
Closed 2 years ago
#65757 closed defect (fixed)
libtapi: builds failing for earlier macOS releases: ARM bits inadvertently included for Intel build?
Reported by: | mascguy (Christopher Nielsen) | Owned by: | catap (Kirill A. Korinsky) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.2 |
Keywords: | Cc: | ||
Port: | libtapi |
Description
It almost looks as if ARM-related bits, are being used for Intel. Unless this is supposed to be in play, for cross-compilation support?
In file included from libtapi/work/apple-libtapi-b7b5bdbfda9e8062d405b48da3b811afad98ae76/src/llvm/lib/Support/AArch64TargetParser.cpp:35: libtapi/work/apple-libtapi-b7b5bdbfda9e8062d405b48da3b811afad98ae76/src/llvm/include/llvm/Support/AArch64TargetParser.def:82:18: error: no viable conversion from 'const char [11]' to 'llvm::StringLiteral' AARCH64_CPU_NAME("cortex-a35", ARMV8A, FK_CRYPTO_NEON_FP_ARMV8, false, ^~~~~~~~~~~~ libtapi/work/apple-libtapi-b7b5bdbfda9e8062d405b48da3b811afad98ae76/src/llvm/lib/Support/AArch64TargetParser.cpp:34:9: note: expanded from macro 'AARCH64_CPU_NAME' .Case(NAME, ARM::DEFAULT_FPU) ^
There is also the following, which appears arch-independent:
In file included from libtapi/work/apple-libtapi-b7b5bdbfda9e8062d405b48da3b811afad98ae76/src/llvm/include/llvm/Support/Chrono.h:14: libtapi/work/apple-libtapi-b7b5bdbfda9e8062d405b48da3b811afad98ae76/src/llvm/include/llvm/Support/FormatProviders.h:267:25: error: no viable conversion from 'const char [2]' to 'llvm::StringLiteral' .Case("Y", B ? "YES" : "NO") ^~~
It's not yet clear how wide-spread this is, as the buildbots are still catching up. But it's a definite issue for 10.9:
Change History (3)
comment:1 Changed 2 years ago by mascguy (Christopher Nielsen)
comment:3 Changed 2 years ago by catap (Kirill A. Korinsky)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Also failing for macOS 10.8, though with different errors:
https://build.macports.org/builders/ports-10.8_x86_64-builder/builds/101095/steps/install-port/logs/stdio