All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrei Gherzan" <andrei@gherzan.com>
To: "Khem Raj" <raj.khem@gmail.com>
Cc: openembedded <openembedded-core@lists.openembedded.org>,
	"Bernhard Rosenkränzer" <bernhard.rosenkraenzer.ext@huawei.com>,
	"Andrei Gherzan" <andrei.gherzan@huawei.com>
Subject: Re: [OE-core] [PATCH] gcc: Fix compile of gcc plugins
Date: Thu, 06 Jan 2022 13:56:53 +0000	[thread overview]
Message-ID: <75e55dfd-3505-483b-8aaf-81249056d03e@www.fastmail.com> (raw)
In-Reply-To: <CAMKF1soJgvom8__9L3C3qXwWUh2owFQTCb=ZTQXZXuLfi2PjaQ@mail.gmail.com>

On Fri, 24 Dec 2021, at 05:50, Khem Raj wrote:
> On Thu, Dec 23, 2021 at 4:26 AM Andrei Gherzan <andrei@gherzan.com> wrote:
>>
>> From: Andrei Gherzan <andrei.gherzan@huawei.com>
>>
>> Without this, compiling gcc plugins will fail with an error similar to:
>> [...]
>> fatal error: ./config/i386/linux64.h: No such file or directory
>> [...]
>>
>> Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
>> ---
>>  meta/recipes-devtools/gcc/gcc-11.2.inc        |  1 +
>>  .../0001-Fix-install-path-of-linux64.h.patch  | 33 +++++++++++++++++++
>>  2 files changed, 34 insertions(+)
>>  create mode 100644 meta/recipes-devtools/gcc/gcc/0001-Fix-install-path-of-linux64.h.patch
>>
>> diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc b/meta/recipes-devtools/gcc/gcc-11.2.inc
>> index e352c958de..f07a5be507 100644
>> --- a/meta/recipes-devtools/gcc/gcc-11.2.inc
>> +++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
>> @@ -59,6 +59,7 @@ SRC_URI = "\
>>             file://0037-libatomic-Do-not-enforce-march-on-aarch64.patch \
>>             file://0041-apply-debug-prefix-maps-before-checksumming-DIEs.patch \
>>             file://0006-If-CXXFLAGS-contains-something-unsupported-by-the-bu.patch \
>> +           file://0001-Fix-install-path-of-linux64.h.patch \
>>             file://0001-CVE-2021-35465.patch \
>>             file://0002-CVE-2021-35465.patch \
>>             file://0003-CVE-2021-35465.patch \
>> diff --git a/meta/recipes-devtools/gcc/gcc/0001-Fix-install-path-of-linux64.h.patch b/meta/recipes-devtools/gcc/gcc/0001-Fix-install-path-of-linux64.h.patch
>> new file mode 100644
>> index 0000000000..55f78eaa0b
>> --- /dev/null
>> +++ b/meta/recipes-devtools/gcc/gcc/0001-Fix-install-path-of-linux64.h.patch
>> @@ -0,0 +1,33 @@
>> +From 58211c7ceb0510b2a11a7f1da3c7fa968c658749 Mon Sep 17 00:00:00 2001
>> +From: Andrei Gherzan <andrei.gherzan@huawei.com>
>> +Date: Wed, 22 Dec 2021 12:49:25 +0100
>> +Subject: [PATCH] Fix install path of linux64.h
>> +
>> +We add linux64.h to tm includes[1] as a relative path to B. This patch
>> +adapts the install path of linux64.h to match the include in tm.h.
>> +
>> +[1] 0016-Use-the-multilib-config-files-from-B-instead-of-usin.patch
>> +
>> +Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
>> +
>> +Upstream-Status: Inappropriate [configuration]
>> +---
>> + gcc/Makefile.in | 2 ++
>> + 1 file changed, 2 insertions(+)
>> +
>> +diff --git a/gcc/Makefile.in b/gcc/Makefile.in
>> +index 9b17d120a..d175ec4e3 100644
>> +--- a/gcc/Makefile.in
>> ++++ b/gcc/Makefile.in
>> +@@ -3693,6 +3693,8 @@ install-plugin: installdirs lang.install-plugin s-header-vars install-gengtype
>> +         "$(srcdir)"/config/* | "$(srcdir)"/common/config/* \
>> +         | "$(srcdir)"/c-family/* | "$(srcdir)"/*.def ) \
>> +           base=`echo "$$path" | sed -e "s|$$srcdirstrip/||"`;; \
>> ++        ./* ) \
>> ++          base=`dirname $$path`;;\
>
> this needs better explaining, and I have a hunch that it could be a
> broad brush too,

The initial fix was to "case it" on the specific header file but I reckon this will be useful for other ./* header that might be added in the future.

I'm going to explain it more in git log and also make it specific to the header.

Andrei


      reply	other threads:[~2022-01-06 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 12:25 [PATCH] gcc: Fix compile of gcc plugins Andrei Gherzan
2021-12-24  5:50 ` [OE-core] " Khem Raj
2022-01-06 13:56   ` Andrei Gherzan [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=75e55dfd-3505-483b-8aaf-81249056d03e@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 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.