[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1022175: tup: FTBFS on riscv64



On Fri, 2022-10-21 at 12:46 +0000, JunYuan Tan wrote:

> There is a merged upstream patch [1] that fixes this issue for riscv64.

I think this is the wrong approach, since it means that every new arch
that comes along needs to add a string for itself and the list of
strings grows longer and longer even though tup doesn't actually do
anything differently on arches except x86_64, other than pass along the
architecture string to the Tupfiles it runs.

If there is a standard define for the current architecture string
defined by GCC/clang, then the code should use that, so that the right
architecture string will be present by default on all distros.

If there is not, then debian/rules should pass $(DEB_HOST_GNU_TYPE) to
the CONFIG_TUP_ARCH field in the tup.config file in dh_auto_configure.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: