On 14 August 2018 at 18:44, Michele Denber <1785...@bugs.launchpad.net> wrote: > On 08-14-2018 4:42 AM, Peter Maydell wrote: >> >> We do assume a posix shell and that that shell is /bin/sh. >> We may have bugs where we assume non-posix behaviour >> from it, since almost all users are going to be on systems >> where /bin/sh is bash or dash or whatever the BSD /bin/sh is. > Apparently Solaris is different in that regard (among others).
Yeah. I'm not sure how much I care about supporting OSes that decide to be totally different from everybody else, to be honest. It's the 21st century and POSIX is a thing. >> (dtc is a sort-of-third-party module, not part of QEMU >> proper.) > I notice in the Makefile in dtc/ that it's calling python. My default > python is 2.6.9. Our Python requirement is 2.7, and configure should check that. If you're telling configure --python=/some/nondefault/python then I guess the problem is we're not passing that on to dtc's build process. > Or is this dtc stuff really necessary? It is necessary, but only for certain guest CPU types. You can disable it by passing configure both "--disable-fdt" and also "--target-list=<some list of targets which doesn't include any arm, ppc, mips, microblaze or riscv targets>" (for instance "--target-list=x86_64-softmmu".) thanks -- PMM
