From: Stefan Weil <weil@mail.berlios.de>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Build failure on mingw / make: *** [config-all-devices.mak] Error 2
Date: Thu, 19 Nov 2009 21:30:01 +0100 [thread overview]
Message-ID: <4B05AAC9.9010007@mail.berlios.de> (raw)
In-Reply-To: <8BC583767FC2436797B051E8CA19E86D@FSCPC>
Sebastian Herbszt schrieb:
> v0.11.0-rc0-1677-gf165b53
>
> $ ./configure --target-list=i386-softmmu
> $ make
> Makefile:427: no file name for `-include'
> /bin/sh.exe: -c: line 1: unexpected EOF while looking for matching `"'
> /bin/sh.exe: -c: line 2: syntax error: unexpected end of file
> make: *** [config-all-devices.mak] Error 2
>
> - Sebastian
I just sent a patch which should fix this problem. See
[PATCH] Fix build for mingw32 on windows ($$ expansion)
Regards,
Stefan
next prev parent reply other threads:[~2009-11-19 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 20:21 [Qemu-devel] Build failure on mingw / make: *** [config-all-devices.mak] Error 2 Sebastian Herbszt
2009-11-19 20:30 ` Stefan Weil [this message]
2009-11-19 20:38 ` Sebastian Herbszt
2009-11-19 20:46 ` Stefan Weil
-- strict thread matches above, loose matches on Subject: below --
2009-11-19 20:42 Sebastian Herbszt
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=4B05AAC9.9010007@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=herbszt@gmx.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).