From: "'cedric.hombourger@siemens.com' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Koch, Stefan" <stefan-koch@siemens.com>
Cc: "Storm, Christian" <christian.storm@siemens.com>,
"Adler, Michael" <michael.adler@siemens.com>,
"amikan@ilbers.de" <amikan@ilbers.de>,
"Sudler, Simon" <simon.sudler@siemens.com>,
"ubely@ilbers.de" <ubely@ilbers.de>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/2] linux-custom: Fix arch dependent deploy dirs for linux-libc-dev packages
Date: Fri, 5 Jul 2024 13:12:10 +0000 [thread overview]
Message-ID: <ef9acb15c0d7087e8b246d2906a63d500d7c2398.camel@siemens.com> (raw)
In-Reply-To: <20240704130725.3050993-1-stefan-koch@siemens.com>
On Thu, 2024-07-04 at 15:07 +0200, Stefan Koch wrote:
> - Solved by avoiding setting of not necessary variables
> - Wrong architecture was used within /usr/include/ARCH/asm directory
> - Solves issue: https://github.com/ilbers/isar/issues/105
>
> Signed-off-by: Stefan Koch <stefan-koch@siemens.com>
Tested-by: Cedric Hombourger <cedric.hombourger@siemens.com>
(confirmed the issue without the patch and that it is correctly
resolved with that change applied). Thanks!
> ---
> meta/recipes-kernel/linux/files/debian/isar/common.tmpl | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/files/debian/isar/common.tmpl
> b/meta/recipes-kernel/linux/files/debian/isar/common.tmpl
> index 86af70c5..def8480e 100644
> --- a/meta/recipes-kernel/linux/files/debian/isar/common.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/isar/common.tmpl
> @@ -18,8 +18,7 @@
> KERNEL_PKG_KERN_KBUILD_CROSS=${KERNEL_PKG_KERN_KBUILD}-
> ${DISTRO_ARCH}-cross
> # The scripts and tools are always created for host arch
> if echo "${DEB_BUILD_PROFILES}" | grep -q -e "cross" -e "kbuild"
> then
> - eval $(dpkg-architecture -f -A ${DISTRO_ARCH})
> - CROSS_COMPILE=${DEB_TARGET_GNU_TYPE}-
> + CROSS_COMPILE=$(dpkg-architecture -f -A ${DISTRO_ARCH} -q
> DEB_TARGET_GNU_TYPE)-
> fi
>
> # Constants
--
Cedric Hombourger
Siemens AG
www.siemens.com
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/ef9acb15c0d7087e8b246d2906a63d500d7c2398.camel%40siemens.com.
next prev parent reply other threads:[~2024-07-05 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 13:07 'Stefan Koch' via isar-users
2024-07-04 13:07 ` [PATCH 2/2] linux-custom: Do not create empty linux-libc-dev-cross package for linux-native 'Stefan Koch' via isar-users
2024-07-05 13:12 ` 'cedric.hombourger@siemens.com' via isar-users [this message]
2024-07-12 6:02 ` [PATCH 1/2] linux-custom: Fix arch dependent deploy dirs for linux-libc-dev packages Uladzimir Bely
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=ef9acb15c0d7087e8b246d2906a63d500d7c2398.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=christian.storm@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=michael.adler@siemens.com \
--cc=simon.sudler@siemens.com \
--cc=stefan-koch@siemens.com \
--cc=ubely@ilbers.de \
/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