From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1028 invoked by alias); 3 Aug 2015 18:10:20 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 589 invoked by uid 89); 3 Aug 2015 18:10:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 X-HELO: usevmg21.ericsson.net Received: from usevmg21.ericsson.net (HELO usevmg21.ericsson.net) (198.24.6.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 03 Aug 2015 18:10:14 +0000 Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 6B.6F.00712.8D54FB55; Mon, 3 Aug 2015 12:43:36 +0200 (CEST) Received: from [142.133.110.144] (147.117.188.8) by smtp-am.internal.ericsson.com (147.117.188.89) with Microsoft SMTP Server id 14.3.210.2; Mon, 3 Aug 2015 14:10:11 -0400 Message-ID: <55BFAE83.3000509@ericsson.com> Date: Mon, 03 Aug 2015 18:10:00 -0000 From: Simon Marchi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Pedro Alves , Subject: Re: [PATCH] Remove symlinks created in argv0-symlink.exp and general cleanup References: <1438287227-11303-1-git-send-email-simon.marchi@ericsson.com> <55BF7962.3060106@redhat.com> <55BF85BC.8040102@ericsson.com> <55BF9811.50202@redhat.com> In-Reply-To: <55BF9811.50202@redhat.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-08/txt/msg00043.txt.bz2 On 15-08-03 12:34 PM, Pedro Alves wrote: > Urgh. Maybe there's some other change to argv0-symlink.exp > that could be made to avoid this? I haven't looked at this > in enough detail to give a good informed suggestion, but > maybe putting the symlink elsewhere? When running tests in parallel, everything gets put in an output directory, with one directory per test, right? Could we do this all the time? > Personally, I'd vote for making in-tree builds, or at least testing, > officially unsupported. I think gcc already does so... I agree.