From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/ibm-sw-tpm2: enable only on supported architectures
Date: Tue, 21 Apr 2020 11:41:15 +0200 [thread overview]
Message-ID: <20200421114115.097bcfe6@windsurf.home> (raw)
In-Reply-To: <20200421092647.2452590-1-fontaine.fabrice@gmail.com>
On Tue, 21 Apr 2020 11:26:47 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fixes:
> - http://autobuild.buildroot.org/results/12d2c27c38cc52248d3277995a9bb5eae4b8bb9e
> - http://autobuild.buildroot.org/results/34151bded9737f7c128b7a2d763c9e0af8018068
> - http://autobuild.buildroot.org/results/9abbbdd2735991277c0b821a47c579b053335caf
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
I was also looking at this issue, and I believe it might be easier to
really fix the problem.
Indeed, it's just:
#ifndef RADIX_BITS
# if defined(__x86_64__) || defined(__x86_64) \
|| defined(__amd64__) || defined(__amd64) || defined(_WIN64) || defined(_M_X64) \
|| defined(_M_ARM64) || defined(__aarch64__) \
|| defined(__powerpc64__) || defined(__ppc64__)
# define RADIX_BITS 64
# elif defined(__i386__) || defined(__i386) || defined(i386) \
|| defined(_WIN32) || defined(_M_IX86) \
|| defined(_M_ARM) || defined(__arm__) || defined(__thumb__)
# define RADIX_BITS 32
# else
# error Unable to determine RADIX_BITS from compiler environment
# endif
#endif // RADIX_BITS
that causes problems.
And this crap can most likely be replaced by:
#define RADIX_BITS __WORDSIZE
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-21 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 9:26 [Buildroot] [PATCH 1/1] package/ibm-sw-tpm2: enable only on supported architectures Fabrice Fontaine
2020-04-21 9:41 ` Thomas Petazzoni [this message]
2020-04-21 9:57 ` Fabrice Fontaine
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=20200421114115.097bcfe6@windsurf.home \
--to=thomas.petazzoni@bootlin.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 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.