Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [2018.02] check-bin-arch fails for PowerPC 32-bit userland, 64-bit kernel
Date: Tue, 20 Feb 2018 09:56:38 +0100	[thread overview]
Message-ID: <20180220085638.GB11289@australia> (raw)

Hi,

I have a defconfig with a multilib toolchain for PowerPC e6500 which is a 64-bit
architecture. The toolchain builds 32-bit by default, which is used for
userland. The kernel forces 64-bit anyway.
BR2_ARCH is set to "powerpc".

With the introduction of check-bin-arch, I now see failures after the kernel
compilation:
    ERROR: architecture for "/lib/modules/3.12.37-rt51/kernel/lib/libcrc32c.ko" is "PowerPC64", should be "PowerPC"
and same for other modules.
For actual userland binaries, readelf does show PowerPC as expected.

According to me, the situation is normal and check-bin-arch should accept it.
However, how to deal with it?

We could add a second variable BR2_READELF_ARCH_NAME_KERNEL.
Its value would be the same as the existing BR2_READELF_ARCH_NAME in case we are
dealing with a 32-bit arch, but the 64-bit equivalent in case of a 64-bit arch.
However, we don't currently mark all 64-bit powerpc architectures as such, so
we'd need some more knowledge about them (or could add them case by case as
required).
In the check-bin-arch script, or its caller, we then need to special case the
linux package.

Alternatively, the new variable could be user-facing and be set by the user in
the defconfig.

Other thoughts? Feedback?

Thanks,
Thomas

             reply	other threads:[~2018-02-20  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20  8:56 Thomas De Schampheleire [this message]
2018-02-20  9:05 ` [Buildroot] [2018.02] check-bin-arch fails for PowerPC 32-bit userland, 64-bit kernel Thomas Petazzoni
2018-02-20  9:41   ` Thomas De Schampheleire
2018-02-20  9:57     ` Thomas Petazzoni

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=20180220085638.GB11289@australia \
    --to=thomas.de_schampheleire@nokia.com \
    --cc=buildroot@busybox.net \
    /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