From: Andrew Haley <aph@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [patch] include the %I spec when building the object file for the main function
Date: Tue, 21 May 2013 13:12:00 -0000 [thread overview]
Message-ID: <519B72D3.7030608@redhat.com> (raw)
In-Reply-To: <519B5144.2010303@ubuntu.com>
On 05/21/2013 11:49 AM, Matthias Klose wrote:
> Am 21.05.2013 10:26, schrieb Andrew Haley:
>> On 05/21/2013 08:23 AM, Matthias Klose wrote:
>>> The inclusion of stdc-predef.h is new in 4.8, the bits/predefs.h is not found in
>>> my case, because this header is on an include path, which is only added when cc1
>>> is passed the -imultiarch <tuple> option. The solution for me is to add the %I
>>> spec, when calling cc1 to build the main function.
>>>
>>> Ok for the trunk, and for 4.8 after the 4.8.1 release?
>>
>> This is slighty baffling. GCC is auto-including stdc-predef.h, but the
>> path info isn't sufficient?
>
> "because this header is on an include path, which is only added when cc1 is
> passed the -imultiarch <tuple> option."
>
> sorry, but I don't know what to add else here to explai the issue.
>
>> And why does this affect gcj?
>
> "when calling cc1 to build the main function". So it does have it's own
> invocation of cc1, and doesn't use any specs how to call cc1, which is used for
> other C files.
Yes, but what I didn't understand was "why has this changed now?"
Andrew.
prev parent reply other threads:[~2013-05-21 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 7:23 Matthias Klose
2013-05-21 8:26 ` Andrew Haley
2013-05-21 10:50 ` Matthias Klose
2013-05-21 13:12 ` Andrew Haley [this message]
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=519B72D3.7030608@redhat.com \
--to=aph@redhat.com \
--cc=doko@ubuntu.com \
--cc=java-patches@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).