Re: strange issues with building ArcticFox - full rebuilds everytime

[RVP <rvp%SDF.ORG@localhost>]

On Fri, 7 Jun 2024, Riccardo Mottola wrote:

> I actually executed in an xterm, interrupted after a couple of minutes and 
> checked the scrollback - configure is rerun.
>
> This does not happen on linux or FreeBSD.

Well, Linux systems usually have bash and a lot of the scripts in Arctic-Fox
hard-code `#!/bin/bash'. And, as for FreeBSD, it's test(1) understands `=='
as a synonym for `='. I noticed this failure too in the error messages.

However, these may not be the issue at all:

> Just as an idea, I checked dates:
>
> -rwxr-xr-x  1 multix  users   221 Jun  6 01:24 configure
> -rw-r--r--  1 multix  users  1154 Mar  5 01:29 configure.in
> -rw-r--r--  1 multix  users  873016 Jun  6 01:25 old-configure
> -rw-r--r--  1 multix  users  253669 Jun  6 01:19 old-configure.in
>
> the ".in" files are suspiciously new, as in the previous run. But I didn't 
> update them. Comparing to linux, I see they are not touched since the last 
> commit to them:
> -rwxr-xr-x 1 multix users  221 May 29 16:08 configure
> -rw-r--r-- 1 multix users 1154 Feb 19 11:24 configure.in
> -rw-r--r-- 1 multix users 874090 May 29 16:08 old-configure
> -rw-r--r-- 1 multix users 253669 May 29 15:30 old-configure.in
>
> the checked out repository is the same... Just to be sure, I yanked the build 
> dir and retried..... no avail.

I tried to compile both the 44.0 release and the latest source, and while the
build didn't get to the compile stage, rerunning `mach build' after it fails
the first time doesn't trigger configure at all on my setup. Error log for
the 2nd run attached (owing probably to some missing dependency which was not
checked for; everything that `mach build' complained about, I installed from
binary packages).

If I do a `mach clobber', then confgure is, of course, re-run on the next
`mach build'.

-RVP

Attachment: err.log.gz
Description: Arctic-Fox-master build error log.