Re: recursion limit of 1024 exceeded

[Dagobert Michelsen]

Hi Paul,

Am 12.12.2020 um 20:29 schrieb Paul Eggert <eggert@cs.ucla.edu>:
> On 12/12/20 4:13 AM, Dagobert Michelsen wrote:
>> m4 should be current, meanwhile I tried to update autoconf to 2.70 with
>> 3 unexpected failures and automake to 14 unexpected failures which I will
>> report on the respective mailing lists.
>> Do you think the error could be from outdated versions of these two?
> 
> It's possible, since I just installed some patches into Gnulib related to 
> Autoconf 2.70. I did test those patches with Autoconf 2.69 too (as patched 
> for Fedora 33), so if the problem is Autoconf related, most likely it's a 
> problem fixed in the Fedora patches for Autoconf 2.69 which means you would 
> be better off with Autoconf 2.70.
> 
> Despite my fondness and nostalgia for Solaris, I don't bother with testing 
> gnulib-tool on Solaris 10 because Solaris 10 ships with GNU m4 1.4.2, 
> Autoconf 2.59, and Automake 1.8.3, and so it's no longer a suitable porting 
> target for Gnulib development. That is, although you can build from 
> Gnulib-based tarballs on Solaris 10, you can't build from Git development 
> trees (Solaris 10 doesn't even have Git) without doing a lot of work and it's 
> not worth the effort to me. Instead, I suggest running './gnulib-tool 
> --create-testdir --dir FOO ...' on a more up-to-date platform, copying FOO to 
> Solaris 10, and then testing just './configure && make' on the copy of FOO on 
> Solaris 10.

I see, would that also count as viable solution for Gnulib CI on Solaris? I 
have other,
more recent systems around to use on the CI system of that would help.


Best regards

  — Dago

-- 
"You don't become great by trying to be great, you become great by wanting to 
do something,
and then doing it so hard that you become great in the process." - xkcd #896