[Qemu-devel] [PATCH] configure: disable qemu-keymap for linux-user qemu

We don't need qemu-keymap when we build only linux-user qemu. When we compile in static mode, the libxkbcommon is detected by configure if the shared one is available, but cannot be linked if the static version is not available. As we don't need it for qemu-linux-user, and we generally need a

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

On 10/13/2017 12:14 PM, Peter Maydell wrote: On 13 October 2017 at 12:46, Thomas Huth wrote: I disagree. If the next OpenBSD release uses Clang by default, we're not building QEMU there with the *working default* C compiler anymore. You're then rather forcing the OpenBSD

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

On Mon, Oct 16, 2017 at 09:44:42AM +0200, Gerd Hoffmann wrote: > Hi, > > > By the way, looks like OpenBSD is also switching to clang by default > > soon: > > > > https://www.phoronix.com/scan.php?page=news_item=OpenBSD-Default- > > Clang > > It did happen already. On openbsd 6.2 (released a

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

Hi, > By the way, looks like OpenBSD is also switching to clang by default > soon: > > https://www.phoronix.com/scan.php?page=news_item=OpenBSD-Default- > Clang It did happen already. On openbsd 6.2 (released a week ago) cc is clang: $ cc --version OpenBSD clang version 4.0.0

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

On 13 October 2017 at 12:46, Thomas Huth wrote: > I disagree. If the next OpenBSD release uses Clang by default, we're not > building QEMU there with the *working default* C compiler anymore. > You're then rather forcing the OpenBSD users then to install an > additional (likely

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

On 13.10.2017 13:38, Daniel P. Berrange wrote: > On Fri, Oct 13, 2017 at 12:55:40PM +0200, Thomas Huth wrote: >> On 13.10.2017 12:52, Thomas Huth wrote: [...] >> By the way, looks like OpenBSD is also switching to clang by default soon: >> >>

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

On Fri, Oct 13, 2017 at 12:55:40PM +0200, Thomas Huth wrote: > On 13.10.2017 12:52, Thomas Huth wrote: > > On 13.10.2017 12:28, Daniel P. Berrange wrote: > >> The system compiler in OpenBSD is gcc 4.2.1 which is too > >> old for our needs. If doing 'pkg_add gcc' you can get a > >> much newer

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

On Fri, Oct 13, 2017 at 12:52:26PM +0200, Thomas Huth wrote: > On 13.10.2017 12:28, Daniel P. Berrange wrote: > > The system compiler in OpenBSD is gcc 4.2.1 which is too > > old for our needs. If doing 'pkg_add gcc' you can get a > > much newer version (4.9.4 in OpenBSD 6.1) which works with > >

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

On 13.10.2017 12:52, Thomas Huth wrote: > On 13.10.2017 12:28, Daniel P. Berrange wrote: >> The system compiler in OpenBSD is gcc 4.2.1 which is too >> old for our needs. If doing 'pkg_add gcc' you can get a >> much newer version (4.9.4 in OpenBSD 6.1) which works with >> QEMU. This installs

Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

On 13.10.2017 12:28, Daniel P. Berrange wrote: > The system compiler in OpenBSD is gcc 4.2.1 which is too > old for our needs. If doing 'pkg_add gcc' you can get a > much newer version (4.9.4 in OpenBSD 6.1) which works with > QEMU. This installs binaries with two naming schemes: > > $ pkg_info

[Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default

The system compiler in OpenBSD is gcc 4.2.1 which is too old for our needs. If doing 'pkg_add gcc' you can get a much newer version (4.9.4 in OpenBSD 6.1) which works with QEMU. This installs binaries with two naming schemes: $ pkg_info -L gcc | grep bin /usr/local/bin/ecpp

Re: [Qemu-devel] [PATCH] configure: Allow --enable-seccomp on s390x, too

On Thu, 14 Sep 2017 12:36:03 +0200 Thomas Huth wrote: > libseccomp supports s390x since version 2.3.0, and I was able to start > a VM with "-sandbox on" without any obvious problems by using this patch, > so it should be safe to allow --enable-seccomp on s390x nowadays, too. >

Re: [Qemu-devel] [PATCH] configure: Allow --enable-seccomp on s390x, too

On 09/14/2017 12:36 PM, Thomas Huth wrote: > libseccomp supports s390x since version 2.3.0, and I was able to start > a VM with "-sandbox on" without any obvious problems by using this patch, > so it should be safe to allow --enable-seccomp on s390x nowadays, too. > > Signed-off-by: Thomas Huth

Re: [Qemu-devel] [PATCH] configure: Allow --enable-seccomp on s390x, too

On Thu, Sep 14, 2017 at 01:55:46PM +0200, Christian Borntraeger wrote: > On 09/14/2017 12:36 PM, Thomas Huth wrote: > > libseccomp supports s390x since version 2.3.0, and I was able to start > > a VM with "-sandbox on" without any obvious problems by using this patch, > > so it should be safe to

Re: [Qemu-devel] [PATCH] configure: Allow --enable-seccomp on s390x, too

On 09/14/2017 12:36 PM, Thomas Huth wrote: > libseccomp supports s390x since version 2.3.0, and I was able to start > a VM with "-sandbox on" without any obvious problems by using this patch, > so it should be safe to allow --enable-seccomp on s390x nowadays, too. Seems to work fine on s390x.

Re: [Qemu-devel] [PATCH] configure: Allow --enable-seccomp on s390x, too

On Thu, Sep 14, 2017 at 12:36:03PM +0200, Thomas Huth wrote: > libseccomp supports s390x since version 2.3.0, and I was able to start > a VM with "-sandbox on" without any obvious problems by using this patch, > so it should be safe to allow --enable-seccomp on s390x nowadays, too. > I don't

[Qemu-devel] [PATCH] configure: Allow --enable-seccomp on s390x, too

libseccomp supports s390x since version 2.3.0, and I was able to start a VM with "-sandbox on" without any obvious problems by using this patch, so it should be safe to allow --enable-seccomp on s390x nowadays, too. Signed-off-by: Thomas Huth --- configure | 2 +- 1 file

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On 4 September 2017 at 18:19, Peter Maydell wrote: > Nobody has mentioned AIX host support on the mailing list for years, > and we have no test systems for it so it is most likely broken. > We've advertised in configure for two releases now that we plan > to drop support

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On 5 September 2017 at 08:36, Thomas Huth wrote: > OTOH, AIX support is really very, very like broken since years It turns out there's an AIX box in the gcc compile farm, so just out of curiosity I had a look. (1) we don't recognize the cpu so you have to pass --cpu=ppc64 (2)

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On Mon, Sep 04, 2017 at 06:19:00PM +0100, Peter Maydell wrote: > Nobody has mentioned AIX host support on the mailing list for years, > and we have no test systems for it so it is most likely broken. > We've advertised in configure for two releases now that we plan > to drop support for this host

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On 05.09.2017 10:04, Daniel P. Berrange wrote: > On Mon, Sep 04, 2017 at 08:09:17PM +0200, Thomas Huth wrote: >> On 04.09.2017 19:19, Peter Maydell wrote: >>> Nobody has mentioned AIX host support on the mailing list for years, >>> and we have no test systems for it so it is most likely broken.

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On Mon, Sep 04, 2017 at 08:09:17PM +0200, Thomas Huth wrote: > On 04.09.2017 19:19, Peter Maydell wrote: > > Nobody has mentioned AIX host support on the mailing list for years, > > and we have no test systems for it so it is most likely broken. > > We've advertised in configure for two releases

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On Mon, 4 Sep 2017 18:19:00 +0100 Peter Maydell wrote: > Nobody has mentioned AIX host support on the mailing list for years, > and we have no test systems for it so it is most likely broken. > We've advertised in configure for two releases now that we plan > to drop

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On 05.09.2017 09:16, Markus Armbruster wrote: > Peter Maydell writes: > >> On 4 September 2017 at 19:09, Thomas Huth wrote: >>> On 04.09.2017 19:19, Peter Maydell wrote: Nobody has mentioned AIX host support on the mailing list for years,

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

Peter Maydell writes: > On 4 September 2017 at 19:09, Thomas Huth wrote: >> On 04.09.2017 19:19, Peter Maydell wrote: >>> Nobody has mentioned AIX host support on the mailing list for years, >>> and we have no test systems for it so it is most likely

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On 04.09.2017 19:19, Peter Maydell wrote: > Nobody has mentioned AIX host support on the mailing list for years, > and we have no test systems for it so it is most likely broken. > We've advertised in configure for two releases now that we plan > to drop support for this host OS, and have had no

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

Le 04/09/2017 à 19:19, Peter Maydell a écrit : > Nobody has mentioned AIX host support on the mailing list for years, > and we have no test systems for it so it is most likely broken. > We've advertised in configure for two releases now that we plan > to drop support for this host OS, and have had

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On 4 September 2017 at 19:09, Thomas Huth wrote: > On 04.09.2017 19:19, Peter Maydell wrote: >> Nobody has mentioned AIX host support on the mailing list for years, >> and we have no test systems for it so it is most likely broken. >> We've advertised in configure for two

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On 04.09.2017 19:19, Peter Maydell wrote: > Nobody has mentioned AIX host support on the mailing list for years, > and we have no test systems for it so it is most likely broken. > We've advertised in configure for two releases now that we plan > to drop support for this host OS, and have had no

Re: [Qemu-devel] [PATCH] configure: Drop AIX host support

On 09/04/2017 02:19 PM, Peter Maydell wrote: Nobody has mentioned AIX host support on the mailing list for years, and we have no test systems for it so it is most likely broken. We've advertised in configure for two releases now that we plan to drop support for this host OS, and have had no

[Qemu-devel] [PATCH] configure: Drop AIX host support

Nobody has mentioned AIX host support on the mailing list for years, and we have no test systems for it so it is most likely broken. We've advertised in configure for two releases now that we plan to drop support for this host OS, and have had no complaints. Drop the AIX host support code. We can

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

On 07/25/2017 10:28 PM, Philippe Mathieu-Daudé wrote: >>> - rm -f $(filter-out %.tlb,$(TOOLS)) $(HELPERS-y) qemu-ga TAGS >>> cscope.* *.pod *~ */*~ >>> + rm -f $(filter-out %.tlb,$(TOOLS)) $(HELPERS-y) qemu-ga${EXESUF} >>> TAGS cscope.* *.pod *~ */*~ >>> >>> It's a bit ugly since `rm -f

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

As noticed by Michael Roth the ./configure entry for qemu-ga is missing the $(EXESUF) on purpose (see fafcaf1d). Patch dropped for 2.10 On 07/24/2017 10:15 PM, Philippe Mathieu-Daudé wrote: Reported-by: Sameeh Jubran Signed-off-by: Philippe Mathieu-Daudé

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

On 07/25/2017 11:56 PM, Michael Roth wrote: Quoting Michael Roth (2017-07-25 21:53:41) Quoting Philippe Mathieu-Daudé (2017-07-25 20:45:31) [...] That change was done explicitly via fafcaf1d so that `make qemu-ga` and `make` without --disable-tools specified to configure will generate the MSI

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

Quoting Michael Roth (2017-07-25 21:56:14) > Quoting Michael Roth (2017-07-25 21:53:41) > > Quoting Philippe Mathieu-Daudé (2017-07-25 20:45:31) > > > Hi Michael, > > > > > > On 07/25/2017 08:03 PM, Michael Roth wrote: > > > > Quoting Philippe Mathieu-Daudé (2017-07-24 20:15:30) > > > >>

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

Quoting Michael Roth (2017-07-25 21:53:41) > Quoting Philippe Mathieu-Daudé (2017-07-25 20:45:31) > > Hi Michael, > > > > On 07/25/2017 08:03 PM, Michael Roth wrote: > > > Quoting Philippe Mathieu-Daudé (2017-07-24 20:15:30) > > >> Reported-by: Sameeh Jubran > > >>

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

Quoting Philippe Mathieu-Daudé (2017-07-25 20:45:31) > Hi Michael, > > On 07/25/2017 08:03 PM, Michael Roth wrote: > > Quoting Philippe Mathieu-Daudé (2017-07-24 20:15:30) > >> Reported-by: Sameeh Jubran > >> Signed-off-by: Philippe Mathieu-Daudé > >> --- >

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

Hi Michael, On 07/25/2017 08:03 PM, Michael Roth wrote: Quoting Philippe Mathieu-Daudé (2017-07-24 20:15:30) Reported-by: Sameeh Jubran Signed-off-by: Philippe Mathieu-Daudé --- original report from Sameeh Jubran:

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

Quoting Philippe Mathieu-Daudé (2017-07-24 20:15:30) > Reported-by: Sameeh Jubran > Signed-off-by: Philippe Mathieu-Daudé > --- > original report from Sameeh Jubran: > http://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg00906.html AFAICT the issue

Re: [Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

On Mon, Jul 24, 2017 at 10:15:30PM -0300, Philippe Mathieu-Daudé wrote: > Reported-by: Sameeh Jubran > Signed-off-by: Philippe Mathieu-Daudé > --- > original report from Sameeh Jubran: > http://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg00906.html >

[Qemu-devel] [PATCH] configure: fix qemu-ga missing '.exe' extension on windows

Reported-by: Sameeh Jubran Signed-off-by: Philippe Mathieu-Daudé --- original report from Sameeh Jubran: http://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg00906.html Makefile | 2 +- configure | 2 +- 2 files changed, 2 insertions(+), 2

Re: [Qemu-devel] [PATCH] configure: Never use 'uname' to identify target OS

On 13 July 2017 at 16:15, Peter Maydell wrote: > For a very long time we have used 'uname -s' as our fallback if > we don't identify the target OS using a compiler #define. This > obviously doesn't work for cross-compilation, and we've had > a comment suggesting we fix

Re: [Qemu-devel] [PATCH] configure: Drop ancient Solaris 9 and earlier support

On 13 July 2017 at 15:21, Peter Maydell wrote: > Solaris 9 was released in 2002, its successor Solaris 10 was > released in 2005, and Solaris 9 was end-of-lifed in 2014. > Nobody has stepped forward to express interest in supporting > Solaris of any flavour, so removing

Re: [Qemu-devel] [PATCH] configure: add -Wno-format-truncation to QEMU_CFLAGS

On 07/20/2017 05:33 PM, Daniel P. Berrange wrote: On Thu, Jul 20, 2017 at 04:57:29PM +0200, Eduardo Otubo wrote: Compilation breaks on GCC 7.1.1 20170622 (Fedora 26), thus adding -Wno-format-truncation to QEMU_CFLAGS on configure script is neecssary. hw/usb/bus.c: In function

Re: [Qemu-devel] [PATCH] configure: add -Wno-format-truncation to QEMU_CFLAGS

On Thu, Jul 20, 2017 at 04:57:29PM +0200, Eduardo Otubo wrote: > Compilation breaks on GCC 7.1.1 20170622 (Fedora 26), thus adding > -Wno-format-truncation to QEMU_CFLAGS on configure script is neecssary. > > hw/usb/bus.c: In function ‘usb_port_location’: > hw/usb/bus.c:410:66: error:

Re: [Qemu-devel] [PATCH] configure: add -Wno-format-truncation to QEMU_CFLAGS

Hi, This series failed build test on FreeBSD host. Please find the details below. Type: series Message-id: 20170720145729.22141-1-ot...@redhat.com Subject: [Qemu-devel] [PATCH] configure: add -Wno-format-truncation to QEMU_CFLAGS === TEST SCRIPT BEGIN === #!/bin/sh # Testing script

[Qemu-devel] [PATCH] configure: add -Wno-format-truncation to QEMU_CFLAGS

Compilation breaks on GCC 7.1.1 20170622 (Fedora 26), thus adding -Wno-format-truncation to QEMU_CFLAGS on configure script is neecssary. hw/usb/bus.c: In function ‘usb_port_location’: hw/usb/bus.c:410:66: error: ‘%d’ directive output may be truncated writing between 1 and 11 bytes into

[Qemu-devel] [PATCH] configure: Never use 'uname' to identify target OS

For a very long time we have used 'uname -s' as our fallback if we don't identify the target OS using a compiler #define. This obviously doesn't work for cross-compilation, and we've had a comment suggesting we fix this in configure for a long time. Since we now have an exhaustive list of which

Re: [Qemu-devel] [PATCH] configure: Drop ancient Solaris 9 and earlier support

On Thu, Jul 13, 2017 at 03:21:37PM +0100, Peter Maydell wrote: > Solaris 9 was released in 2002, its successor Solaris 10 was > released in 2005, and Solaris 9 was end-of-lifed in 2014. > Nobody has stepped forward to express interest in supporting > Solaris of any flavour, so removing support for

Re: [Qemu-devel] [PATCH] configure: Drop ancient Solaris 9 and earlier support

On 07/13/2017 09:21 AM, Peter Maydell wrote: > Solaris 9 was released in 2002, its successor Solaris 10 was > released in 2005, and Solaris 9 was end-of-lifed in 2014. > Nobody has stepped forward to express interest in supporting > Solaris of any flavour, so removing support for the ancient >

[Qemu-devel] [PATCH] configure: Drop ancient Solaris 9 and earlier support

Solaris 9 was released in 2002, its successor Solaris 10 was released in 2005, and Solaris 9 was end-of-lifed in 2014. Nobody has stepped forward to express interest in supporting Solaris of any flavour, so removing support for the ancient versions seems uncontroversial. In particular, this

Re: [Qemu-devel] [PATCH] configure: Handle having no c++ compiler in FORTIFY_SOURCE check

Applied to trivial, thanks! /mjt

Re: [Qemu-devel] [PATCH] configure: Fix build with pkg-config and --static --enable-sdl

13.06.2017 21:00, Thomas Huth wrote: > The configure script prefers pkg-config over sdl-config, but > the "--static-libs" parameter only exists for the latter. With > pkg-config, "--static --libs" have to be used instead. Applied to -trivial, thanks! /mjt

Re: [Qemu-devel] [PATCH] configure: Handle having no c++ compiler in FORTIFY_SOURCE check

On 06/26/2017 12:25 PM, Peter Maydell wrote: Our FORTIFY_SOURCE check assumes that $cxx refers to a working C++ compiler, with the result that if you don't happen to have one then configure will spuriously print configure: line 4685: c++: command not found Fix this by adding a 'has $cxx'

[Qemu-devel] [PATCH] configure: Handle having no c++ compiler in FORTIFY_SOURCE check

Our FORTIFY_SOURCE check assumes that $cxx refers to a working C++ compiler, with the result that if you don't happen to have one then configure will spuriously print configure: line 4685: c++: command not found Fix this by adding a 'has $cxx' check. Signed-off-by: Peter Maydell

Re: [Qemu-devel] [PATCH] configure: Define NCURSES_WIDECHAR if we're using curses

On 2 June 2017 at 15:35, Peter Maydell wrote: > We want the wide character functions from the ncurses header. > Unfortunately it doesn't provide them by default, but only > if either: > * NCURSES_WIDECHAR is defined (for ncurses 20111030 and up) > *

Re: [Qemu-devel] [PATCH] configure: Fix build with pkg-config and --static --enable-sdl

Hi, This series failed automatic build test. Please find the testing commands and their output below. If you have docker installed, you can probably reproduce it locally. Type: series Subject: [Qemu-devel] [PATCH] configure: Fix build with pkg-config and --static --enable-sdl Message-id

[Qemu-devel] [PATCH] configure: Fix build with pkg-config and --static --enable-sdl

The configure script prefers pkg-config over sdl-config, but the "--static-libs" parameter only exists for the latter. With pkg-config, "--static --libs" have to be used instead. Buglink: https://bugs.launchpad.net/qemu/+bug/984516 Signed-off-by: Thomas Huth --- configure | 6

Re: [Qemu-devel] [PATCH] configure: Define NCURSES_WIDECHAR if we're using curses

On 06/03/17 11:43, Kamil Rytarowski wrote: > On 02.06.2017 23:58, Laszlo Ersek wrote: >> On 06/02/17 16:35, Peter Maydell wrote: >>> We want the wide character functions from the ncurses header. >>> Unfortunately it doesn't provide them by default, but only >>> if either: >>> * NCURSES_WIDECHAR

Re: [Qemu-devel] [PATCH] configure: Define NCURSES_WIDECHAR if we're using curses

On 03.06.2017 12:13, Rainer Müller wrote: > On 2017-06-02 16:35, Peter Maydell wrote: >> diff --git a/configure b/configure >> index 0586ec9..6aca5d1 100755 >> --- a/configure >> +++ b/configure >> @@ -3053,6 +3053,8 @@ int main(void) { >> EOF >>IFS=: >>for curses_inc in $curses_inc_list;

Re: [Qemu-devel] [PATCH] configure: Define NCURSES_WIDECHAR if we're using curses

On 2017-06-02 16:35, Peter Maydell wrote: > diff --git a/configure b/configure > index 0586ec9..6aca5d1 100755 > --- a/configure > +++ b/configure > @@ -3053,6 +3053,8 @@ int main(void) { > EOF >IFS=: >for curses_inc in $curses_inc_list; do > +# Make sure we get the wide character

Re: [Qemu-devel] [PATCH] configure: Define NCURSES_WIDECHAR if we're using curses

On 02.06.2017 23:58, Laszlo Ersek wrote: > On 06/02/17 16:35, Peter Maydell wrote: >> We want the wide character functions from the ncurses header. >> Unfortunately it doesn't provide them by default, but only >> if either: >> * NCURSES_WIDECHAR is defined (for ncurses 20111030 and up) >> *

Re: [Qemu-devel] [PATCH] configure: Define NCURSES_WIDECHAR if we're using curses

On 06/02/17 16:35, Peter Maydell wrote: > We want the wide character functions from the ncurses header. > Unfortunately it doesn't provide them by default, but only > if either: > * NCURSES_WIDECHAR is defined (for ncurses 20111030 and up) > * _XOPEN_SOURCE/_XOPEN_SOURCE_EXTENDED are suitably

[Qemu-devel] [PATCH] configure: Define NCURSES_WIDECHAR if we're using curses

We want the wide character functions from the ncurses header. Unfortunately it doesn't provide them by default, but only if either: * NCURSES_WIDECHAR is defined (for ncurses 20111030 and up) * _XOPEN_SOURCE/_XOPEN_SOURCE_EXTENDED are suitably defined So far we have been implicitly relying on

Re: [Qemu-devel] [PATCH] configure: Detect native NetBSD curses(3)

26.04.2017 13:50, Kamil Rytarowski wrote: > NetBSD ships with traditional BSD curses with compatibility with ncurses. > qemu works nicely with the basesystem version of curses(3) from NetBSD. > > The only mismatch between curses(3) and ncurses is the lack of > curses_version() in the NetBSD

Re: [Qemu-devel] [PATCH] configure: Detect native NetBSD curses(3)

Hi Kamil, On 04/26/2017 07:50 AM, Kamil Rytarowski wrote: NetBSD ships with traditional BSD curses with compatibility with ncurses. qemu works nicely with the basesystem version of curses(3) from NetBSD. The only mismatch between curses(3) and ncurses is the lack of curses_version() in the

Re: [Qemu-devel] [PATCH] configure: Detect native NetBSD curses(3)

Ping? Could someone please put it on the pull-request? Adding qemu-trivial@. On 08.05.2017 13:33, Alex Bennée wrote: > > Kamil Rytarowski writes: > >> NetBSD ships with traditional BSD curses with compatibility with ncurses. >> qemu works nicely with the basesystem version of

Re: [Qemu-devel] [PATCH] configure: Remove -lxencall for Xen detection

On Thu, 11 May 2017, Anthony PERARD wrote: > QEMU does not depends on libxencall, it was added because it was a > missing link dependency of libxendevicemodel, but now the later should > be built properly. > > Signed-off-by: Anthony PERARD Reviewed-by: Stefano

[Qemu-devel] [PATCH] configure: Remove -lxencall for Xen detection

QEMU does not depends on libxencall, it was added because it was a missing link dependency of libxendevicemodel, but now the later should be built properly. Signed-off-by: Anthony PERARD --- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [Qemu-devel] [PATCH] configure: Detect native NetBSD curses(3)

Kamil Rytarowski writes: > NetBSD ships with traditional BSD curses with compatibility with ncurses. > qemu works nicely with the basesystem version of curses(3) from NetBSD. > > The only mismatch between curses(3) and ncurses is the lack of > curses_version() in the NetBSD

Re: [Qemu-devel] [PATCH] configure: Detect native NetBSD curses(3)

x1 ping On 26.04.2017 12:50, Kamil Rytarowski wrote: > NetBSD ships with traditional BSD curses with compatibility with ncurses. > qemu works nicely with the basesystem version of curses(3) from NetBSD. > > The only mismatch between curses(3) and ncurses is the lack of > curses_version() in the

Re: [Qemu-devel] [PATCH] configure: fix trace backend list for out-of-tree builds

On 26 April 2017 at 14:21, Greg Kurz wrote: > Since commit "c53eeaf75a04 configure: eliminate Python dependency for > --help", configure --help fails to produce the list of available trace > backends if invoked out-of-tree. It also spits the following error: > > grep:

[Qemu-devel] [PATCH] configure: fix trace backend list for out-of-tree builds

Since commit "c53eeaf75a04 configure: eliminate Python dependency for --help", configure --help fails to produce the list of available trace backends if invoked out-of-tree. It also spits the following error: grep: scripts/tracetool/backend/*.py: No such file or directory This patch simply adds

[Qemu-devel] [PATCH] configure: Detect native NetBSD curses(3)

NetBSD ships with traditional BSD curses with compatibility with ncurses. qemu works nicely with the basesystem version of curses(3) from NetBSD. The only mismatch between curses(3) and ncurses is the lack of curses_version() in the NetBSD version. This function is used solely in the configure

Re: [Qemu-devel] [PATCH] configure: eliminate Python dependency for --help

On 28 March 2017 at 14:08, Stefan Hajnoczi wrote: > The ./configure script should produce --help output even if Python is > not installed. > > Listing trace backends is simple: show the names of all Python modules > in scripts/tracetool/backend/ whose source code contains

[Qemu-devel] [PATCH] configure: eliminate Python dependency for --help

The ./configure script should produce --help output even if Python is not installed. Listing trace backends is simple: show the names of all Python modules in scripts/tracetool/backend/ whose source code contains 'PUBLIC = True'. Perform the backend enumeration in shell instead of Python so that

Re: [Qemu-devel] [PATCH] configure: Fix cut-n-paste errors in OS deprecation warning

On 23 March 2017 at 08:58, Stefan Hajnoczi wrote: > On Tue, Mar 21, 2017 at 06:08:49PM +, Peter Maydell wrote: >> Fix some cut-and-paste errors in the OS deprecation warning >> pointed out by Thomas Huth. >> >> Reported-by: Thomas Huth >> Signed-off-by:

Re: [Qemu-devel] [PATCH] configure: Fix cut-n-paste errors in OS deprecation warning

On Tue, Mar 21, 2017 at 06:08:49PM +, Peter Maydell wrote: > Fix some cut-and-paste errors in the OS deprecation warning > pointed out by Thomas Huth. > > Reported-by: Thomas Huth > Signed-off-by: Peter Maydell > --- > configure | 4 ++-- > 1

[Qemu-devel] [PATCH] configure: Fix cut-n-paste errors in OS deprecation warning

Fix some cut-and-paste errors in the OS deprecation warning pointed out by Thomas Huth. Reported-by: Thomas Huth Signed-off-by: Peter Maydell --- configure | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure b/configure

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On 03/17/2017 09:52 PM, Peter Maydell wrote: On 17 March 2017 at 11:49, Daniel P. Berrange wrote: On Fri, Mar 17, 2017 at 11:08:22AM +, Peter Maydell wrote: We plan to drop support in a future QEMU release for host OSes and host architectures for which we have no test

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On 17 March 2017 at 11:08, Peter Maydell wrote: > This commit flags up as deprecated the CPU architectures: > * ia64 > * sparc > * anything which we don't have a TCG port for >(and which was presumably using TCI) > and the OSes: > * Cygwin > * GNU/kFreeBSD > *

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On 17.03.2017 14:22, Peter Maydell wrote: > On 17 March 2017 at 13:19, Thomas Huth wrote: >> On 17.03.2017 12:52, Peter Maydell wrote: >>> On 17 March 2017 at 11:49, Daniel P. Berrange wrote: On Fri, Mar 17, 2017 at 11:08:22AM +, Peter Maydell

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On 17 March 2017 at 13:19, Thomas Huth wrote: > So could you maybe change your patch that it does not warn when the user > has run configure with the "--enable-tcg-interpreter" option? Nope. I specifically don't want to enable support for TCI on random who-knows-what-this-is

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On 17 March 2017 at 13:19, Thomas Huth wrote: > On 17.03.2017 12:52, Peter Maydell wrote: >> On 17 March 2017 at 11:49, Daniel P. Berrange wrote: >>> On Fri, Mar 17, 2017 at 11:08:22AM +, Peter Maydell wrote: We plan to drop support in a future

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On 17.03.2017 12:52, Peter Maydell wrote: > On 17 March 2017 at 11:49, Daniel P. Berrange wrote: >> On Fri, Mar 17, 2017 at 11:08:22AM +, Peter Maydell wrote: >>> We plan to drop support in a future QEMU release for host OSes >>> and host architectures for which we have

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On Fri, 2017-03-17 at 11:56 +, Daniel P. Berrange wrote: > > Yeah. I'm just struggling with setting up a FreeBSD VM so we > > can compile test that. Interesting that GNU/kFreeBSD has users. >  > I wouldn't go so far as to say GNU/kFreeBSD has users. It had a few people > who have noticed bits

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On Fri, Mar 17, 2017 at 11:49:53AM +, Daniel P. Berrange wrote: > On Fri, Mar 17, 2017 at 11:08:22AM +, Peter Maydell wrote: > > This list is definitely too all-encompassing, and we should > > move at least some of the BSDs into "not-deprecated". > > I'm posting the patch for the moment

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On Fri, Mar 17, 2017 at 11:52:01AM +, Peter Maydell wrote: > On 17 March 2017 at 11:49, Daniel P. Berrange wrote: > > On Fri, Mar 17, 2017 at 11:08:22AM +, Peter Maydell wrote: > >> We plan to drop support in a future QEMU release for host OSes > >> and host

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On 17 March 2017 at 11:49, Daniel P. Berrange wrote: > On Fri, Mar 17, 2017 at 11:08:22AM +, Peter Maydell wrote: >> We plan to drop support in a future QEMU release for host OSes >> and host architectures for which we have no test machine where >> we can build and run

Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts

On Fri, Mar 17, 2017 at 11:08:22AM +, Peter Maydell wrote: > We plan to drop support in a future QEMU release for host OSes > and host architectures for which we have no test machine where > we can build and run tests. For the 2.9 release, make configure > print a warning if it is run on such

[Qemu-devel] [PATCH] configure: Warn about deprecated hosts

We plan to drop support in a future QEMU release for host OSes and host architectures for which we have no test machine where we can build and run tests. For the 2.9 release, make configure print a warning if it is run on such a host, so that the user has some warning of the plans and can

Re: [Qemu-devel] [PATCH] configure: add the missing help output for optional features

On 10/03/2017 11:14, Lin Ma wrote: > Signed-off-by: Lin Ma > --- > configure | 12 > 1 file changed, 12 insertions(+) > > diff --git a/configure b/configure > index 6c21975..2603e10 100755 > --- a/configure > +++ b/configure > @@ -1335,6 +1335,12 @@ Advanced

[Qemu-devel] [PATCH] configure: add the missing help output for optional features

Signed-off-by: Lin Ma --- configure | 12 1 file changed, 12 insertions(+) diff --git a/configure b/configure index 6c21975..2603e10 100755 --- a/configure +++ b/configure @@ -1335,6 +1335,12 @@ Advanced options (experts only): --with-vss-sdk=SDK-path enable

[Qemu-devel] [PATCH] configure: allow enabling seccomp on s390x

Allow enabling seccomp support on s390x if sufficient build dependencies are provided. Signed-off-by: Christian Ehrhardt --- configure | 3 +++ 1 file changed, 3 insertions(+) diff --git a/configure b/configure index 86f5214..5056ba9 100755 --- a/configure +++

Re: [Qemu-devel] [PATCH] configure: For libgcrypt if pkg-config is available use it

On 5 January 2017 at 01:27, Daniel P. Berrange wrote: > On Thu, Jan 05, 2017 at 12:56:52AM +1000, Nathan Rossi wrote: >> If libgcrypt info is available with pkg-config use it over using the >> libgcrypt-config. pkg-config is preferred due to is compatibility with >>

Re: [Qemu-devel] [PATCH] configure: For libgcrypt if pkg-config is available use it

On Thu, Jan 05, 2017 at 12:56:52AM +1000, Nathan Rossi wrote: > If libgcrypt info is available with pkg-config use it over using the > libgcrypt-config. pkg-config is preferred due to is compatibility with > cross-compilation (where you cannot execute the targets version of > libgcrypt-config).

[Qemu-devel] [PATCH] configure: For libgcrypt if pkg-config is available use it

If libgcrypt info is available with pkg-config use it over using the libgcrypt-config. pkg-config is preferred due to is compatibility with cross-compilation (where you cannot execute the targets version of libgcrypt-config). This change makes configure check for libgcrypt in pkg-config first,

Re: [Qemu-devel] [PATCH] configure: fix LTTng UST tracing backend detection

On Mon, Nov 28, 2016 at 10:52:17AM -0500, Francis Deslauriers wrote: > The detection program needs to be linked with -ldl to build succesfully > with recent versions of LTTng-UST. > > We also need to add -ldl to the libs required to build the LTTng-UST > backend (lttng_ust_libs). > >

[Qemu-devel] [PATCH] configure: fix LTTng UST tracing backend detection

The detection program needs to be linked with -ldl to build succesfully with recent versions of LTTng-UST. We also need to add -ldl to the libs required to build the LTTng-UST backend (lttng_ust_libs). Signed-off-by: Francis Deslauriers --- configure | 4 ++--

Re: [Qemu-devel] [PATCH] configure: Always compile with -fwrapv

On 12 September 2016 at 18:06, Paolo Bonzini wrote: > > > On 12/09/2016 15:10, Peter Maydell wrote: >> QEMU's code relies on left shifts of signed integers always >> being defined behaviour with the obvious 2s-complement >> semantics. The only way to tell the compiler (and

<    1   2   3   4   5   6   7   8   9   10   >