On Mon, Aug 06, 2018 at 09:58:50PM +0200, Marcin Juszkiewicz wrote:
W dniu 05.08.2018 o 16:36, Jeff Johnson pisze:
> So you are recommending using 14 lines (with comments) of spec file
> goop that uses 2 %ifarch build section tests in order to set/unset a
> macro.
>
> There's further baggage in spec files needed to add a BR, pass an
> option to configure, add libraries to link, etc
Spec files are often wrote in 'I do not know other archs than x86' way.
I remember going through valgrind support for aarch64 few years ago
where changes to upstream valgrind were simple but all those packages
where %{valgrind_archs} was done in "%ifarch x86_64 i686" way required
patching and then patching...
From what I remember there is no architecture supported by Fedora
without Valgrind support. We got rid of s390 (32bit) and risc-v does not
count yet.
As you say, for riscv64 we will want to disable valgrind initially,
but eventually hope to get it enabled.
I don't have the link handy but I talked with upstream a while back
and they (quite rightly) wish to wait and see how popular RISC-V
becomes before thinking about supporting it.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html