From: Da Shi Cao <dscao999@hotmail.com>
To: Xi Ruoyao <xry111@mengyan1223.wang>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: architecture dependent directory of C header
Date: Sat, 26 Mar 2022 23:53:09 +0000 [thread overview]
Message-ID: <SN4PR22MB32221A781FC4942405C2D4D58C1B9@SN4PR22MB3222.namprd22.prod.outlook.com> (raw)
In-Reply-To: <186f56a70b2179d945d7bb61ad2e3e6c37e7e3be.camel@mengyan1223.wang>
Hi Ruoyao,
Thanks a lot. I’ll have a try of it.
But this arch dependent including directory is in the default search path of the compiler if aarch64 cross gcc is built on x86_64 without the option “--enable-multiarch”. It is missing when arm cross gcc is built.
Dashi Cao
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
From: Xi Ruoyao<mailto:xry111@mengyan1223.wang>
Sent: Saturday, March 26, 2022 22:50
To: Da Shi Cao<mailto:dscao999@hotmail.com>; gcc-help@gcc.gnu.org<mailto:gcc-help@gcc.gnu.org>
Subject: Re: architecture dependent directory of C header
On Sat, 2022-03-26 at 12:37 +0000, Da Shi Cao via Gcc-help wrote:
> When compiling a C source using gcc, the following list of directories
> to search for included header files could be displayed:
> /usr/lib/gcc/x86_64-linux-gnu/8/include
> /usr/local/include
> /usr/lib/gcc/x86_64-linux-gnu/8/include-fixed
> /usr/include/x86_64-linux-gnu <--- arch dependent?
> /usr/include
>
> I'd like to know how this arch dependent directory
> (/usr/include/x86_64-linux-gnu) be incorporated into the gcc if a gcc
> compiler is to be built?
Configure GCC with --enable-multiarch.
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-03-26 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 12:37 Da Shi Cao
2022-03-26 14:50 ` Xi Ruoyao
2022-03-26 23:53 ` Da Shi Cao [this message]
2022-03-27 9:37 ` Xi Ruoyao
2022-03-27 15:14 ` Da Shi Cao
2022-03-28 10:29 ` Xi Ruoyao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SN4PR22MB32221A781FC4942405C2D4D58C1B9@SN4PR22MB3222.namprd22.prod.outlook.com \
--to=dscao999@hotmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=xry111@mengyan1223.wang \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).