From patchwork Thu Nov 30 13:41:07 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Xi Ruoyao X-Patchwork-Id: 81031 Return-Path: X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 458F43857835 for ; Thu, 30 Nov 2023 13:42:38 +0000 (GMT) X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from xry111.site (xry111.site [89.208.246.23]) by sourceware.org (Postfix) with ESMTPS id 9EDC93858C66 for ; Thu, 30 Nov 2023 13:42:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9EDC93858C66 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 9EDC93858C66 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=1701351743; cv=none; b=nUBFF2RCRcVz41NrGyfexDOZkRcLw0Tzy+C8ja9fHa2FT1N/TJd77D5dLzoynN0UbvZuqb4E8OogRZojVzXDb6DoMbIeXmDnvyppV4NVW/LgICGvTFjzHftznHE3yW0U6VK2zrtnwho8trtTfWp/k4wBUF+PdQr2ip+gsPd1OKo= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701351743; c=relaxed/simple; bh=YntUj49gnBDF05auk5RRuEjJgKUMAshbdAB2OV/t6e0=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=NkLvGpLQ7+RQXR9XskMivamXoin0PrbOgCfP4ZP32rC8p7dKKqKQ2opACAkhq0JTuPWtVp+beXzOIHYeALobu60dwBCrMvbDn6Ko7Ua1gFsZxhF0KTU+D2nceolJq7ZzYUfFktrlkABA3AAdJ3XuwUlDB2SFk4WTFXsRU5tHpzk= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xry111.site; s=default; t=1701351739; bh=YntUj49gnBDF05auk5RRuEjJgKUMAshbdAB2OV/t6e0=; h=From:To:Cc:Subject:Date:From; b=cdn1ifP5A66E1qK1gr4InBkqBGBA7JVL15YBPIuLWBS4kwqCSq5P98oqL0qR1NXYg FB3/XxflMtLXw9/68yWxsuPPSde5F2H2ngebvH34vKNpKeYLiYGdVEwVyRuUTq0H/E 3+eCewG3dXKmzPpXT/sPPqJGjLBlH4RxCEN0/Rz0= Received: from stargazer.. (unknown [113.200.174.122]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 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 A12ED66A1E; Thu, 30 Nov 2023 08:42:18 -0500 (EST) From: Xi Ruoyao To: gcc-patches@gcc.gnu.org Cc: Richard Biener , Xi Ruoyao Subject: [PATCH v2] doc: Update the status of build directory not fully separated Date: Thu, 30 Nov 2023 21:41:07 +0800 Message-ID: <20231130134205.12445-1-xry111@xry111.site> X-Mailer: git-send-email 2.43.0 MIME-Version: 1.0 X-Spam-Status: No, score=-9.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, KAM_SHORT, LIKELY_SPAM_FROM, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org Recently there are some people building GCC with srcdir == objdir and the attempts just failed [1]. So stop to say "it should work". OTOH objdir as a subdirectory of srcdir works: we've built GCC in LFS [2] and BLFS [3] this way for decades and this is confirmed during the review of a previous version of this patch [4]. [1]: https://gcc.gnu.org/pipermail/gcc-help/2023-November/143068.html [2]: https://www.linuxfromscratch.org/lfs/view/12.0/chapter08/gcc.html [3]: https://www.linuxfromscratch.org/blfs/view/12.0/general/gcc.html [4]: https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638760.html gcc/ChangeLog: * doc/install.texi: Deem srcdir == objdir broken, but objdir as a subdirectory of srcdir fine. --- Superseds https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638728.html. Ok for trunk? gcc/doc/install.texi | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index c1ccb8ba02d..c1128d9274c 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -697,9 +697,8 @@ phases. First, we @strong{highly} recommend that GCC be built into a separate directory from the sources which does @strong{not} reside within the source tree. This is how we generally build GCC; building -where @var{srcdir} == @var{objdir} should still work, but doesn't -get extensive testing; building where @var{objdir} is a subdirectory -of @var{srcdir} is unsupported. +where @var{objdir} is a subdirectory of @var{srcdir} should work as well; +building where @var{objdir} == @var{srcdir} is unsupported. If you have previously built GCC in the same directory for a different target machine, do @samp{make distclean} to delete all files