From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libressl: fix mips64el build
Date: Thu, 25 Jul 2024 17:41:48 +0200 [thread overview]
Message-ID: <20240725174148.33be7bc7@windsurf> (raw)
In-Reply-To: <20240725113943.1761962-1-fontaine.fabrice@gmail.com>
On Thu, 25 Jul 2024 13:39:43 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Disable assembly with mips64el to avoid the following build failure
> raised since bump to version 3.8.2 in commit
> 21eca49ed5110872407b76ab9337d2877c4cda24:
>
> /home/autobuild/autobuild/instance-21/output-1/host/opt/ext-toolchain/bin/../lib/gcc/mips64el-buildroot-linux-gnu/13.2.0/../../../../mips64el-buildroot-linux-gnu/bin/ld: ../../crypto/libcrypto.so.52.0.0: undefined reference to `bn_mul_words'
>
> Fixes: 21eca49ed5110872407b76ab9337d2877c4cda24
> - http://autobuild.buildroot.org/results/09b86c95ea1054d5f54d4ef4a041eb105c3f4aa9
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Could you track down a bit more precisely what is going on, i.e which
upstream commit broke this? I don't immediately see something relevant.
6501696dd7669b3d20d69beffc508c46f0a807da was already in v3.7.3 that we
were using prior to the bump in
21eca49ed5110872407b76ab9337d2877c4cda24.
Do you have some evidence that only BR2_mips64el is impacted, and not
BR2_mips64 (i.e big endian MIPS64) ?
Thanks,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-25 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 11:39 [Buildroot] [PATCH 1/1] package/libressl: fix mips64el build Fabrice Fontaine
2024-07-25 15:41 ` Thomas Petazzoni via buildroot [this message]
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=20240725174148.33be7bc7@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@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 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.