William.Hatheway
Well-known member
Hi all,
While building WRF with AOCC (flang/clang), I ran into a linker failure caused by a misspelling in the AOCC stanza that ends up in configure.wrf.
In my generated configure.wrf, the AOCC stanza contained this flag in AMDLDFLAGS:
-vectorize-noncontigous-memory-aggressively (missing the u in “contiguous”).
When WRF hits a link step that uses AMDLDFLAGS, ld.lld errors out with an “unknown argument” message, and suggests the correctly spelled option.
Quick workaround (post-config patch):
sed -i 's/vectorize-noncontigous-memory-aggressively/vectorize-non-contiguous-memory-aggressively/g' configure.wrf
Better long-term fix:
Update the corresponding AOCC stanza in arch/configure.defaults so new configure.wrf files are generated correctly on every ./configure.
If anyone else is using AOCC, this typo can be easy to miss because you may not hit the failing link path immediately, but it will break later in the build when those linker flags are applied.
Thanks!
@islas @kwerner @dudhia @mgduda
While building WRF with AOCC (flang/clang), I ran into a linker failure caused by a misspelling in the AOCC stanza that ends up in configure.wrf.
In my generated configure.wrf, the AOCC stanza contained this flag in AMDLDFLAGS:
-vectorize-noncontigous-memory-aggressively (missing the u in “contiguous”).
When WRF hits a link step that uses AMDLDFLAGS, ld.lld errors out with an “unknown argument” message, and suggests the correctly spelled option.
Quick workaround (post-config patch):
sed -i 's/vectorize-noncontigous-memory-aggressively/vectorize-non-contiguous-memory-aggressively/g' configure.wrf
Better long-term fix:
Update the corresponding AOCC stanza in arch/configure.defaults so new configure.wrf files are generated correctly on every ./configure.
If anyone else is using AOCC, this typo can be easy to miss because you may not hit the failing link path immediately, but it will break later in the build when those linker flags are applied.
Thanks!
@islas @kwerner @dudhia @mgduda
Last edited: