Re: `checking size of mp_limb_t... 0` and `configure: error: Oops, mp_limb_t doesn't seem to work` when compiling the Microchip XC32 compiler from source

Marc, yes, I see that too now. For anyone wondering where that is, here it is: https://github.com/ElectricRCAircraftGuy/Microchip_XC32_Compiler/blob/main/xc32-v4.35-src/pic32m-source/gmp-6.1.0/acinclude.m4#L125-L140 What I'm calling, by the way, inside build-xc32-v4.35m.sh, is this: https://github

Re: `checking size of mp_limb_t... 0` and `configure: error: Oops, mp_limb_t doesn't seem to work` when compiling the Microchip XC32 compiler from source

Marc Glisse writes: > From acinclude.m4: > > > dnl GMP_INCLUDE_GMP_H > dnl - > dnl Expand to the right way to #include gmp-h.in. This must be used > dnl instead of gmp.h, since that file isn't generated until the end > of the > dnl configure. > dnl > dnl Dummy value for GMP

Re: `checking size of mp_limb_t... 0` and `configure: error: Oops, mp_limb_t doesn't seem to work` when compiling the Microchip XC32 compiler from source

On Tue, 7 Nov 2023, Niels Möller wrote: (2) It makes no sense for any C code, in conftest.c or otherwise, to ever attempt to include gmp-h.in. That's not a valid C header file, since it lacks the substitutions that turns it into a valid gmp.h header file. From acinclude.m4: dnl GMP

Re: `checking size of mp_limb_t... 0` and `configure: error: Oops, mp_limb_t doesn't seem to work` when compiling the Microchip XC32 compiler from source

"Stinking" and "stinker" are playful terms in American English--things you'd call your little kids when they're being cute or funny. It's more of a playful term. In this context it expresses excitement that I found the bug. To a non-native American English speaker, I can see the confusion. I was ve

Re: `checking size of mp_limb_t... 0` and `configure: error: Oops, mp_limb_t doesn't seem to work` when compiling the Microchip XC32 compiler from source

Thanks, Niels. I had been looking in config.log and came across a failure to include a file with an absolute path. I found the solution and wrote about it here: https://stackoverflow.com/a/77435216/4561887 On Fri, Nov 3, 2023 at 9:50 AM Niels Möller wrote: > When debugging configure issues, th

Re: `checking size of mp_limb_t... 0` and `configure: error: Oops, mp_limb_t doesn't seem to work` when compiling the Microchip XC32 compiler from source

"Gabriel Staples, ElectricRCAircraftGuy.com" writes: > In the answer , please jump > halfway down, to the section titled "Explanation of the > ${gcc_srcdir_RELATIVE}/configure relative path fix that works". I can > neither explain it more nor less sim

Re: `checking size of mp_limb_t... 0` and `configure: error: Oops, mp_limb_t doesn't seem to work` when compiling the Microchip XC32 compiler from source

"Gabriel Staples, ElectricRCAircraftGuy.com" writes: > Thanks, Niels. I had been looking in config.log and came across a failure > to include a file with an absolute path. I found the solution and wrote > about it here: https://stackoverflow.com/a/77435216/4561887 I've had a quick look, but real

Re: `checking size of mp_limb_t... 0` and `configure: error: Oops, mp_limb_t doesn't seem to work` when compiling the Microchip XC32 compiler from source

When debugging configure issues, the first step is to check config.log. That should tell you in detail what configure tried to compile or run, and how it failed. Regards, /Niels "Gabriel Staples, ElectricRCAircraftGuy.com" skrev: (3 november 2023 08:26:03 CET) >I could really use some help he