From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sourceware.org (Postfix) with ESMTPS id 0CAD9385842B for ; Sat, 16 Apr 2022 19:47:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0CAD9385842B X-IronPort-AV: E=Sophos;i="5.90,266,1643670000"; d="scan'208";a="11718041" Received: from 85-171-189-19.rev.numericable.fr (HELO hippo) ([85.171.189.19]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Apr 2022 21:47:32 +0200 Date: Sat, 16 Apr 2022 21:47:27 +0200 (CEST) From: Marc Glisse Reply-To: gcc-help@gcc.gnu.org To: Jonathan Wakely cc: "Matthew R. Wilson" , gcc-help Subject: Re: Error when building gcc w/ Go language on Solaris In-Reply-To: Message-ID: <55a8308e-4538-3492-2cc-d54a9bd578bc@hippo.saclay.inria.fr> References: <20220416053920.4hj6vcnqqlscile7@mattwilson.org> <20220416192445.dxuftlrblkhctmir@mattwilson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2022 19:47:34 -0000 On Sat, 16 Apr 2022, Jonathan Wakely via Gcc-help wrote: >>> Just a guess, but maybe the Go build uses sed or another command like >>> that, and relies on the POSIX-conforming version in /usr/xpg4/bin >>> rather than the /usr/bin one. Try putting /usr/xpg4/bin in your path, >>> just after /opt/mrwgcc/bin >> >> Aha! What a great guess -- that fixed it! Thank you so much! > > Great! We should document this, if we don't already. And even better would > be if the build failed with a clear error mentioning the need for POSIX sed > (or whichever command it was). https://gcc.gnu.org/install/specific.html#x-x-solaris2 says "The build process works more smoothly with the legacy Solaris tools so, if you have /usr/xpg4/bin in your PATH, we recommend that you place /usr/bin before /usr/xpg4/bin for the duration of the build." So we actually document the opposite... -- Marc Glisse