Re: Strange armel build error

2024-08-18 Thread Alec Leamas
On 18/08/2024 11:35, Adam D. Barratt wrote: On Sun, 2024-08-18 at 14:23 +0500, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: [...]-- If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel pac

Re: Strange armel build error

2024-08-18 Thread Sebastiaan Couwenberg
On 8/18/24 11:23 AM, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the

Re: Strange armel build error

2024-08-18 Thread Alec Leamas
Hi list, On 18/08/2024 11:23, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: Hi Stephen, On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel

Re: Strange armel build error

2024-08-18 Thread Alec Leamas
Hi; On 18/08/2024 06:11, Wookey wrote: On 2024-08-17 17:58 +0200, Alec Leamas wrote: To make it more interesting, the simple -latomic fix doesn't seem to cut it That's a pity, it sounds plausible. I'll try to take a look. Thanks! That said, unless you have oceans of time, perhaps it might m

Re: Strange armel build error

2024-08-18 Thread Adam D. Barratt
On Sun, 2024-08-18 at 14:23 +0500, Andrey Rakhmatullin wrote: > On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: > > Hi Stephen, > > > > On 18/08/2024 09:04, Stephen Kitt wrote: > > [...] > > > If you can’t fix the build, you don’t need to exclude the > > > architecture — you > > > ca

Re: Strange armel build error

2024-08-18 Thread Andrey Rakhmatullin
On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: > Hi Stephen, > > On 18/08/2024 09:04, Stephen Kitt wrote: > > On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas > > wrote: > > > Or just exclude that architecture i. e., list all archs but armel? > > If you can’t fix the build, you don’

Re: Strange armel build error

2024-08-18 Thread Alec Leamas
Hi Stephen, On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package

Re: Strange armel build error

2024-08-18 Thread Stephen Kitt
On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: > Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package in testing. That will allow the package to migrate even

Re: Strange armel build error

2024-08-17 Thread Wookey
On 2024-08-17 17:58 +0200, Alec Leamas wrote: > > > Fair enough. But TBH, i just cannot wait "a couple of weeks" for a possible > reply; there are users waiting for the backports as I write. Fair enough. If you can't wait then you can't wait. > To make it more interesting, the simple -latomic

Re: Strange armel build error

2024-08-17 Thread Alec Leamas
On 17/08/2024 14:42, Wookey wrote: On 2024-08-16 17:46 +0200, Alec Leamas wrote: From another perspective: what is the right thing to do in a situation like this? Trying to hunt down the problem, and thus causing all sorts of noise like this message? This is what the policy says, but still

Re: Strange armel build error

2024-08-17 Thread Wookey
On 2024-08-16 17:46 +0200, Alec Leamas wrote: > > From another perspective: what is the right thing to do in a situation like > this? Trying to hunt down the problem, and thus causing all sorts of noise > like this message? This is what the policy says, but still... > > Or just exclude that arc

Re: Strange armel build error

2024-08-16 Thread Alec Leamas
Hi Timo and Paul, On 16/08/2024 18:10, Timo Röhling wrote: Hi Alec, * Alec Leamas [2024-08-16 17:46]: /usr/include/c++/14/bits/atomic_futex.h:278:(.text+0x16dc): undefined reference to `std::__atomic_futex_unsigned_base::_M_futex_notify_all(unsigned int*)' /usr/bin/ld: /usr/include/c++/14/b

Re: Strange armel build error

2024-08-16 Thread Timo Röhling
Hi Alec, * Alec Leamas [2024-08-16 17:46]: /usr/include/c++/14/bits/atomic_futex.h:278:(.text+0x16dc): undefined reference to `std::__atomic_futex_unsigned_base::_M_futex_notify_all(unsigned int*)' /usr/bin/ld: /usr/include/c++/14/bits/atomic_futex.h:278:(.text+0x29d8): undefined reference to

Re: Strange armel build error

2024-08-16 Thread Paul Gevers
Hi, On 16-08-2024 17:46, Alec Leamas wrote: All other builds are OK. Has anyone a hint about what might be going on here? https://release.debian.org/testing/arch_qualify.html armel column. Paul OpenPGP_signature.asc Description: OpenPGP digital signature