>> Your patch dealt with board/multilib_flags, but the same problem exists >> for board/cflags and many other flag-containing options. > > What's the use case for that? IIUC board flags are supposed to be ones > that are absolutely required for executables to run with a given board, > such as multilib selection, special linker scripts, non-standard run-time > library paths, etc. These must not be overridden by test cases or they > will inevitably fail.
We want to build most bpf-unknown-none test files with -mxbpf, but not all. I wasn't aware of the "absolutely require" nature of the board flags... then it is clear we need to find another strategy, like specifying it in the individual test files/dg-options.
