Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openssl: fix build on riscv32
Date: Wed, 03 Mar 2021 08:12:15 +0100	[thread overview]
Message-ID: <878s74lnhs.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210302215147.1556308-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Tue, 2 Mar 2021 22:51:47 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > riscv32 is (surprise!) a 32-bit architecture. But it has been 2038-safe
 > from its inception. As such, there is no legacy binaries that may use
 > the 32-bit time syscalls, and thus they are anot available on riscv32.

 > Code tht directly calls to the syscalls without using the C libraries
 > wrappers thus need to handle this case by themselves.

 > Backport a patch from the upstream development branch that will
 > eventually be openssl 3.0, but has not yet been backported to the 1.1.1
 > stable branch.

 > Fixes:
 >     http://autobuild.buildroot.org/results/eb9/eb9a64d4ffae8569b5225083f282cf87ffa7c681/
 >     ...
 >     http://autobuild.buildroot.org/results/07e/07e413b24ba8adc9558c80267ce16dda339bf032/

 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
 > Cc: Matt Weber <matthew.weber@rockwellcollins.com>
 > Cc: Mark Corbin <mark@dibsco.co.uk>

Did you see Arndbs comment on the upstream commit?

https://github.com/openssl/openssl/commit/5b5e2985f355c8e99c196d9ce5d02c15bebadfbc

I cannot quite figure out if this causes issues for other archs?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2021-03-03  7:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 21:51 [Buildroot] [PATCH] package/openssl: fix build on riscv32 Yann E. MORIN
2021-03-02 22:58 ` Arnout Vandecappelle
2021-03-03  7:12 ` Peter Korsgaard [this message]
2021-03-03 10:34   ` Yann E. MORIN

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=878s74lnhs.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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