From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from xry111.site (xry111.site [89.208.246.23]) by sourceware.org (Postfix) with ESMTPS id 8FC823858C42 for ; Mon, 4 Dec 2023 04:38:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8FC823858C42 Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=xry111.site Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=xry111.site ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8FC823858C42 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=89.208.246.23 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701664722; cv=none; b=n5T4/yD2uvFUHrJMlh36difYQOv4xYhn3mJ1hEcUYaRCZNe7u+XqybGXJhNYcnDvB3GMuA5876PTRNcR1+5Y9/7p0dPql4BVhrqfoVfNAphnRx5CW8XISHvSPPg6rulwunLJ5yNvLErpUmNu9A8E2aMJm+rpzIVmI4G02eJVy+Q= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701664722; c=relaxed/simple; bh=L21sMuzeAN5sByq4mgXEe5Wp6NHoGPD8iUPkJZHUqMc=; h=DKIM-Signature:Message-ID:Subject:From:To:Date:MIME-Version; b=cDxxgzR0VsebI9L0L715r/rWyfWmQcupy8Dm7dSU1/AG4rRzKR47F8u2lR/7DzdjPgwDzn2jPIDI89z24WpQoyj8o+e663XkeOtMjf6I9AkYuy+b5LZcyME/tJd/rnwWTqNFI2ieJpcYcxWbmOi+U3LzgYgYOfBdbHmp2Rja9AI= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xry111.site; s=default; t=1701664719; bh=L21sMuzeAN5sByq4mgXEe5Wp6NHoGPD8iUPkJZHUqMc=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=g+izUau+R4z3QKto3kneCI26tG1O2kcaB/wEHdCCY5WaOEUPTHJLBAUuW3zorjyEU FNASxTYnFIusfiAufvapJjbWKzp3Oq74LEgWGCXKnWLbjzRh4QyEeH7eA7veY1DPga YzBjvFjbbZv9stVp1yM98EpSKln2niMkofJXozN0= Received: from [127.0.0.1] (unknown [IPv6:2001:470:683e::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: xry111@xry111.site) by xry111.site (Postfix) with ESMTPSA id 6361E66BE3; Sun, 3 Dec 2023 23:38:38 -0500 (EST) Message-ID: Subject: Re: host-x86_64-pc-linux-gnu/gcc/xgcc: No such file or directory From: Xi Ruoyao To: Jonny Grant , Jonathan Wakely Cc: gcc-help Date: Mon, 04 Dec 2023 12:38:36 +0800 In-Reply-To: References: <9eed991c-7def-440a-bb3b-96ea4f26a19e@jguk.org> <8b1d2871-b1e1-4f6a-985a-a66d1b2fe40e@jguk.org> <26da4e26-5623-4427-98b5-93540271fa8f@jguk.org> Autocrypt: addr=xry111@xry111.site; prefer-encrypt=mutual; keydata=mDMEYnkdPhYJKwYBBAHaRw8BAQdAsY+HvJs3EVKpwIu2gN89cQT/pnrbQtlvd6Yfq7egugi0HlhpIFJ1b3lhbyA8eHJ5MTExQHhyeTExMS5zaXRlPoiTBBMWCgA7FiEEkdD1djAfkk197dzorKrSDhnnEOMFAmJ5HT4CGwMFCwkIBwICIgIGFQoJCAsCBBYCAwECHgcCF4AACgkQrKrSDhnnEOPHFgD8D9vUToTd1MF5bng9uPJq5y3DfpcxDp+LD3joA3U2TmwA/jZtN9xLH7CGDHeClKZK/ZYELotWfJsqRcthOIGjsdAPuDgEYnkdPhIKKwYBBAGXVQEFAQEHQG+HnNiPZseiBkzYBHwq/nN638o0NPwgYwH70wlKMZhRAwEIB4h4BBgWCgAgFiEEkdD1djAfkk197dzorKrSDhnnEOMFAmJ5HT4CGwwACgkQrKrSDhnnEOPjXgD/euD64cxwqDIqckUaisT3VCst11RcnO5iRHm6meNIwj0BALLmWplyi7beKrOlqKfuZtCLbiAPywGfCNg8LOTt4iMD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.50.2 MIME-Version: 1.0 X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,LIKELY_SPAM_FROM,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Mon, 2023-12-04 at 00:34 +0000, Jonny Grant wrote: > Is it this page? >=20 > https://gcc.gnu.org/install/configure.html >=20 > How about changing this line to clarify make just say building within the= src tree does not work, and is unsupported? >=20 > Change from: > "First, we highly recommend that GCC be built into a separate directory" >=20 > To: > "First, we only support building GCC from a separate directory" This paragraph has been updated to: First, we highly recommend that GCC be built into a separate directory from the sources which does not reside within the source tree. This is how we generally build GCC; building where objdir is a subdirectory of srcdir should work as well; building where objdir =3D=3D srcdir is unsupported. Richard told me using a new subdirectory in srcdir as objdir works fine and *is* supported (i. e. if it somehow stops to work we'll fix). But objdir =3D=3D srcdir has been broken for a long time and there is no intention to make it "work". The FAQ is a different page: https://gcc.gnu.org/wiki/FAQ#configure --=20 Xi Ruoyao School of Aerospace Science and Technology, Xidian University