On Thu, Jul 5, 2018 at 11:31 AM, Liviu Ionescu <i...@livius.net> wrote: > If this is really a problem I guess you can blacklist it somehow. > But this proves once again that Linux native compilers and cross embedded > toolchains should be processed differently.
It isn't a major problem. There is the issue that the more different configure triplets we have the more work I need to do to keep them all working. So from my viewpoint, I'd rather not have riscv-*, but now that we have it, I can fix the gcc config.sub to make it work. On the linux side, the expectation is that everyone will be using riscv64-linux, and we don't have any usable upstream riscv32-linux support yet, so there isn't any problem (yet). Jim
