Ping! Just ran into this bug today and noticed this
patch never got applied.
Patch still applies OK, patchwork url is:
http://patchwork.ozlabs.org/patch/178920/
thanks
-- PMM
On 20 August 2012 19:45, Bruce Rogers brog...@suse.com wrote:
When building qemu-kvm for openSUSE:Factory, I am getting
Am 24.10.2012 18:48, schrieb Peter Maydell:
Ping! Just ran into this bug today and noticed this
patch never got applied.
Patch still applies OK, patchwork url is:
http://patchwork.ozlabs.org/patch/178920/
...and since it was noticed while packaging v1.2, it should go into
stable as well
On Sun, Oct 21, 2012 at 10:58:37PM +0400, Michael Tokarev wrote:
On 19.10.2012 23:33, Aurelien Jarno wrote:
On Wed, Oct 17, 2012 at 07:09:25PM +0200, Jan Kiszka wrote:
We need to evaluate $libexecdir in configure, otherwise we literally end
up with ${prefix}/libexec instead of the absolute
On 19.10.2012 23:33, Aurelien Jarno wrote:
On Wed, Oct 17, 2012 at 07:09:25PM +0200, Jan Kiszka wrote:
We need to evaluate $libexecdir in configure, otherwise we literally end
up with ${prefix}/libexec instead of the absolute path as
CONFIG_QEMU_HELPERDIR.
Signed-off-by: Jan Kiszka
Rather than printing a message saying we're silently falling
back to gthread coroutines when running on MacOS, actually
do it silently.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
I guess this is a self-falsifying echo :-)
configure | 2 --
1 file changed, 2 deletions(-)
diff
On Wed, Oct 17, 2012 at 07:09:25PM +0200, Jan Kiszka wrote:
We need to evaluate $libexecdir in configure, otherwise we literally end
up with ${prefix}/libexec instead of the absolute path as
CONFIG_QEMU_HELPERDIR.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
configure |2 +-
We need to evaluate $libexecdir in configure, otherwise we literally end
up with ${prefix}/libexec instead of the absolute path as
CONFIG_QEMU_HELPERDIR.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
configure |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Am 14.10.2012 22:24, schrieb Peter Maydell:
On 14 October 2012 21:15, Blue Swirlblauwir...@gmail.com wrote:
On Sun, Oct 14, 2012 at 8:00 PM, Peter Maydellpeter.mayd...@linaro.org wrote:
Blue Swirl previously submitted a patch which enabled this flag
(among others):
On 16 October 2012 21:20, Stefan Weil s...@weilnetz.de wrote:
Hi Peter, hi Blue,
gcc uses a different flag -Wno-override-init to disable initializer override
warnings.
I tested the following patch which uses -Wextra with gcc-4.4 and gcc-4.7.
It allows compilation of QEMU without warnings.
On Sun, Oct 14, 2012 at 8:00 PM, Peter Maydell peter.mayd...@linaro.org wrote:
Disable clang's initializer-overrides warnings, as QEMU makes significant
use of the pattern of initializing an array with a range-based default
entry like
[0 ... 0x1ff] = { GPIO_NONE, 0 }
followed by specific
Disable clang's initializer-overrides warnings, as QEMU makes significant
use of the pattern of initializing an array with a range-based default
entry like
[0 ... 0x1ff] = { GPIO_NONE, 0 }
followed by specific entries which override that default, and clang
would otherwise warn initializer
On 14 October 2012 21:15, Blue Swirl blauwir...@gmail.com wrote:
On Sun, Oct 14, 2012 at 8:00 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
Blue Swirl previously submitted a patch which enabled this flag
(among others):
http://lists.gnu.org/archive/html/qemu-devel/2012-07/msg04203.html
This modification is required if compiler option -Wunused-parameter is
activated.
Signed-off-by: Stefan Weil s...@weilnetz.de
---
configure |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 353d788..499ad81 100755
--- a/configure
+++
On Wed, Sep 26, 2012 at 10:04:38PM +0200, Stefan Weil wrote:
Specifying an empty target list with --target-list= is shorter
than specifying --disable-user --disable-system.
Both variants should give the same result: no targets at all.
This modification implements that feature.
It uses a
Tidy up some remnants of code to support non-64-bit physaddrs
which were accidentally omitted from commit 4be403c8.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
configure |2 --
1 file changed, 2 deletions(-)
diff --git a/configure b/configure
index e58846d..11b0e21 100755
---
Stefan Weil s...@weilnetz.de writes:
The old code aborted configure when no emulation target was selected.
Even after removing the 'exit 1', it tried to read from STDIN
when QEMU was configured with
configure' '--disable-user' '--disable-system'
This is fixed here.
Signed-off-by:
Specifying an empty target list with --target-list= is shorter
than specifying --disable-user --disable-system.
Both variants should give the same result: no targets at all.
This modification implements that feature.
It uses a trick which works with POSIX compliant shells to test whether
On Sat, Sep 22, 2012 at 11:37 PM, Stefan Weil s...@weilnetz.de wrote:
Am 14.09.2012 19:02, schrieb Stefan Weil:
The old code aborted configure when no emulation target was selected.
Even after removing the 'exit 1', it tried to read from STDIN
when QEMU was configured with
configure'
Am 24.09.2012 12:57, schrieb Laurent Desnogues:
On Sat, Sep 22, 2012 at 11:37 PM, Stefan Weils...@weilnetz.de wrote:
Am 14.09.2012 19:02, schrieb Stefan Weil:
The old code aborted configure when no emulation target was selected.
Even after removing the 'exit 1', it tried to read from STDIN
Am 14.09.2012 19:02, schrieb Stefan Weil:
The old code aborted configure when no emulation target was selected.
Even after removing the 'exit 1', it tried to read from STDIN
when QEMU was configured with
configure' '--disable-user' '--disable-system'
This is fixed here.
Signed-off-by:
On Sun, 16 Sep 2012 22:21:31 +0200
Stefan Weil s...@weilnetz.de wrote:
Am 16.09.2012 21:52, schrieb Mike Frysinger:
On Sunday 15 July 2012 15:54:51 Stefan Weil wrote:
Am 15.07.2012 22:26, schrieb Mike Frysinger:
We should not quote the PKG_CONFIG setting as this deviates from the
Mike Frysinger vap...@gentoo.org writes:
We should not quote the PKG_CONFIG setting as this deviates from the
canonical upstream behavior that gets integrated with all other build
systems, and deviates from how we treat all other toolchain variables
that we get from the environment.
On 09/17/2012 01:38 PM, Anthony Liguori wrote:
Mike Frysinger vap...@gentoo.org writes:
We should not quote the PKG_CONFIG setting as this deviates from the
canonical upstream behavior that gets integrated with all other build
systems, and deviates from how we treat all other toolchain
Am 16.09.2012 21:52, schrieb Mike Frysinger:
On Sunday 15 July 2012 15:54:51 Stefan Weil wrote:
Am 15.07.2012 22:26, schrieb Mike Frysinger:
We should not quote the PKG_CONFIG setting as this deviates from the
canonical upstream behavior that gets integrated with all other build
systems, and
On 12 September 2012 14:20, Laurent Desnogues
laurent.desnog...@gmail.com wrote:
Sorry, I had missed this patch...
On Tue, Sep 11, 2012 at 9:02 PM, Eduardo Habkost ehabk...@redhat.com wrote:
commit 66d5499b3754b83c09487259c08fe2ce73188a59 broke the support for
comma-separated target lists on
Peter Maydell peter.mayd...@linaro.org writes:
On 12 September 2012 14:20, Laurent Desnogues
laurent.desnog...@gmail.com wrote:
Sorry, I had missed this patch...
On Tue, Sep 11, 2012 at 9:02 PM, Eduardo Habkost ehabk...@redhat.com wrote:
commit 66d5499b3754b83c09487259c08fe2ce73188a59 broke
On Fri, Sep 14, 2012 at 01:53:11PM +0100, Peter Maydell wrote:
On 12 September 2012 14:20, Laurent Desnogues
laurent.desnog...@gmail.com wrote:
Sorry, I had missed this patch...
On Tue, Sep 11, 2012 at 9:02 PM, Eduardo Habkost ehabk...@redhat.com
wrote:
commit
The old code aborted configure when no emulation target was selected.
Even after removing the 'exit 1', it tried to read from STDIN
when QEMU was configured with
configure' '--disable-user' '--disable-system'
This is fixed here.
Signed-off-by: Stefan Weil s...@weilnetz.de
---
This patch
Am 14.09.2012 14:53, schrieb Peter Maydell:
On 12 September 2012 14:20, Laurent Desnogues
laurent.desnog...@gmail.com wrote:
Sorry, I had missed this patch...
On Tue, Sep 11, 2012 at 9:02 PM, Eduardo Habkostehabk...@redhat.com wrote:
commit 66d5499b3754b83c09487259c08fe2ce73188a59 broke the
Feel free to merge this into the original commit at that is not upstream
yet.
Signed-off-by: Hans de Goede hdego...@redhat.com
CC: Aurelien Jarno aurel...@aurel32.net
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 1854b0b..d63530a
On 09/13/12 09:31, Hans de Goede wrote:
-libs_softmmu=$LIBS $usb_redir_libs
+libs_softmmu=$libs_softmmu $usb_redir_libs
Good point ;)
Fix squashed in.
thanks,
Gerd
On 09/11/12 20:57, Aurelien Jarno wrote:
usbredir is only used by system emulation, so add the libraries to
libs_softmmu instead of LIBS.
Patch added to usb patch queue.
thanks,
Gerd
Sorry, I had missed this patch...
On Tue, Sep 11, 2012 at 9:02 PM, Eduardo Habkost ehabk...@redhat.com wrote:
commit 66d5499b3754b83c09487259c08fe2ce73188a59 broke the support for
comma-separated target lists on the --target-list option. e.g.:
$ ./configure
commit 66d5499b3754b83c09487259c08fe2ce73188a59 broke the support for
comma-separated target lists on the --target-list option. e.g.:
$ ./configure --target-list=x86_64-linux-user,x86_64-softmmu
[...]
ERROR: Target 'x86_64-linux-user,x86_64-softmmu' not recognised
$
This patch restores
usbredir is only used by system emulation, so add the libraries to
libs_softmmu instead of LIBS.
Cc: Michael Tokarev m...@tls.msk.ru
Cc: Gerd Hoffmann kra...@redhat.com
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
---
configure |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Wed, Sep 12, 2012 at 5:02 AM, Eduardo Habkost ehabk...@redhat.com wrote:
commit 66d5499b3754b83c09487259c08fe2ce73188a59 broke the support for
comma-separated target lists on the --target-list option. e.g.:
$ ./configure --target-list=x86_64-linux-user,x86_64-softmmu
[...]
ERROR:
On 11.09.2012 22:57, Aurelien Jarno wrote:
usbredir is only used by system emulation, so add the libraries to
libs_softmmu instead of LIBS.
Fwiw, original code breaks user-static build - not it only
tries to link with unused library but also some distros
does not package/provide static (.a)
Am 06.09.2012 22:40, schrieb Yann E. MORIN:
Currently, if libseccomp is missing but the user explicitly requested
seccomp support using --enable-seccomp, configure silently ignores the
situation and disables seccomp support.
This is unlike all other tests that explicitly fail in such
Currently, if libseccomp is missing but the user explicitly requested
seccomp support using --enable-seccomp, configure silently ignores the
situation and disables seccomp support.
This is unlike all other tests that explicitly fail in such situation.
Fix that.
Signed-off-by: Yann E. MORIN
OpenBSD's uname works as expected with the -s flag so remove the special
handling when determining the target OS. Use arch -s to retrieve the
hardware architecture as uname -m will return the meta architecture
instead of the hardware architecture (.e.g. macppc vs powerpc).
Signed-off-by: Brad
On 24 August 2012 10:47, Brad Smith b...@comstyle.com wrote:
OpenBSD's uname works as expected with the -s flag so remove the special
handling when determining the target OS. Use arch -s to retrieve the
hardware architecture as uname -m will return the meta architecture
instead of the hardware
On Fri, Aug 24, 2012 at 10:55:10AM +0100, Peter Maydell wrote:
On 24 August 2012 10:47, Brad Smith b...@comstyle.com wrote:
OpenBSD's uname works as expected with the -s flag so remove the special
handling when determining the target OS. Use arch -s to retrieve the
hardware architecture as
Il 24/08/2012 11:55, Peter Maydell ha scritto:
OpenBSD's uname works as expected with the -s flag so remove the special
handling when determining the target OS. Use arch -s to retrieve the
hardware architecture as uname -m will return the meta architecture
instead of the hardware
On Fri, Aug 24, 2012 at 01:56:31PM +0200, Paolo Bonzini wrote:
Il 24/08/2012 11:55, Peter Maydell ha scritto:
OpenBSD's uname works as expected with the -s flag so remove the special
handling when determining the target OS. Use arch -s to retrieve the
hardware architecture as uname -m
Il 24/08/2012 14:00, Brad Smith ha scritto:
OpenBSD's uname works as expected with the -s flag so remove the
special
handling when determining the target OS. Use arch -s to retrieve
the
hardware architecture as uname -m will return the meta architecture
instead of the
On Fri, Aug 24, 2012 at 02:02:57PM +0200, Paolo Bonzini wrote:
Il 24/08/2012 14:00, Brad Smith ha scritto:
OpenBSD's uname works as expected with the -s flag so remove the
special
handling when determining the target OS. Use arch -s to retrieve
the
hardware architecture
When building qemu-kvm for openSUSE:Factory, I am getting a
warning in the pipe2 detection performed by configure, which
prevents using --enable-werror.
Change detection code to use return value of pipe2.
Signed-off-by: Bruce Rogers brog...@suse.com
---
configure |3 +--
1 files changed, 1
On 20 August 2012 19:45, Bruce Rogers brog...@suse.com wrote:
When building qemu-kvm for openSUSE:Factory, I am getting a
warning in the pipe2 detection performed by configure, which
prevents using --enable-werror.
Change detection code to use return value of pipe2.
Signed-off-by: Bruce
Both MacOS and Solaris have special case handling for the CPU
type, because the check_define probes will return i386 even if
the hardware is 64 bit and x86_64 would be preferable. Move
these checks earlier in the configure probing so that we can
do them only if the user didn't specify a CPU with
Am 14.08.2012 16:35, schrieb Peter Maydell:
Both MacOS and Solaris have special case handling for the CPU
type, because the check_define probes will return i386 even if
the hardware is 64 bit and x86_64 would be preferable. Move
these checks earlier in the configure probing so that we can
do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pathetic case (32bit qemu on 64bit hw under Mac OS X 10.6) tested succesfully.
Thanks for your patience and help.
Michael
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Configuring with Clang compiler with -Werror would not work after
improved checks:
/tmp/qemu-conf--25992-.c:4:32: error: self-comparison always evaluates
to true [-Werror,-Wtautological-compare]
int main(void) { return preadv == preadv; }
/tmp/qemu-conf--25992-.c:13:26: error: self-comparison
On 9 August 2012 21:31, Blue Swirl blauwir...@gmail.com wrote:
Configuring with Clang compiler with -Werror would not work after
improved checks:
/tmp/qemu-conf--25992-.c:4:32: error: self-comparison always evaluates
to true [-Werror,-Wtautological-compare]
int main(void) { return preadv ==
Ping?
-- PMM
On 18 July 2012 12:10, Peter Maydell peter.mayd...@linaro.org wrote:
The code creating the symlink from linux-headers/asm to the
architecture specific linux-headers/asm-$arch directory was
implicitly hardcoding a list of KVM supporting architectures.
Add a default case for the
Am 02.08.2012 17:41, schrieb Peter Maydell:
Ping?
Alex? Christian?
-- PMM
On 18 July 2012 12:10, Peter Maydell peter.mayd...@linaro.org wrote:
The code creating the symlink from linux-headers/asm to the
architecture specific linux-headers/asm-$arch directory was
implicitly hardcoding a
On 02.08.2012, at 17:46, Andreas Färber wrote:
Am 02.08.2012 17:41, schrieb Peter Maydell:
Ping?
Alex? Christian?
Looks good to me, and should probably go in through the kvm queue. Avi, Marcelo?
-- PMM
On 18 July 2012 12:10, Peter Maydell peter.mayd...@linaro.org wrote:
The code
Am 18.07.2012 13:10, schrieb Peter Maydell:
The code creating the symlink from linux-headers/asm to the
architecture specific linux-headers/asm-$arch directory was
implicitly hardcoding a list of KVM supporting architectures.
Add a default case for the common Linux architecture name and
QEMU
On 2 August 2012 17:01, Andreas Färber afaer...@suse.de wrote:
One minor nit: The indentation seems off here - esac 2 spaces, if 4.
configure's indentation is pretty inconsistent generally between
2 or 4 spaces. I usually go for 4 for new code but don't reindent
old code. (There's a lot more
Am 02.08.2012 18:22, schrieb Peter Maydell:
On 2 August 2012 17:01, Andreas Färber afaer...@suse.de wrote:
One minor nit: The indentation seems off here - esac 2 spaces, if 4.
configure's indentation is pretty inconsistent generally between
2 or 4 spaces. I usually go for 4 for new code but
On Thu, Aug 02, 2012 at 05:53:37PM +0200, Alexander Graf wrote:
On 02.08.2012, at 17:46, Andreas Färber wrote:
Am 02.08.2012 17:41, schrieb Peter Maydell:
Ping?
Alex? Christian?
Looks good to me, and should probably go in through the kvm queue. Avi,
Marcelo?
Sure, please send
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
This fix the below error on ubuntu 12.04
a.c: In function ‘main’:
a.c:3:24: error: variable ‘caps’ set but not used
[-Werror=unused-but-set-variable]
a.c:3:1: error: control reaches end of non-void function [-Werror=return-type]
Avi Kivity a...@redhat.com writes:
- avoid assigned-but-not-used error
- avoid missing return error
Signed-off-by: Avi Kivity a...@redhat.com
Acked-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Am 31.07.2012 08:52, schrieb Aneesh Kumar K.V:
Avi Kivity a...@redhat.com writes:
- avoid assigned-but-not-used error
- avoid missing return error
Signed-off-by: Avi Kivity a...@redhat.com
Acked-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
---
configure | 2 +-
1
On 31 July 2012 17:33, Stefan Weil s...@weilnetz.de wrote:
please apply http://patchwork.ozlabs.org/patch/171067/,
or we'll get a 4th bug fix for this.
Peter sent a series with this one and more patches on
2012-07-18 (1st: http://patchwork.ozlabs.org/patch/171686/).
At least the first 10 of
On Tue, Jul 31, 2012 at 4:40 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 31 July 2012 17:33, Stefan Weil s...@weilnetz.de wrote:
please apply http://patchwork.ozlabs.org/patch/171067/,
or we'll get a 4th bug fix for this.
Peter sent a series with this one and more patches on
Stefan Weil s...@weilnetz.de writes:
Am 31.07.2012 08:52, schrieb Aneesh Kumar K.V:
Avi Kivity a...@redhat.com writes:
- avoid assigned-but-not-used error
- avoid missing return error
Signed-off-by: Avi Kivity a...@redhat.com
Acked-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
On Tue, Jul 31, 2012 at 4:40 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 31 July 2012 17:33, Stefan Weil s...@weilnetz.de wrote:
please apply http://patchwork.ozlabs.org/patch/171067/,
or we'll get a 4th bug fix for this.
Peter sent a series with this one and more patches on
On 31 July 2012 18:56, Blue Swirl blauwir...@gmail.com wrote:
On Tue, Jul 31, 2012 at 4:40 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
I believe the valgrind test patch should fix the issues Blue Swirl
was seeing with the 11-patch series (and I tested it on debian
squeeze which I think
Thanks, applied.
On Mon, Jul 30, 2012 at 3:13 PM, Peter Maydell peter.mayd...@linaro.org wrote:
Split the configure test that checks for valgrind into two, one
part checking whether we have the gcc pragma to disable unused-but-set
variables, and the other part checking for the existence of
- avoid assigned-but-not-used error
- avoid missing return error
Signed-off-by: Avi Kivity a...@redhat.com
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 7767aca..5fb449d 100755
--- a/configure
+++ b/configure
@@ -2099,7 +2099,7 @@
On 30 July 2012 12:41, Avi Kivity a...@redhat.com wrote:
- avoid assigned-but-not-used error
- avoid missing return error
Signed-off-by: Avi Kivity a...@redhat.com
There's already a patch on the list for this:
http://patchwork.ozlabs.org/patch/171704/
-- PMM
Split the configure test that checks for valgrind into two, one
part checking whether we have the gcc pragma to disable unused-but-set
variables, and the other part checking for the existence of valgrind.h.
The first of these has to be compiled with -Werror and the second
does not and shouldn't
On Mon, Jul 30, 2012 at 02:41:33PM +0300, Avi Kivity wrote:
- avoid assigned-but-not-used error
- avoid missing return error
Signed-off-by: Avi Kivity a...@redhat.com
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index
The xs.h header is now deprecated and produce a warning. This prevent the
configure script from enabling xen with Xen unstable whom will become 4.2. As
this header is not anymore common to every version of Xen, we just remove it
from the early probe for Xen.
Signed-off-by: Anthony PERARD
On Thu, 26 Jul 2012, Anthony PERARD wrote:
The xs.h header is now deprecated and produce a warning. This prevent the
configure script from enabling xen with Xen unstable whom will become 4.2. As
this header is not anymore common to every version of Xen, we just remove it
from the early probe
Am 26.07.2012 12:09, schrieb Anthony PERARD:
The xs.h header is now deprecated and produce a warning. This prevent the
produces, prevents
Stefano, can you fix in your queue?
Regards,
/-F
configure script from enabling xen with Xen unstable whom will become 4.2. As
this header is not anymore
On Thu, 26 Jul 2012, Andreas Färber wrote:
Am 26.07.2012 12:09, schrieb Anthony PERARD:
The xs.h header is now deprecated and produce a warning. This prevent the
produces, prevents
Stefano, can you fix in your queue?
Yep, I'll submit a pull request with the fixup.
On Tue, Jul 17, 2012 at 7:28 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 17 July 2012 20:24, Stefan Weil s...@weilnetz.de wrote:
The arguments why -Werror is a bad idea for some configure tests
are reasonable.
Nevertheless the QEMU community was able to produce thousands of
lines of
On 23 July 2012 18:40, Blue Swirl blauwir...@gmail.com wrote:
On Tue, Jul 17, 2012 at 7:28 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
The trouble is that the warnings and errors here don't cause the
build to fail noisily; that's a big distinction IMHO.
I suppose we could make
On Fri, Jul 20, 2012 at 5:19 PM, Stefan Weil s...@weilnetz.de wrote:
Am 20.07.2012 08:38, schrieb Alexey Kardashevskiy:
On 20/07/12 16:05, Alexey Kardashevskiy wrote:
On 20/07/12 15:37, Alexey Kardashevskiy wrote:
On 20/07/12 15:23, Stefan Weil wrote:
Am 20.07.2012 05:53, schrieb Alexey
On 23 July 2012 18:45, Peter Maydell peter.mayd...@linaro.org wrote:
On 23 July 2012 18:40, Blue Swirl blauwir...@gmail.com wrote:
On Tue, Jul 17, 2012 at 7:28 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
The trouble is that the warnings and errors here don't cause the
build to fail
SRC_PATH is undefined during configure run time, it is only defined in
makefiles generated by it. Replace with source_path which is defined.
Signed-off-by: Alon Levy al...@redhat.com
---
configure |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index
On 22 July 2012 12:00, Alon Levy al...@redhat.com wrote:
SRC_PATH is undefined during configure run time, it is only defined in
makefiles generated by it. Replace with source_path which is defined.
There's a (slightly different) patch to address this issue in my
configure series I posted
On Sun, Jul 22, 2012 at 12:30:27PM +0100, Peter Maydell wrote:
On 22 July 2012 12:00, Alon Levy al...@redhat.com wrote:
SRC_PATH is undefined during configure run time, it is only defined in
makefiles generated by it. Replace with source_path which is defined.
There's a (slightly
On Mon, Jul 16, 2012 at 12:10 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Sun, Jul 15, 2012 at 09:38:25PM +0200, Laszlo Ersek wrote:
... after commit 417c9d72 (configure: add -Werror to QEMU_CFLAGS early)
Signed-off-by: Laszlo Ersek ler...@redhat.com
---
configure |2 +-
1 files
On 20/07/12 15:37, Alexey Kardashevskiy wrote:
On 20/07/12 15:23, Stefan Weil wrote:
Am 20.07.2012 05:53, schrieb Alexey Kardashevskiy:
On 19/07/12 02:37, Stefan Weil wrote:
32-bit applications on Windows normally only get virtual memory in
the lower 2 GiB address space.
Because of memory
On 20/07/12 16:05, Alexey Kardashevskiy wrote:
On 20/07/12 15:37, Alexey Kardashevskiy wrote:
On 20/07/12 15:23, Stefan Weil wrote:
Am 20.07.2012 05:53, schrieb Alexey Kardashevskiy:
On 19/07/12 02:37, Stefan Weil wrote:
32-bit applications on Windows normally only get virtual memory in
the
Am 20.07.2012 08:38, schrieb Alexey Kardashevskiy:
On 20/07/12 16:05, Alexey Kardashevskiy wrote:
On 20/07/12 15:37, Alexey Kardashevskiy wrote:
On 20/07/12 15:23, Stefan Weil wrote:
Am 20.07.2012 05:53, schrieb Alexey Kardashevskiy:
On 19/07/12 02:37, Stefan Weil wrote:
32-bit applications
On 19/07/12 02:37, Stefan Weil wrote:
32-bit applications on Windows normally only get virtual memory in
the lower 2 GiB address space.
Because of memory fragmentation, VirtualAlloc() usually won't get 1 GiB
of contiguous virtual memory in that address space. Therefore running
system
Am 20.07.2012 05:53, schrieb Alexey Kardashevskiy:
On 19/07/12 02:37, Stefan Weil wrote:
32-bit applications on Windows normally only get virtual memory in
the lower 2 GiB address space.
Because of memory fragmentation, VirtualAlloc() usually won't get 1 GiB
of contiguous virtual memory in
On 20/07/12 15:23, Stefan Weil wrote:
Am 20.07.2012 05:53, schrieb Alexey Kardashevskiy:
On 19/07/12 02:37, Stefan Weil wrote:
32-bit applications on Windows normally only get virtual memory in
the lower 2 GiB address space.
Because of memory fragmentation, VirtualAlloc() usually won't get 1
The code creating the symlink from linux-headers/asm to the
architecture specific linux-headers/asm-$arch directory was
implicitly hardcoding a list of KVM supporting architectures.
Add a default case for the common Linux architecture name and
QEMU CPU name match case, so future architectures will
On Monday 16 July 2012 11:58:55 Stefan Weil wrote:
Am 16.07.2012 17:39, schrieb Eric Blake:
On 07/15/2012 01:54 PM, Stefan Weil wrote:
Am 15.07.2012 22:26, schrieb Mike Frysinger:
We should not quote the PKG_CONFIG setting as this deviates from the
canonical upstream behavior that gets
32-bit applications on Windows normally only get virtual memory in
the lower 2 GiB address space.
Because of memory fragmentation, VirtualAlloc() usually won't get 1 GiB
of contiguous virtual memory in that address space. Therefore running
system emulations with 1 GiB or more RAM will abort with
After commit 417c9d72d48275d19c60861896efd4962d21aca2 all configure tests are
executed with -Werror flag. Current ALSA configure test program invokes a
warning:
warning: ‘handle’ is used uninitialized in this function [-Wuninitialized]
which results in error with -Werror flag and, consequently,
I see now that this bug was already noticed, please ignore this mail
On 07/17/2012 09:34 PM, Igor Mitsyanko wrote:
After commit 417c9d72d48275d19c60861896efd4962d21aca2 all configure tests are
executed with -Werror flag. Current ALSA configure test program invokes a
warning:
warning: ‘handle’
Am 17.07.2012 20:03, schrieb Igor Mitsyanko:
I see now that this bug was already noticed, please ignore this mail
On 07/17/2012 09:34 PM, Igor Mitsyanko wrote:
After commit 417c9d72d48275d19c60861896efd4962d21aca2 all configure
tests are
executed with -Werror flag. Current ALSA configure test
On 17 July 2012 19:32, Stefan Weil s...@weilnetz.de wrote:
Hello Anthony, hello Blue,
these patches fix broken builds, therefore I expected that they
would be applied fast:
http://patchwork.ozlabs.org/patch/171066/
http://patchwork.ozlabs.org/patch/171067/
Am 17.07.2012 20:46, schrieb Peter Maydell:
On 17 July 2012 19:32, Stefan Weil s...@weilnetz.de wrote:
Hello Anthony, hello Blue,
these patches fix broken builds, therefore I expected that they
would be applied fast:
http://patchwork.ozlabs.org/patch/171066/
Don't run configure tests with -Werror in the compiler flags. The idea
of -Werror is that it makes problems very obvious to developers, so
they get fixed quickly. However, when running configure tests, failures
due to -Werror are far from obvious -- they simply result in the test
quietly failing
801 - 900 of 1161 matches
Mail list logo
