From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] linux install.tmpl: added CONFIG_HAVE_OBJTOOL in OR for objtool
Date: Thu, 17 Nov 2022 21:28:06 +0100 [thread overview]
Message-ID: <CAJGKYO6+bLB6u3cjuE66dgfizYOBNm6ttKgrZ0GUXi4xWMt0xw@mail.gmail.com> (raw)
In-Reply-To: <5d50a4da-6a2e-bcce-58bc-b86b40c5e0d2@ilbers.de>
On Thu, 17 Nov 2022 at 09:30, Anton Mikanovich <amikan@ilbers.de> wrote:
>
> 03.11.2022 18:55, roberto.foglietta@gmail.com wrote:
> > From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
> >
> > linux install.tmpl: added OR with CONFIG_HAVE_OBJTOOL for objtools
> > a fix for newer kernels (since 5.19 for sure) to include objtool
> >
> > The newer kernels (e.g. v5.19) when compiled and packaged by an ISAR
> > do not include the objectool anymore in linux headears package. This
> > obviously breaks any activity which expects to use that binary
> > executable.
> >
> > Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
>
> Applied to next, thanks.
>
Hi Anton,
I have integrated the isar next new HEAD into my project and tested
it against linux 5.10.150 (older) and 5.19.17 (newer) and both
linux-headers correctly includes objtool/objtool
$ for i in $(sudo find build -name linux-headers\*.deb); do dpkg -c $i
| grep -i objtool/objtool && echo $i; done
-rwxr-xr-x root/root 147464 2022-11-17 20:25
./usr/src/linux-headers-5.10.150/tools/objtool/objtool
build/tmp/work/debian-bullseye-amd64/linux-raidtest/5.19.17-r0/isar-apt/debian-bullseye-amd64/apt/debian-bullseye/pool/main/l/linux-raidtest/linux-headers-raidtest_5.10.150+r0_amd64.deb
-rwxr-xr-x root/root 180232 2022-11-17 20:58
./usr/src/linux-headers-5.19.17/tools/objtool/objtool
build/tmp/work/debian-bullseye-amd64/linux-raidtest/5.19.17-r0/linux-headers-raidtest_5.19.17+r0_amd64.deb
-rwxr-xr-x root/root 180232 2022-11-17 20:58
./usr/src/linux-headers-5.19.17/tools/objtool/objtool
build/tmp/deploy/isar-apt/debian-bullseye-amd64/apt/debian-bullseye/pool/main/l/linux-raidtest/linux-headers-raidtest_5.19.17+r0_amd64.deb
Best regards, R-
prev parent reply other threads:[~2022-11-17 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 15:55 roberto.foglietta
2022-11-07 8:02 ` Henning Schild
2022-11-07 9:46 ` Roberto A. Foglietta
2022-11-17 8:30 ` Anton Mikanovich
2022-11-17 20:28 ` Roberto A. Foglietta [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=CAJGKYO6+bLB6u3cjuE66dgfizYOBNm6ttKgrZ0GUXi4xWMt0xw@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.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