From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Steffen Persvold <spersvold@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/directfb: enable on riscv32 again
Date: Sat, 13 Jul 2024 23:10:28 +0200 [thread overview]
Message-ID: <20240713231028.3ac24ecc@windsurf> (raw)
In-Reply-To: <20240627103457.28001-1-spersvold@gmail.com>
Hello Steffen,
On Thu, 27 Jun 2024 12:34:57 +0200
Steffen Persvold <spersvold@gmail.com> wrote:
> Newer 32bit architectures like RISCV32 and ARC are using 64bit time_t
> from the get go unlike other 32bit architectures, therefore aliasing
> __NR_futex to __NR_futex_time64 avoids the build error mentioned
> in cb6fd050.
>
> Fixes:
> - http://autobuild.buildroot.org/results/c0f4168575fa85af933539441eea95a3b10dac91
>
> Signed-off-by: Steffen Persvold <spersvold@gmail.com>
> ---
> ...-__NR_futex-on-32bit-architectures-u.patch | 40 +++++++++++++++++++
> package/directfb/Config.in | 2 -
> 2 files changed, 40 insertions(+), 2 deletions(-)
> create mode 100644 package/directfb/0007-libdirect-define-__NR_futex-on-32bit-architectures-u.patch
Thanks for your contribution, applied to our master branch!
How of curiosity, are you actually using DirectFB on RISC-V 32-bit
platforms?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-13 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 10:34 [Buildroot] [PATCH] package/directfb: enable on riscv32 again Steffen Persvold
2024-07-13 21:10 ` Thomas Petazzoni via buildroot [this message]
2024-08-12 13:03 ` Peter Korsgaard
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=20240713231028.3ac24ecc@windsurf \
--to=buildroot@buildroot.org \
--cc=spersvold@gmail.com \
--cc=thomas.petazzoni@bootlin.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