On 26 September 2013 21:54, Paolo Bonzini pbonz...@redhat.com wrote:
Il 26/09/2013 05:22, Doug Goldstein ha scritto:
On Mon, Sep 9, 2013 at 2:30 PM, Stefan Weil stefan.w...@weilnetz.de wrote:
Am 28.08.2013 10:21, schrieb James Hogan:
On 1 July 2013 04:30, Mike Frysinger vap...@gentoo.org
Am 04.11.2013 13:19, schrieb Dinar Valeev:
From: Dinar Valeev dval...@suse.de
This patch enables pie for PowerPC and ARM architectures
Signed-off-by: Dinar Valeev dval...@suse.com
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
Am 04.11.2013 22:16, schrieb Paolo Bonzini:
Il 04/11/2013 21:51, Richard Henderson ha scritto:
if test $pie = ; then
case $cpu-$targetos in
-i386-Linux|x86_64-Linux|x32-Linux|i386-OpenBSD|x86_64-OpenBSD)
+
From: Dinar Valeev dval...@suse.de
This patch enables pie for PowerPC and ARM architectures
Signed-off-by: Dinar Valeev dval...@suse.com
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 91372f9..0130e7e 100755
--- a/configure
+++
On 11/04/2013 10:19 PM, Dinar Valeev wrote:
From: Dinar Valeev dval...@suse.de
This patch enables pie for PowerPC and ARM architectures
Signed-off-by: Dinar Valeev dval...@suse.com
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
Il 04/11/2013 21:51, Richard Henderson ha scritto:
if test $pie = ; then
case $cpu-$targetos in
-i386-Linux|x86_64-Linux|x32-Linux|i386-OpenBSD|x86_64-OpenBSD)
+
i386-Linux|x86_64-Linux|x32-Linux|ppc*-Linux|arm*-Linux|aarch64*-Linux|i386-OpenBSD|x86_64-OpenBSD)
I'd much
Am 20.10.2013 18:39, schrieb Stefan Weil:
The latest configure invocation was saved in config-host.mak and could
be extracted from that file to recreate the configuration.
Now it is saved in a new file config.status which can be directly executed
to recreate the configuration. The file name
On Sun, 10/20 18:39, Stefan Weil wrote:
The latest configure invocation was saved in config-host.mak and could
be extracted from that file to recreate the configuration.
Now it is saved in a new file config.status which can be directly executed
to recreate the configuration. The file name
The latest configure invocation was saved in config-host.mak and could
be extracted from that file to recreate the configuration.
Now it is saved in a new file config.status which can be directly executed
to recreate the configuration. The file name and the comments were copied
from GNU autoconf.
Il 12/10/2013 21:05, Michael Tokarev ha scritto:
I considered doing it there initially, but decided to add it
to the other place, because that's where virtfs variable
is set. The place you're referring to will need to have a
condition `if' based on $virtfs value.
It's harmless to create a
m...@tls.msk.ru writes:
In some cases when building with parallelism (make -jN),
build fails because the directory where output files are
supposed to be does not exist. In particular, when make
decides to build virtfs-proxy-helper.1 before other files
in fsdev/, build will fail with the
Il 11/10/2013 11:05, Michael Tokarev ha scritto:
In some cases when building with parallelism (make -jN),
build fails because the directory where output files are
supposed to be does not exist. In particular, when make
decides to build virtfs-proxy-helper.1 before other files
in fsdev/,
12.10.2013 20:28, Paolo Bonzini wrote:
Il 11/10/2013 11:05, Michael Tokarev ha scritto:
[]
--- a/configure
+++ b/configure
@@ -3576,6 +3576,7 @@ if test $softmmu = yes ; then
if test $cap = yes test $linux = yes test $attr = yes ; then
virtfs=yes
tools=$tools
In some cases when building with parallelism (make -jN),
build fails because the directory where output files are
supposed to be does not exist. In particular, when make
decides to build virtfs-proxy-helper.1 before other files
in fsdev/, build will fail with the following error:
perl -Ww --
Il 26/09/2013 05:22, Doug Goldstein ha scritto:
On Mon, Sep 9, 2013 at 2:30 PM, Stefan Weil stefan.w...@weilnetz.de wrote:
Am 28.08.2013 10:21, schrieb James Hogan:
On 1 July 2013 04:30, Mike Frysinger vap...@gentoo.org wrote:
This avoids needing to execute a program and keeping an
On Mon, Sep 9, 2013 at 2:30 PM, Stefan Weil stefan.w...@weilnetz.de wrote:
Am 28.08.2013 10:21, schrieb James Hogan:
On 1 July 2013 04:30, Mike Frysinger vap...@gentoo.org wrote:
This avoids needing to execute a program and keeping an (incomplete)
list when cross-compiling. Signed-off-by: Mike
Am 28.08.2013 10:21, schrieb James Hogan:
On 1 July 2013 04:30, Mike Frysinger vap...@gentoo.org wrote:
This avoids needing to execute a program and keeping an (incomplete)
list when cross-compiling. Signed-off-by: Mike Frysinger
vap...@gentoo.org
This fixes mipsel cross compiling. I also
Am 21.08.2013 07:44, schrieb Stefan Weil:
Compiler option -Wextra enables an additional set of compiler warnings.
Some of these warnings were already enabled explicitly in QEMU:
-Wold-style-declaration, -Wtype-limits, -Wignored-qualifiers and
-Wempty-body are now redundant and can be removed.
On 1 July 2013 04:30, Mike Frysinger vap...@gentoo.org wrote:
This avoids needing to execute a program and keeping an (incomplete)
list when cross-compiling.
Signed-off-by: Mike Frysinger vap...@gentoo.org
This fixes mipsel cross compiling. I also checked it detected a mips
(be) compiler as
When a Python script is run, Python normally writes bytecode into a .pyc file.
QEMU's build process uses several Python scripts which are called from
configure or make.
The generated .pyc files take disk space without being of much use, because
those scripts are short, not time critical and only
Ping for qemu-trivial now 1.7 is open.
thanks
-- PMM
On 5 August 2013 20:16, Peter Maydell peter.mayd...@linaro.org wrote:
Some versions of clang will warn about adding integers to strings:
disas/i386.c:4753:23: error: adding 'char' to a string does not append
to the string
Compiler option -Wextra enables an additional set of compiler warnings.
Some of these warnings were already enabled explicitly in QEMU:
-Wold-style-declaration, -Wtype-limits, -Wignored-qualifiers and
-Wempty-body are now redundant and can be removed.
Others don't work with the current code and
Peter Maydell peter.mayd...@linaro.org writes:
Some versions of clang will warn about adding integers to strings:
disas/i386.c:4753:23: error: adding 'char' to a string does not append
to the string [-Werror,-Wstring-plus-int]
oappend (%es: + intel_syntax);
Some versions of clang will warn about adding integers to strings:
disas/i386.c:4753:23: error: adding 'char' to a string does not append
to the string [-Werror,-Wstring-plus-int]
oappend (%es: + intel_syntax);
~~~^~
disas/i386.c:4753:23: note: use array
Applied. Thanks.
Regards,
Anthony Liguori
If the system has GTK but not libvte, it's more helpful to
tell the user that libvte is missing than to simply say that
GTK is not present.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
Since this confused me today and also iggy on IRC, it seems worth
making the message a little more
Applied. Thanks.
Regards,
Anthony Liguori
On 06/30/2013 08:30 PM, Mike Frysinger wrote:
This avoids needing to execute a program and keeping an (incomplete)
list when cross-compiling.
Signed-off-by: Mike Frysinger vap...@gentoo.org
For the benefit of the list, this is a porting of the autoconf test.
Reviewed-by: Richard Henderson
This avoids needing to execute a program and keeping an (incomplete)
list when cross-compiling.
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
configure | 40 ++--
1 file changed, 14 insertions(+), 26 deletions(-)
diff --git a/configure b/configure
index
clang 3.8 with -fsanitize=undefined will fail to link code containing an
int128_t * int128_t multiply (http://llvm.org/bugs/show_bug.cgi?id=16404)
so add this to our configure test for whether [u]int128_t are usable.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
configure |1 +
1
On 06/21/2013 06:01 AM, Peter Maydell wrote:
clang 3.8 with -fsanitize=undefined will fail to link code containing an
int128_t * int128_t multiply (http://llvm.org/bugs/show_bug.cgi?id=16404)
so add this to our configure test for whether [u]int128_t are usable.
Signed-off-by: Peter Maydell
On 21 June 2013 14:01, Peter Maydell peter.mayd...@linaro.org wrote:
clang 3.8 with -fsanitize=undefined will fail to link code containing an
int128_t * int128_t multiply (http://llvm.org/bugs/show_bug.cgi?id=16404)
so add this to our configure test for whether [u]int128_t are usable.
I meant
error_exit already prepends ERROR: , so no need to print it manually.
Signed-off-by: Andreas Färber afaer...@suse.de
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index ad32f87..bb126e8 100755
--- a/configure
+++ b/configure
@@ -2529,7
On 18 June 2013 00:09, Andreas Färber afaer...@suse.de wrote:
error_exit already prepends ERROR: , so no need to print it manually.
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
-- PMM
It was only used in one place (and already expanded in one other).
Signed-off-by: Ed Maste ema...@freebsd.org
---
configure | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/configure b/configure
index 1654413..e197b91 100755
--- a/configure
+++ b/configure
@@ -3556,7 +3556,6
It hasn't built since FreeBSD 8.x, and is disabled by a patch in the
FreeBSD ports tree. FreeBSD is migrating to QEMU's libusb support.
Signed-off-by: Ed Maste ema...@freebsd.org
---
configure | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index
Signed-off-by: Ed Maste ema...@freebsd.org
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 1654413..ec833df 100755
--- a/configure
+++ b/configure
@@ -4445,7 +4445,7 @@ fi
if test $ARCH = tci; then
linker_script=
else
-
When probing for ncurses, try pkg-config first rather than after
explicit -lncurses and -lcurses. This fixes static linking in the case
that ncurses has additional dependencies, such as -ltinfo (as on FreeBSD).
Signed-off-by: Ed Maste ema...@freebsd.org
---
configure | 2 +-
1 file changed, 1
The configure script had some code to manipulate config-host.ld~ (i.e.,
a common backup filename), comparing it with the newly-generated file.
I believe the sense of the comparison was backwards.
Since it seemed to serve little purpose anyway, remove it to avoid any
confusion.
Signed-off-by: Ed
We already had a test to add -march=i486 when needed. Make the
existing test independent of vhost-net, so that it is also used
under Win32.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
configure | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/configure
There is no reason why vhost-net should not work with TCG.
Hence, put the limitation in hw/vhost-net.c, not straight in
the config-*.mak files.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
configure | 6 +++---
hw/net/vhost_net.c | 2 +-
2 files changed, 4 insertions(+), 4
On 9 April 2013 11:25, Paolo Bonzini pbonz...@redhat.com wrote:
We already had a test to add -march=i486 when needed. Make the
existing test independent of vhost-net, so that it is also used
under Win32.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
configure | 7 +--
1 file
On Tue, Apr 09, 2013 at 12:27:28PM +0200, Paolo Bonzini wrote:
There is no reason why vhost-net should not work with TCG.
Hence, put the limitation in hw/vhost-net.c, not straight in
the config-*.mak files.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
If you want to enable vhost for tcg
Il 09/04/2013 13:16, Michael S. Tsirkin ha scritto:
There is no reason why vhost-net should not work with TCG.
Hence, put the limitation in hw/vhost-net.c, not straight in
the config-*.mak files.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
If you want to enable vhost for tcg why
Il 02/04/2013 15:49, Paolo Bonzini ha scritto:
No need to put them in config-target.mak.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
configure | 36 +---
1 file changed, 17 insertions(+), 19 deletions(-)
diff --git a/configure b/configure
index
On 2 April 2013 14:49, Paolo Bonzini pbonz...@redhat.com wrote:
No need to put them in config-target.mak.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
-- PMM
Applied. Thanks.
Regards,
Anthony Liguori
No need to put them in config-target.mak.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
configure | 36 +---
1 file changed, 17 insertions(+), 19 deletions(-)
diff --git a/configure b/configure
index fbea75e..04c2618 100755
--- a/configure
+++ b/configure
These variables have not been set for a long time. Do not
include them in config-host.mak.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
configure | 2 --
1 file changed, 2 deletions(-)
diff --git a/configure b/configure
index ec51b0b..54e9017 100755
--- a/configure
+++ b/configure
@@
On 2 April 2013 16:57, Paolo Bonzini pbonz...@redhat.com wrote:
These variables have not been set for a long time. Do not
include them in config-host.mak.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
-- PMM
From: Dunrong Huang huan...@cloud-times.com
--enable-debug-info and --disable-debug-info were not shown
in --help output.
Signed-off-by: Dunrong Huang huan...@cloud-times.com
---
configure | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configure b/configure
index f2af714..61e71fa 100755
This patch let configure tool print out which library
is missing besides the qemu feature name when it fails.
CC: Blue Swirl blauwir...@gmail.com
CC: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Qingtang Zhou zho...@gmail.com
---
configure | 15 ++-
1 file changed, 10
On 15 March 2013 11:46, Qingtang Zhou zho...@gmail.com wrote:
This patch let configure tool print out which library
is missing besides the qemu feature name when it fails.
just fyi, this is going to clash badly with the patch I posted to
the list yesterday to abstract out error message printing
On Fri, Mar 15, 2013 at 7:53 PM, Peter Maydell peter.mayd...@linaro.orgwrote:
On 15 March 2013 11:46, Qingtang Zhou zho...@gmail.com wrote:
This patch let configure tool print out which library
is missing besides the qemu feature name when it fails.
just fyi, this is going to clash badly
On Fri, Mar 01, 2013 at 08:43:18AM +0100, Michal Privoznik wrote:
As of 5a49d3e9 we assume SPICE_PORT_EVENT_BREAK to be defined.
However, it is defined not in 0.12.2 what we require now, but in
0.12.3. Therefore in order to prevent build failure we must
adjust our minimal requirements.
---
Required since v1.4.0-rc0
For SPICE_PORT_EVENT_BREAK used by spice-qemu-char.c since:
commit 5a49d3e9a799b7e1bf87da7ae7f2a719e01da319
Author: Marc-André Lureau marcandre.lur...@gmail.com
Date: Wed Dec 5 16:15:34 2012 +0100
spice-qemu-char: add spiceport chardev
Signed-off-by: Alon Levy
On Sun, Mar 3, 2013 at 4:04 AM, Alon Levy a...@pobox.com wrote:
Required since v1.4.0-rc0
For SPICE_PORT_EVENT_BREAK used by spice-qemu-char.c since:
commit 5a49d3e9a799b7e1bf87da7ae7f2a719e01da319
Author: Marc-André Lureau marcandre.lur...@gmail.com
Date: Wed Dec 5 16:15:34 2012 +0100
As of 5a49d3e9 we assume SPICE_PORT_EVENT_BREAK to be defined.
However, it is defined not in 0.12.2 what we require now, but in
0.12.3. Therefore in order to prevent build failure we must
adjust our minimal requirements.
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Applied. Thanks.
Regards,
Anthony Liguori
From: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
configure |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 0657b1a..cfccec5 100755
--- a/configure
+++ b/configure
@@ -4289,6 +4289,7 @@ FILES=$FILES
Am 02.02.2013 11:46, schrieb Jan Kiszka:
From: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
configure |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 0657b1a..cfccec5 100755
--- a/configure
Am 31.01.2013 11:15, schrieb Michal Privoznik:
Currently, we are enforcing the _FORTIFY_SOURCE=2 without any
previous detection if the macro has been already defined, e.g.
by environment, or is just enabled by compiler by default.
Signed-off-by: Michal Privoznik mpriv...@redhat.com
---
On 01.02.2013 10:54, Andreas Färber wrote:
Am 31.01.2013 11:15, schrieb Michal Privoznik:
Currently, we are enforcing the _FORTIFY_SOURCE=2 without any
previous detection if the macro has been already defined, e.g.
by environment, or is just enabled by compiler by default.
Signed-off-by:
The build is broken on ppc64-linux, possibly only with new binutils:
ld: hw/lm32/../milkymist-tmu2.o: undefined reference to symbol 'XFree'
ld: note: 'XFree' is defined in DSO /lib64/libX11.so.6 so try \
adding it to the linker command line
So let's follow the linker's advice.
Signed-off-by:
Currently, we are enforcing the _FORTIFY_SOURCE=2 without any
previous detection if the macro has been already defined, e.g.
by environment, or is just enabled by compiler by default.
Signed-off-by: Michal Privoznik mpriv...@redhat.com
---
configure | 2 +-
1 file changed, 1 insertion(+), 1
We should be able to cross compile QEMU for ARM64 host.
This is required for trying out ARM 32-bit guest on ARM64 host using QEMU + KVM
ARM64.
Signed-off-by: Anup Patel anup.pa...@linaro.org
---
configure |5 +
1 file changed, 5 insertions(+)
diff --git a/configure b/configure
index
On 8 January 2013 11:05, Anup Patel anup.pa...@linaro.org wrote:
diff --git a/configure b/configure
index fe18ed2..0bfb8bb 100755
--- a/configure
+++ b/configure
@@ -366,6 +366,8 @@ elif check_define __s390__ ; then
fi
elif check_define __arm__ ; then
cpu=arm
+elif check_define
On 8 January 2013 17:38, Peter Maydell peter.mayd...@linaro.org wrote:
On 8 January 2013 11:05, Anup Patel anup.pa...@linaro.org wrote:
diff --git a/configure b/configure
index fe18ed2..0bfb8bb 100755
--- a/configure
+++ b/configure
@@ -366,6 +366,8 @@ elif check_define __s390__ ; then
On 8 January 2013 12:24, Anup Patel anup.pa...@linaro.org wrote:
On 8 January 2013 17:38, Peter Maydell peter.mayd...@linaro.org wrote:
Also, I suspect this isn't the only thing that will be required.
Yes. This patch only tries to make sure that the configure step falls
through and at-least
On 01/08/2013 04:08 AM, Peter Maydell wrote:
The translator sources (as and when we implement a
TCG QEMU target for this) should live under the existing target-arm.
Of this I'm not certain, given that A64 is different enough from A32
to warrant a brand new gcc backend. I havn't tried to
On 8 January 2013 15:57, Richard Henderson r...@twiddle.net wrote:
On 01/08/2013 04:08 AM, Peter Maydell wrote:
The translator sources (as and when we implement a
TCG QEMU target for this) should live under the existing target-arm.
Of this I'm not certain, given that A64 is different enough
Signed-off-by: Stefan Weil s...@weilnetz.de
---
configure |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 837a84a..4bd9e92 100755
--- a/configure
+++ b/configure
@@ -2697,7 +2697,7 @@ if compile_prog ; then
byteswap_h=yes
fi
-# Search for
Thanks, applied.
Regards,
Anthony Liguori
Incremental builds added new lines to that file each time when configure
was run.
Now a new file with a comment line is written.
Signed-off-by: Stefan Weil s...@weilnetz.de
---
The file still contains lots of duplicated entries, but they don't cause
problems.
Regards and happy new year
Stefan
Robert Schiele rschi...@gmail.com writes:
When we build neither any system emulation targets nor the tools there
is actually no need for pixman library. In that case do not enforce
presence of that library on the system.
Signed-off-by: Robert Schiele rschi...@gmail.com
Applied. Thanks.
Probe pkg-config before it is used for the first time (libseccomp check).
Signed-off-by: Stefan Weil s...@weilnetz.de
---
configure | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/configure b/configure
index ecdb33a..728caca 100755
--- a/configure
+++
When we build neither any system emulation targets nor the tools there
is actually no need for pixman library. In that case do not enforce
presence of that library on the system.
Signed-off-by: Robert Schiele rschi...@gmail.com
---
This allows to reduce dependencies in case you build only user
On 4 December 2012 15:58, Robert Schiele rschi...@gmail.com wrote:
diff --git a/target-unicore32/helper.c b/target-unicore32/helper.c
index a9e226b..3e0df33 100644
--- a/target-unicore32/helper.c
+++ b/target-unicore32/helper.c
@@ -13,7 +13,9 @@
#include gdbstub.h
#include helper.h
Am 04.12.2012 16:58, schrieb Robert Schiele:
When we build neither any system emulation targets nor the tools there
is actually no need for pixman library. In that case do not enforce
presence of that library on the system.
Signed-off-by: Robert Schiele rschi...@gmail.com
Reviewed-by:
On 22 November 2012 00:04, Andreas Färber andreas.faer...@web.de wrote:
Am 22.11.2012 00:19, schrieb Peter Maydell:
On 17 November 2012 13:10, Peter Maydell peter.mayd...@linaro.org wrote:
On 17 November 2012 13:02, Andreas Färber andreas.faer...@web.de wrote:
Am 16.11.2012 17:37, schrieb
On Thu, Nov 22, 2012 at 08:33:17AM +, Peter Maydell wrote:
On 22 November 2012 00:04, Andreas F??rber andreas.faer...@web.de wrote:
Am 22.11.2012 00:19, schrieb Peter Maydell:
On 17 November 2012 13:10, Peter Maydell peter.mayd...@linaro.org wrote:
On 17 November 2012 13:02, Andreas
On 22 November 2012 08:38, Brad Smith b...@comstyle.com wrote:
On Thu, Nov 22, 2012 at 08:33:17AM +, Peter Maydell wrote:
On 22 November 2012 00:04, Andreas F??rber andreas.faer...@web.de wrote:
But then again there's the question of why not doing it on Linux as well
now that we seem to
On Thu, Nov 22, 2012 at 08:41:19AM +, Peter Maydell wrote:
On 22 November 2012 08:38, Brad Smith b...@comstyle.com wrote:
On Thu, Nov 22, 2012 at 08:33:17AM +, Peter Maydell wrote:
On 22 November 2012 00:04, Andreas F??rber andreas.faer...@web.de wrote:
But then again there's the
On 17 November 2012 13:10, Peter Maydell peter.mayd...@linaro.org wrote:
On 17 November 2012 13:02, Andreas Färber andreas.faer...@web.de wrote:
Am 16.11.2012 17:37, schrieb Peter Maydell:
+if test $(uname -s) = Darwin; then
+ # On MacOS X the standard supported system compiler is 'cc'
Am 22.11.2012 00:19, schrieb Peter Maydell:
On 17 November 2012 13:10, Peter Maydell peter.mayd...@linaro.org wrote:
On 17 November 2012 13:02, Andreas Färber andreas.faer...@web.de wrote:
Am 16.11.2012 17:37, schrieb Peter Maydell:
+if test $(uname -s) = Darwin; then
+ # On MacOS X the
Am 16.11.2012 17:37, schrieb Peter Maydell:
When building for MacOS X, default the C compiler to 'cc' (usually
clang) rather than 'gcc'. This avoids the Apple 'gcc', which is
generally an elderly llvm-gcc provided mostly for legacy purposes,
in favour of the best supported compiler available
On 17 November 2012 13:02, Andreas Färber andreas.faer...@web.de wrote:
Am 16.11.2012 17:37, schrieb Peter Maydell:
When building for MacOS X, default the C compiler to 'cc' (usually
clang) rather than 'gcc'. This avoids the Apple 'gcc', which is
generally an elderly llvm-gcc provided mostly
When building for MacOS X, default the C compiler to 'cc' (usually
clang) rather than 'gcc'. This avoids the Apple 'gcc', which is
generally an elderly llvm-gcc provided mostly for legacy purposes,
in favour of the best supported compiler available on the platform.
Signed-off-by: Peter Maydell
Thanks, applied.
On Sat, Oct 27, 2012 at 9:19 PM, Peter Maydell peter.mayd...@linaro.org wrote:
gcc will silently accept unrecognized -Wno-wombat warning suppression
options (it only mentions them if it has to print a compiler warning
for some other reason). Since we already run a check for
On 10/28/2012 1:19 AM, Peter Maydell wrote:
gcc will silently accept unrecognized -Wno-wombat warning suppression
options (it only mentions them if it has to print a compiler warning
for some other reason). Since we already run a check for whether gcc
recognizes the warning options we use, we
Thanks, applied.
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 }
Thanks, applied.
On Mon, Aug 20, 2012 at 6:45 PM, 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.
On 10/27/2012 8:51 PM, Blue Swirl wrote:
Thanks, applied.
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
On 27 October 2012 21:32, Igor Mitsyanko i.mitsya...@gmail.com wrote:
I encountered strange behavior of latest mingw gcc, it ignores unrecognized
-Wno-wombat options only in case if no other warnings are issued (configure
gccflags test doesn't issue any), otherwise I get this:
cc1.exe:
gcc will silently accept unrecognized -Wno-wombat warning suppression
options (it only mentions them if it has to print a compiler warning
for some other reason). Since we already run a check for whether gcc
recognizes the warning options we use, we can easily make this use
the positive sense of
Am 27.10.2012 22:32, schrieb Igor Mitsyanko:
On 10/27/2012 8:51 PM, Blue Swirl wrote:
Thanks, applied.
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
Am 27.10.2012 23:19, schrieb Peter Maydell:
gcc will silently accept unrecognized -Wno-wombat warning suppression
options (it only mentions them if it has to print a compiler warning
for some other reason). Since we already run a check for whether gcc
recognizes the warning options we use, we
On 27 October 2012 22:24, Stefan Weil s...@weilnetz.de wrote:
Am 27.10.2012 22:32, schrieb Igor Mitsyanko:
I encountered strange behavior of latest mingw gcc, it ignores
unrecognized -Wno-wombat options only in case if no other warnings are
issued (configure gccflags test doesn't issue any),
Am 27.10.2012 23:35, schrieb Peter Maydell:
On 27 October 2012 22:24, Stefan Weils...@weilnetz.de wrote:
Am 27.10.2012 22:32, schrieb Igor Mitsyanko:
I encountered strange behavior of latest mingw gcc, it ignores
unrecognized -Wno-wombat options only in case if no other warnings are
issued
On 14 October 2012 21:24, Peter Maydell peter.mayd...@linaro.org wrote:
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
701 - 800 of 1161 matches
Mail list logo
