I'm sorry I didn't think of this before, but another option would be to
use the build.sh bootstrapping script, which we provide for situations
where you want to build GNU Make on systems where there isn't already a
make instance available.
This doesn't run make and doesn't require a configure, it
Unfortunately it looks like I won't be able to get this solved. I was
hoping to, and even thinking of contributing some README-type documentation
on how to do it, but I just couldn't get it to work and we ended up solving
the problem another way so the impetus is gone. I didn't keep track of all
th
Thank you both for the replies. I've had little time to get back to this
and little success when I tried but it's too early to draw any conclusions.
I'll update on progress when I get back to it.
Paul, I didn't know "make make" was an option but it doesn't seem to help.
Actually I think there's a
On Fri, Mar 8, 2024 at 9:32 AM DSB wrote:
> Is there a scripted way to
> reliably build make at each bisection point (assuming 4.3 as the minimum)?
There is definitely a scripted way to do this.
i use this small makefile (see in the attachment) instead of the
automake generated one.
This makefile
On Fri, 2024-03-08 at 07:01 -0500, DSB wrote:
> So my question is: has anyone done this before? Is there a scripted
> way to reliably build make at each bisection point (assuming 4.3 as
> the minimum)?
I have never tried to do this, but yes certainly each commit was
buildable when it was committed
Background situation: we're seeing an error that manifests reliably when
make 4.4.1 is used but not with 4.3. This isn't necessarily a make problem,
there are many other tools involved, but the insight we have is that 4.41
reliably triggers it vs 4.3. Therefore I'm trying to narrow it down by
doing