From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Add -nostdinc to TARGET_CFLAGS
Date: Thu, 29 Oct 2009 11:46:11 +0100 [thread overview]
Message-ID: <4AE97273.1020405@gmail.com> (raw)
In-Reply-To: <20091029103618.GA10006@thorin>
Robert Millan wrote:
> On Thu, Oct 29, 2009 at 11:14:33AM +0100, Robert Millan wrote:
>
>> It appears that -nostdinc also excludes GCC internal header directory (for
>> e.g. stdarg.h), which I didn't expect.
>>
>> Does someone know a clean way to resolve this? A quick check at GCC
>> command-line options didn't reveal a way to explicitly include that
>> directory afterwards without knowing its path.
>>
>> I.e. something similar to `gcc -print-file-name=libgcc.a`
>>
>
> Maybe with -isysroot=`pwd`/dummy instead of -nostdinc.
>
>
Why not to create a real sysdir? For gcc grub is just another OS
environment so we can use same approach as if we were cross-compiling
for another OS
> It's an ugly kludge, but the alternatives look even worse.
>
> Does someone have a better idea?
>
>
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
next prev parent reply other threads:[~2009-10-29 10:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 16:16 [PATCH] Add -nostdinc to TARGET_CFLAGS Robert Millan
2009-10-28 23:16 ` Robert Millan
2009-10-29 10:14 ` Robert Millan
2009-10-29 10:36 ` Robert Millan
2009-10-29 10:46 ` Vladimir 'phcoder' Serbinenko [this message]
2009-10-30 18:55 ` Robert Millan
2009-11-04 10:48 ` Felix Zielcke
2009-11-14 21:16 ` Felix Zielcke
2009-11-15 11:04 ` Robert Millan
2009-11-15 11:12 ` Robert Millan
2009-11-15 11:19 ` Felix Zielcke
2009-11-15 11:17 ` Felix Zielcke
2009-11-15 11:35 ` Robert Millan
2009-11-15 11:50 ` Felix Zielcke
2009-11-15 12:32 ` Robert Millan
2009-11-15 12:42 ` Felix Zielcke
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=4AE97273.1020405@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.