From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out30-131.freemail.mail.aliyun.com (out30-131.freemail.mail.aliyun.com [115.124.30.131]) by sourceware.org (Postfix) with ESMTPS id 521793858D28 for ; Wed, 25 Jan 2023 09:41:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 521793858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=linux.alibaba.com X-Alimail-AntiSpam:AC=PASS;BC=-1|-1;BR=01201311R101e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=ay29a033018046049;MF=cooper.qu@linux.alibaba.com;NM=1;PH=DS;RN=2;SR=0;TI=SMTPD_---0Va9dIsg_1674639706; Received: from localhost(mailfrom:cooper.qu@linux.alibaba.com fp:SMTPD_---0Va9dIsg_1674639706) by smtp.aliyun-inc.com; Wed, 25 Jan 2023 17:41:47 +0800 Date: Wed, 25 Jan 2023 17:41:45 +0800 From: Cooper Qu To: Joseph Myers Cc: gcc-patches@gcc.gnu.org Subject: Re: [committed] C-SKY: Define SYSROOT_SUFFIX_SPEC. Message-ID: References: <20230113124319.75544-1-cooper.qu@linux.alibaba.com> <22262a2-6de-923b-c4d7-5e1a855934a1@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <22262a2-6de-923b-c4d7-5e1a855934a1@codesourcery.com> X-Spam-Status: No, score=-14.6 required=5.0 tests=BAYES_00,ENV_AND_HDR_SPF_MATCH,KAM_DMARC_STATUS,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,TXREP,UNPARSEABLE_RELAY,USER_IN_DEF_SPF_WL autolearn=ham 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 Fri, Jan 20, 2023 at 05:27:26PM +0000, Joseph Myers wrote: > I think this caused the build failures with build-many-glibcs.py shown by > my bot. SYSROOT_SUFFIX_SPEC should not be defined for a > --disable-multilib build; in such a build you can expect a single sysroot > without a suffix involved. Thus, you should put the SYSROOT_SUFFIX_SPEC > definition in a separate header only used if test "x${enable_multilib}" = > xyes (as in the config.gcc code removed in the older patch you refer to > above), or something similar. > Hi Joseph, Sorry, this is indeed caused by this patch. I tested the multilib scenario, but I didn't test the non-multilib, so I didn't find this problem in time. Now I have fixed this problem, the patch can be seen in https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610534.html Hope it also works for you, If you still have problems, please contact me. Thanks, Cooper