From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51929) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gHVXv-0001s5-5y for qemu-devel@nongnu.org; Tue, 30 Oct 2018 11:03:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gHVXq-0001fs-K9 for qemu-devel@nongnu.org; Tue, 30 Oct 2018 11:03:07 -0400 Received: from mail-wr1-f66.google.com ([209.85.221.66]:36785) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gHVXq-0001dn-Ct for qemu-devel@nongnu.org; Tue, 30 Oct 2018 11:03:02 -0400 Received: by mail-wr1-f66.google.com with SMTP id y16so12974467wrw.3 for ; Tue, 30 Oct 2018 08:03:02 -0700 (PDT) References: <20181030125005.28151-1-peter.maydell@linaro.org> From: =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= Message-ID: Date: Tue, 30 Oct 2018 16:02:59 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/3] configure: symlink directories, not wildcarded files List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , QEMU Developers Cc: "patches@linaro.org" , "Michael S. Tsirkin" On 30/10/18 14:08, Peter Maydell wrote: > On 30 October 2018 at 13:01, Peter Maydell wrote: >> ...having sent this out and moved on to something else, I have >> discovered a problem with it. If you configure a build tree >> using this, and then switch back to a git branch which has >> the older configure, then that configure will end up trashing >> all the tests/acpi-test-data and tests/hex-loader-check-data >> files in the source tree by replacing them with symlinks to >> themselves... This is fixable by doing "git checkout tests" >> but it's a bit of a landmine for bisection :-( Got there now switching to another series after testing yours ;) > Maybe we should standardize on having all data files for tests > be in tests/data, which is and has always been a symlink to > a directory. That would avoid this problem with old versions > of configure mangling the source directory by accident. This seems the clever move. > > thanks > -- PMM >