On 2024-04-09 18:06, Sam James wrote:
> Nick poses that a specific combination of tools is what is tested and
> anything else invalidates it. But how does this work when building on
> a system that was never tested on, or with different flags, or a
> different toolchain?
>
> It's reasonable to say
Follow-up Comment #5, sr #111048 (group autoconf):
[comment #4 comment #4:]
> Note that adding a syntax check before each check will certainly make
"configure" somewhat slower. Should we prefer increasing security at the cost
of something slower?
You only need to run the syntax checker if the te
Sam James replied to Bruno Haible who cited Nick Bowler:
> >> If I distribute a release package, what I have tested is exactly what is
> >> in that package. If you start replacing different versions of m4 macros,
> >> or use some distribution-patched autoconf/automake/libtool or whatever,
> >> the
Bruno Haible writes:
> Nick Bowler wrote:
>> If I distribute a release package, what I have tested is exactly what is
>> in that package. If you start replacing different versions of m4 macros,
>> or use some distribution-patched autoconf/automake/libtool or whatever,
>> then this you have inval
