From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by sourceware.org (Postfix) with ESMTP id 695CE3858D1E; Mon, 25 Dec 2023 23:01:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 695CE3858D1E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=kernel.crashing.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 695CE3858D1E Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=63.228.1.57 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703545297; cv=none; b=bx+HPicMK2foHZik8ueVxXcGL9CHmJ1gQ6hzHg0LmDQxP0VLcHNz1AngVegAgZK65YT72HZ5aSMxBwt62ChC1H7CqtyQl2+5tJBeShR0vEV9V1LkI4M9jqSBwZjKFjBcRxE4yWvi7bRr2BP1r64pI5PcyuUhEaIblKQZq+0Tp0M= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703545297; c=relaxed/simple; bh=zGDslOV09HZLhYW4cj1v4sSjvihFRo53ZjowJfAatEk=; h=Date:From:To:Subject:Message-ID:Mime-Version; b=aB8HVk6snsOEBG/zCjW7P56mIfDXTdh5YjPwSjzjXWiJwPV8CbzZV8BrxOLSnusCo/LT60UfFBwE2B2zVXs/Q4g6oQESI0QkM+9+z7id+AipkK9gU+MFwemi+PqryOTS7h0WumN8EDUjQ5kwrVqztCtHgZ/l9kGdhUcbWJdPSos= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 3BPN0YDP010473; Mon, 25 Dec 2023 17:00:34 -0600 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 3BPN0Yvt010472; Mon, 25 Dec 2023 17:00:34 -0600 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Mon, 25 Dec 2023 17:00:33 -0600 From: Segher Boessenkool To: Xi Ruoyao Cc: Prashant , gcc-help@gcc.gnu.org, gcc@gcc.gnu.org Subject: Re: 'posix_spawnp' error in build Message-ID: <20231225230033.GT19790@gate.crashing.org> References: <20231225162814.GS19790@gate.crashing.org> <22078885f012045083b9287a25dac5157e84ece6.camel@xry111.site> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <22078885f012045083b9287a25dac5157e84ece6.camel@xry111.site> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,KAM_SHORT,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 Tue, Dec 26, 2023 at 12:33:40AM +0800, Xi Ruoyao wrote: > On Mon, 2023-12-25 at 10:28 -0600, Segher Boessenkool wrote: > > > 1) git clone git://gcc.gnu.org/git/gcc.git > > > 2) cd gcc & ./contrib/download_prerequisites > > > 3) mkdir objdir & cd objdir > > > 4) ../gcc/configure --prefix=/home/path/to/gcc --enable-languages=c,c++ > > > > That is wrong.  Build dir as a subdir of the source dir is not > > supported.  It might work in many cases, but that does not mean it is > > okay to do. > > It *is* supported, per discussion at > https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638760.html. Huh, okay. That changed "recently" then, for some elongated timescale anyway :-) > But then you should use "../configure", not "../gcc/configure". Ha! I didn't even notice that. > Running > the configure script of a GCC component (instead of the top-level > configure) directly is completely unsupported. Without all the necessary configuration arguments, yeah. So it is still easier to just make an actually separate object dir -- even if only so you can just blow it away when you want to start over :-) Segher