From: "Fujitani, Kenji/藤谷 賢治" <kenji_fujitani@jtekt.co.jp>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Compare with GreenHills Compiler
Date: Tue, 7 Dec 2021 02:23:46 +0000 [thread overview]
Message-ID: <TYAPR01MB4462174B1615F9A2FDFEF3D4B66E9@TYAPR01MB4462.jpnprd01.prod.outlook.com> (raw)
Dears,
I’m working under Ubuntu-PC(18.04LTS), and using gcc(version 7.5.0).
Recentry, I was trying to compile developed C-Code which worked on Green Hills Compiler(GHS) by above environment,
But this Code’s referenced HeaderFile exists on too complexed branching directory.
Even if I use "-I" option, it couldn’t search any header-files.
I heard it caused of pragma, but I can't understand in detail.
Why does It able to compile one by GHS, but it could’t by gcc?
If it has any solution, please show me how to do it.
Kind Regards,
Ken
JTEKT prepared a Global Privacy Policy for EU residents.
Please visit the website. https://www.jtekt.co.jp/e/privacy3.html
next reply other threads:[~2021-12-07 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 2:23 Fujitani, Kenji/藤谷 賢治 [this message]
2021-12-07 7:21 ` Jonathan Wakely
2021-12-07 10:02 ` David Brown
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=TYAPR01MB4462174B1615F9A2FDFEF3D4B66E9@TYAPR01MB4462.jpnprd01.prod.outlook.com \
--to=kenji_fujitani@jtekt.co.jp \
--cc=gcc-help@gcc.gnu.org \
/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).