From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Samuel Martin <s.martin49@gmail.com>,
linux-amarula@amarulasolutions.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/armadillo: bump to version 10.1.0
Date: Mon, 26 Aug 2024 18:57:41 +0200 [thread overview]
Message-ID: <20240826185741.7c68d235@windsurf> (raw)
In-Reply-To: <20240824151511.3178807-1-dario.binacchi@amarulasolutions.com>
Hello Dario,
On Sat, 24 Aug 2024 17:15:11 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> - C++11 is now the minimum required C++ standard
> - faster handling of compound expressions by trimatu() and trimatl()
> - faster sparse matrix addition, subtraction and element-wise multiplication
> - expanded sparse submatrix views to handle the non-contiguous form of X.cols(vector_of_column_indices)
> - expanded eigs_sym() and eigs_gen() with optional fine-grained parameters
>
> Fixes:
> - http://autobuild.buildroot.org/results/d4e9e7b453960a4f62a199344b30b729a4f235bc
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> package/armadillo/armadillo.hash | 2 +-
> package/armadillo/armadillo.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Same comment as for babeld: bumping to solve a download issue is not a
good solution. Indeed, if we have to bump because upstream dropped the
tarball, what tells us that they won't drop the new tarball again in
the future? This can only be resolved either by finding an alternate
upstream location or by talking with upstream so that they restore the
previous tarball and understand the issues caused by moving/removing
previous tarballs.
Also, if they made C++11 required, then I'm pretty sure we will need a
BR2_TOOLCHAIN_GCC_AT_LEAST_xyz dependency added, no?
Thanks!
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-08-26 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 15:15 [Buildroot] [PATCH 1/1] package/armadillo: bump to version 10.1.0 Dario Binacchi
2024-08-26 16:57 ` Thomas Petazzoni via buildroot [this message]
2024-08-27 6:11 ` Dario Binacchi
2024-08-27 6:20 ` Dario Binacchi
2024-08-30 16:47 ` Thomas Petazzoni via buildroot
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=20240826185741.7c68d235@windsurf \
--to=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=s.martin49@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.