The shell-based tracetool has been replace in commit 650ab98d1d9551f0ca21 with a script that has been implemented in Python, so I think we can close this bug nowadays.
** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/636315 Title: configure and build errors on Solaris 10 due to /bin/sh usage Status in QEMU: Fix Released Bug description: Running `LANG=C LC_ALL=C ./configure --prefix=... --install=/usr/ucb/install` on Solaris 10 amd64 results in the following errors: ./configure: bad substitution ./configure: !: not found ./configure: curl-config: not found ./configure: curl-config: not found Error: invalid trace backend Please choose a supported trace backend. Unfortunately it doesn't print the line numbers of the errors. It must be somewhere after the check for `install`. The first few can be resolved by running `bash ./configure ...` instead. The "check if trace backend exists" hardcodes `sh "$source_path/tracetool" ...` in configure. Replacing sh with bash makes it work. `gmake` complains "Makefile:331: no file name for -include", which is a filter for *.d files. `create_config` gets the 'bad substitution' error as well. Replacing sh with bash in rules.mak works. etc. To sum it up, a) there are shell script incompatibilities with Solaris 10's /bin/sh shell, and b) hardcoding 'sh' in configure or Makefiles seems like a bad idea. QEMU Git 73d7434279e3905164afd02360eebe4b43c7fa (ESP: fix ESP DMA access...) $ uname -a SunOS sonnengoettin 5.10 Generic_142901-03 i86pc i386 i86pc # No banner output for /bin/sh $ bash --version GNU bash, version 3.00.16(1)-release (i386-pc-solaris2.10) Copyright (C) 2004 Free Software Foundation, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/636315/+subscriptions