From: "Andrei Gherzan" <andrei@gherzan.com>
To: "Khem Raj" <raj.khem@gmail.com>
Cc: openembedded <openembedded-core@lists.openembedded.org>,
"Andrei Gherzan" <andrei.gherzan@huawei.com>,
"Bernhard Rosenkränzer" <bernhard.rosenkraenzer.ext@huawei.com>
Subject: Re: [OE-core] [PATCH] gcc: Fix tm.h plugin header
Date: Thu, 09 Dec 2021 18:39:54 +0000 [thread overview]
Message-ID: <09f8ff3a-829d-41e4-95c1-fd203eaba643@www.fastmail.com> (raw)
In-Reply-To: <CAMKF1srj=FoX1Omr-57j35T6gGgU5JcGTdJMdghVjFy45K73-A@mail.gmail.com>
On Thu, 9 Dec 2021, at 16:40, Khem Raj wrote:
> On Thu, Dec 9, 2021 at 7:40 AM Andrei Gherzan <andrei@gherzan.com> wrote:
>>
>> From: Andrei Gherzan <andrei.gherzan@huawei.com>
>>
>> On x86-64, tm.h (needed to build gcc plugins) tries to include
>> config/i386/linux64.h, which isn't installed. Fortunately it also isn't
>> used, so simply removing the include statement is an ok fix.
>>
>
> is it due to multilib support ? if so we might be ok since we may not
> be using it
> but really it will be good to check it with multilib builds of x86_64/x86
I don't think it is related to multilib but I'll give multilib a try. In my case, the issue was revealed when compiling a kernel plugin config. I can't remember right now which one but I can replicate it for logs.
--
Andrei
next prev parent reply other threads:[~2021-12-09 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 15:40 [PATCH] gcc: Fix tm.h plugin header Andrei Gherzan
2021-12-09 16:40 ` [OE-core] " Khem Raj
2021-12-09 18:39 ` Andrei Gherzan [this message]
2021-12-20 1:39 ` Bernhard Rosenkränzer
2021-12-21 11:56 ` [OE-core] " Andrei Gherzan
2021-12-21 12:04 ` Richard Purdie
2021-12-23 12:28 ` Andrei Gherzan
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=09f8ff3a-829d-41e4-95c1-fd203eaba643@www.fastmail.com \
--to=andrei@gherzan.com \
--cc=andrei.gherzan@huawei.com \
--cc=bernhard.rosenkraenzer.ext@huawei.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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