From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mengyan1223.wang (mengyan1223.wang [89.208.246.23]) by sourceware.org (Postfix) with ESMTPS id 3C8033858C83 for ; Sun, 27 Mar 2022 09:37:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3C8033858C83 Received: from [IPv6:240e:358:114d:ff00:dc73:854d:832e:3] (unknown [IPv6:240e:358:114d:ff00:dc73:854d:832e:3]) (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@mengyan1223.wang) by mengyan1223.wang (Postfix) with ESMTPSA id ABC24660F4; Sun, 27 Mar 2022 05:37:12 -0400 (EDT) Message-ID: Subject: Re: architecture dependent directory of C header From: Xi Ruoyao To: Da Shi Cao , "gcc-help@gcc.gnu.org" Date: Sun, 27 Mar 2022 17:37:03 +0800 In-Reply-To: References: <186f56a70b2179d945d7bb61ad2e3e6c37e7e3be.camel@mengyan1223.wang> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.0 MIME-Version: 1.0 X-Spam-Status: No, score=-3031.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no 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: Sun, 27 Mar 2022 09:37:19 -0000 On Sat, 2022-03-26 at 23:53 +0000, Da Shi Cao wrote: > Hi Ruoyao, > Thanks a lot. I=E2=80=99ll have a try of it. > But this arch dependent including directory is in the default search > path of the compiler =C2=A0if aarch64 cross gcc is built on x86_64 withou= t > the option =E2=80=9C--enable-multiarch=E2=80=9D. Do you mean "$PREFIX/aarch64-linux-gnu/include" or "$PREFIX/include/aarch64-linux-gnu"? The previous one is a standard location for a cross compiler. The latter is not enabled without --enable-multiarch, at least for the upstream GCC code. Note that if you get a GCC source tarball elsewhere, it's unlikely you may get an answer here because we have no way to know how the source code is modified. --=20 Xi Ruoyao School of Aerospace Science and Technology, Xidian University