Re: [PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread Carlo Arenas
On Tue, Mar 31, 2020 at 3:38 AM Daniel P. Berrangé wrote: > Running configure directly from the source directory is a build > configuration that will go away in future. It is also not currently > s/in future/in the future/g Carlo

Re: [PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread Kevin Wolf
Am 31.03.2020 um 16:56 hat Daniel P. Berrangé geschrieben: > On Tue, Mar 31, 2020 at 09:44:37AM -0500, Eric Blake wrote: > > On 3/31/20 5:37 AM, Daniel P. Berrangé wrote: > > > Running configure directly from the source directory is a build > > > configuration that will go away in future. It is als

Re: [PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread BALATON Zoltan
On Tue, 31 Mar 2020, Eric Blake wrote: On 3/31/20 5:37 AM, Daniel P. Berrangé wrote: Running configure directly from the source directory is a build configuration that will go away in future. It is also not currently covered by any automated testing. Display a deprecation warning if the user att

Re: [PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread Daniel P . Berrangé
On Tue, Mar 31, 2020 at 09:44:37AM -0500, Eric Blake wrote: > On 3/31/20 5:37 AM, Daniel P. Berrangé wrote: > > Running configure directly from the source directory is a build > > configuration that will go away in future. It is also not currently > > covered by any automated testing. Display a dep

Re: [PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread Eric Blake
On 3/31/20 5:37 AM, Daniel P. Berrangé wrote: Running configure directly from the source directory is a build configuration that will go away in future. It is also not currently covered by any automated testing. Display a deprecation warning if the user attempts to use an in-srcdir build setup, s

Re: [PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread Philippe Mathieu-Daudé
On 3/31/20 1:41 PM, Daniel P. Berrangé wrote: On Tue, Mar 31, 2020 at 01:11:45PM +0200, Philippe Mathieu-Daudé wrote: On 3/31/20 12:37 PM, Daniel P. Berrangé wrote: Running configure directly from the source directory is a build configuration that will go away in future. It is also not currentl

Re: [PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread Daniel P . Berrangé
On Tue, Mar 31, 2020 at 01:11:45PM +0200, Philippe Mathieu-Daudé wrote: > On 3/31/20 12:37 PM, Daniel P. Berrangé wrote: > > Running configure directly from the source directory is a build > > configuration that will go away in future. It is also not currently > > covered by any automated testing.

Re: [PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread Philippe Mathieu-Daudé
On 3/31/20 12:37 PM, Daniel P. Berrangé wrote: Running configure directly from the source directory is a build configuration that will go away in future. It is also not currently covered by any automated testing. Display a deprecation warning if the user attempts to use an in-srcdir build setup,

[PATCH] configure: warn if not using a separate build directory

2020-03-31 Thread Daniel P . Berrangé
Running configure directly from the source directory is a build configuration that will go away in future. It is also not currently covered by any automated testing. Display a deprecation warning if the user attempts to use an in-srcdir build setup, so that they are aware that they're building QEMU