Changes between Initial Version and Version 1 of Ticket #60169, comment 6
- Timestamp:
- Mar 9, 2020, 3:19:26 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #60169, comment 6
initial v1 5 5 Deselcting any llvm like this {{{sudo port select llvm none}}} also fixes the universal build. 6 6 7 It appears that {{{llvm-ar}}} is being found if present, and if it's not universal,the build errors out. If {{{llvm-ar}}} is not found, {{{meson}}} falls back to {{{ar}}} it seems, and that works.7 It appears that {{{llvm-ar}}} is being found if present, and the build errors out. If {{{llvm-ar}}} is not found, {{{meson}}} falls back to {{{ar}}} it seems, and that works. 8 8 9 9 note: … … 15 15 [5/74] rm -f droute/libdroute.a && ar csr droute/libdroute.a 'droute/8dce163@@droute@sta/droute.c.o' 'droute/8dce163@@droute@sta/droute-variant.c.o' 'droute/8dce163@@droute@sta/droute-pairhash.c.o' 16 16 }}} 17 18 I had thought that selecting an llvm that was installed +universal might work, but surprisingly to me, it still errored out, so perhaps there is more sleuthing to do to see why that failed. 19 20 For now, having an {{{llvm-ar}}} of any kind on the PATH seems to cause universal builds to fail.