Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-11-07 Thread Richard B. Kreckel
Hi Helmut, On 06.11.21 10:49, Helmut Grohne wrote: > I confirm. Mystery finally solved. The next upstream release shall close > this bug. So, that powerpc problem with computing long double epsilon was a false alarm, then? If you could confirm that, I'ld close this, spin a release, and be

Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-11-07 Thread Helmut Grohne
Control: tags -1 + fixed-upstream - patch On Sat, Nov 06, 2021 at 02:27:07AM +0100, Richard B. Kreckel wrote: > Yes, I can. There seems to be a misunderstanding. > > This hang creating intparam.h is the known issue you reported and that > should be fixed upstream. > > Sorry, the Debian package

Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-11-05 Thread Richard B. Kreckel
Hi Helmut, On 05.11.21 23:28, Helmut Grohne wrote: > I created a fresh unstable chroot containing only essential and then ran > the following commands inside: > > # dpkg --add-architecture ppc64el > # apt-get update > # apt-get install g++-powerpc64le-linux-gnu make file libgmp-dev:ppc64el > $

Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-11-05 Thread Helmut Grohne
Hi Richard, On Fri, Nov 05, 2021 at 11:00:17PM +0100, Richard B. Kreckel wrote: > So I uninstalled it. It still compiles and I can still run the tests. That makes things interesting. Let us pin down as much as we can to figure out the difference. I created a fresh unstable chroot containing

Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-11-05 Thread Richard B. Kreckel
Hi Helmut, On 05.11.21 15:41, Helmut Grohne wrote: > On Fri, Nov 05, 2021 at 10:32:59AM +0100, Richard B. Kreckel wrote: > I vaguely suspect that you do have qemu-user-binfmt installed and that > it enables running foreign binaries and changes the way configure > behaves. Does that match reality?

Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-11-05 Thread Helmut Grohne
Hi Richard, On Fri, Nov 05, 2021 at 10:32:59AM +0100, Richard B. Kreckel wrote: > How can I reproduce this? Thank you for looking into the issue. > On my bullseye setup, this works: > $ ./configure --host=powerpc64le-linux-gnu --disable-shared > $ make > $ qemu-ppc64le -L

Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-11-05 Thread Richard B. Kreckel
On 05.11.21 10:32, Richard B. Kreckel wrote: > On my bullseye setup, this works: > $ ./configure --host=powerpc64le-linux-gnu --disable-shared > $ make > $ qemu-ppc64le -L /usr/powerpc64le-linux-gnu ./tests/exam > Tests passed. It was on a bookworm/unstable setup, actually. (I don't see how that

Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-11-05 Thread Richard B. Kreckel
Hi Helmut, On 28.08.21 13:53, Helmut Grohne wrote: > The issue is with the detection of the long double epsilon on powerpc > architectures. m4/floatparam.m4' macro CL_FLOATPARAM_CROSS attempts to > deduce the minimal value that can be added to 1 using compile time > bisection. That works, because

Bug#971939: cln FTCBFS: missing #include for intptr_t

2021-08-28 Thread Helmut Grohne
Hi, On Mon, Oct 19, 2020 at 11:11:40AM +0200, Richard B. Kreckel wrote: > Okay, all that has just been fixed upstream now. I contend that the cross build still loops for ppc64el. It kinda feels like a different issue though. Should we close this one and open a new one or retitle? The issue is

Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-19 Thread Richard B. Kreckel
On 12.10.20 20:49, Helmut Grohne wrote: I strongly suggest that you do not proxy builds through me. The latency is much higher than doing it yourself. The primary goal of cross builds is that you can build for anything on your box instead of having to own the target box. All you need to do is

Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-12 Thread Helmut Grohne
Hi, On Sun, Oct 11, 2020 at 11:04:05PM +0200, Richard B. Kreckel wrote: > > Before I dig into this, could you, please, try applying the attached patch > and check if it works? I strongly suggest that you do not proxy builds through me. The latency is much higher than doing it yourself. The

Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-11 Thread Richard B. Kreckel
On 11.10.20 19:28, Helmut Grohne wrote: If you are interested in figuring out why this happens, all the better, I guess you should pass --anything-failed-commands=%SBUILD_SHELL to sbuild and examine config.log. Before I dig into this, could you, please, try applying the attached patch and

Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-11 Thread Helmut Grohne
On Sun, Oct 11, 2020 at 12:27:03PM +0200, Richard B. Kreckel wrote: > Thank you! Your patch has been upstreamed. Great! This is not urgent from my pov, just close the Debian bug with the new upstream upload. > > I fear this is not the only issue. For instance on ppc64el, the build > > times out

Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-11 Thread Richard B. Kreckel
On 10.10.20 07:04, Helmut Grohne wrote: Source: cln Version: 1.3.6-4 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs cln fails to cross build from source, because it checks for the size of intptr_t without including . It thus fails detecting a size and errors out.

Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-09 Thread Helmut Grohne
Source: cln Version: 1.3.6-4 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs cln fails to cross build from source, because it checks for the size of intptr_t without including . It thus fails detecting a size and errors out. Please add the required include. I'm attaching