On Tue, Nov 19, 2019 at 11:11:39PM +, Maciej W. Rozycki wrote:
> Why do you think it is important that it is only the relevant (i.e.
> `riscv*') targets that the directory providing newly-built libatomic is
> pointed at ?
Such changes don't happen every day, no other port added it similarly
Add flags to find libatomic in build-tree testing, fixing a catastrophic
libgomp testsuite failure with targets such as `riscv-linux-gnu' that
imply `-latomic' with the `-pthread' GCC option, implied in turn by the
`-fopenacc' and `-fopenmp' options, removing failures like:
.../bin/riscv64-linu
