Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory

2020-04-06 Thread Daniel P . Berrangé
On Sun, Apr 05, 2020 at 03:38:55PM +0100, Peter Maydell wrote: > On Fri, 3 Apr 2020 at 14:53, 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

Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory

2020-04-05 Thread Aleksandar Markovic
11:14 Sub, 04.04.2020. Peter Maydell је написао/ла: > > On Fri, 3 Apr 2020 at 23:35, Aleksandar Markovic > wrote: > > But, Eric, while, to some extent I understand your motivation and the idea, there are still features working in in-tree builds only (some coccinele scenarios, and some

Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory

2020-04-05 Thread Aleksandar Markovic
16:39 Ned, 05.04.2020. Peter Maydell је написао/ла: > > On Fri, 3 Apr 2020 at 14:53, 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 v4 for-5.0] configure: warn if not using a separate build directory

2020-04-05 Thread Peter Maydell
On Fri, 3 Apr 2020 at 14:53, 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

Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory

2020-04-04 Thread Peter Maydell
On Fri, 3 Apr 2020 at 23:35, Aleksandar Markovic wrote: > But, Eric, while, to some extent I understand your motivation and the idea, > there are still features working in in-tree builds only (some coccinele > scenarios, and some gcov-related scenarios - and perhaps others that nobody > seems

Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory

2020-04-03 Thread Aleksandar Markovic
16:44 Pet, 03.04.2020. Eric Blake је написао/ла: > > On 4/3/20 9:02 AM, Eric Blake wrote: > > On 4/3/20 8:53 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

Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory

2020-04-03 Thread BALATON Zoltan
On Fri, 3 Apr 2020, Eric Blake wrote: On 4/3/20 8:53 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

Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory

2020-04-03 Thread Eric Blake
On 4/3/20 9:02 AM, Eric Blake wrote: On 4/3/20 8:53 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

Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory

2020-04-03 Thread Eric Blake
On 4/3/20 8:53 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,