Re: Bug#995867 mipsel FTBFS (relocation truncated to fit: R_MIPS_CALL16)

To: 995867@bugs.debian.org, debian-mips@lists.debian.org
Subject: Re: Bug#995867 mipsel FTBFS (relocation truncated to fit: R_MIPS_CALL16)
From: Drew Parsons <dparsons@debian.org>
Date: Mon, 25 Oct 2021 21:11:07 +0200
Message-id: <[🔎] f5cfa826b2572f66875862c4a20a46ea@debian.org>
Reply-to: dparsons@debian.org

Hi mipsel porters,

I need help resolving Bug#995867 [1]. xtensor implacably FTBFS.

I thought it might have been related to memory constraints, sincextensor is a header-only library. But the problem is still present afterreducing the test file to only one "optional" tests (unless that's stilltoo big and need more radical reduction in object size).

Upstream has recently made a new release, but it doesn't seem to havemade such changes to the test file structure that would significantlyreduce the object size. Perhaps the problem is something different.


Drew

[1] For your convenience:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995867

Reply to:

Follow-Ups:
- Re: Bug#995867 mipsel FTBFS (relocation truncated to fit: R_MIPS_CALL16)
  - From: YunQiang Su <wzssyqa@gmail.com>

Prev by Date: Re: Bug#997011: llvm-toolchain-13: FTBFS on mipsel: undefined reference to lldb_private::process_linux::NativeRegisterContextLinux::CreateHostNativeRegisterContextLinux in lldb-server
Next by Date: Re: Bug#995867 mipsel FTBFS (relocation truncated to fit: R_MIPS_CALL16)
Previous by thread: Re: Bug#997011: llvm-toolchain-13: FTBFS on mipsel: undefined reference to lldb_private::process_linux::NativeRegisterContextLinux::CreateHostNativeRegisterContextLinux in lldb-server
Next by thread: Re: Bug#995867 mipsel FTBFS (relocation truncated to fit: R_MIPS_CALL16)
Index(es):
- Date
- Thread