From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Get sh right on OpenSolaris/SPARC
Date: Wed, 04 Mar 2009 22:30:33 +0100 [thread overview]
Message-ID: <49AEF2F9.7060400@mail.berlios.de> (raw)
In-Reply-To: <Pine.NEB.4.64.0903022047120.15645@otaku.freeshell.org>
Palle Lyckegaard schrieb:
>
> The patch below solves a problem when building qemu on OpenSolaris/SPARC.
>
> "feature_to_c.sh: test: argument expected"
>
> There seemes to be a problem with how "features_to_c.sh" is started
> from the makefile. On Solaris the shell in /bin/sh is not standards
> compliant according to
> http://docs.sun.com/app/docs/doc/816-5165/sh-1?a=view so the patch
> fixes the configure script so a proper sh in located in /usr/xpg4/bin
> when building on OpenSolaris. Other platforms defaults to whatever is
> in the path when configure is running.
>
> Please consider this patch so qemu builds out-of-the-box for
> OpenSolaris...
>
> Best regards
> Palle
>
> ------ start of patch
>
> Index: configure
> ===================================================================
> --- configure (revision 6657)
> +++ configure (working copy)
> @@ -34,6 +34,7 @@
> make="make"
> install="install"
> strip="strip"
> +shell="`which sh`"
>
> # parse CC options first
> for opt do
> @@ -263,6 +264,7 @@
> SunOS)
> solaris="yes"
> make="gmake"
> + shell="/usr/xpg4/bin/sh"
This shell is part of package SUNWxcu4. Is this a mandatory or optional
package?
If it is optional, many installations won't provide /usr/xpg4/bin/sh.
Regards
Stefan Weil
next prev parent reply other threads:[~2009-03-04 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 21:04 [Qemu-devel] [PATCH] Get sh right on OpenSolaris/SPARC Palle Lyckegaard
2009-03-04 21:30 ` Stefan Weil [this message]
2009-03-04 22:08 ` Anthony Liguori
2009-03-17 19:37 ` Palle Lyckegaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49AEF2F9.7060400@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).