Re: GNU Make 4.3.92 release candidate available

[Sam James]

> On 24 Oct 2022, at 14:17, Frank Heckenbach  wrote:
> 
> Paul Smith wrote:
> 
>> I expect this to be the final release candidate before GNU Make 4.4.
>> I will probably allow for testing for about a week.

> All problems I reported appear fixed, thanks.
> 

Indeed, me too. I'd forgotten I was even using it :)



signature.asc
Description: Message signed with OpenPGP

Re: GNU make 4.3.90 release candidate available

[Sam James]

> On 24 Sep 2022, at 18:45, Paul Smith  wrote:
> 
> On Wed, 2022-09-21 at 06:18 +0100, Sam James wrote:
>> Can I suggest forwarding to the platform-testers@ mailing list as
>> well?
> 
> I've never heard of this; is it @gnu.org?  Or somewhere else?  A full
> email address would be useful and also if you have any information on
> this (a website or whatever) that would be good.
> 

Eli beat me to explaining - sorry for being vague! You got it exactly,
just platform-test...@gnu.org as a mailing list.

> Cheers!
> 

best,
sam



signature.asc
Description: Message signed with OpenPGP

Re: [PATCH] Pacify GCC -Wsign-compare

[Sam James]

> On 22 Sep 2022, at 01:24, Paul Eggert  wrote:
> 
> On 9/21/22 16:11, Sam James wrote:
>> For these, could you consider including the full version?
> 
> Sure, revised patch attached.<0001-Pacify-GCC-Wsign-compare.patch>

Thanks and looks good.


signature.asc
Description: Message signed with OpenPGP

Re: GNU make 4.3.90 release candidate available

[Sam James]

> On 20 Sep 2022, at 19:36, Paul Smith  wrote:
> 
>
>GNU make is a tool which controls the generation of executables and
>other non-source files of a program from the program's source files.
> 
>You can learn more at: https://www.gnu.org/software/make/
>
> 
> A new release candidate for GNU make 4.4 is available now for download:

Can I suggest forwarding to the platform-testers@ mailing list as well?

Cheers!


signature.asc
Description: Message signed with OpenPGP

Re: New release of GNU make

[Sam James]

> On 15 Sep 2022, at 14:39, Paul Smith  wrote:
> 
> On Thu, 2022-09-15 at 14:00 +0100, Sam James wrote:
>>> Very preliminary results (only mild testing done so far)
>>> but the only failure I've hit thus far is autoconf-2.71:
>>> https://bugs.gentoo.org/869257.
>>> 
>>> I'll continue testing.
>> 
>> It's been very quiet indeed, which is good news.
> 
> That is good news, thank you.
> 
> I'm going to make one final push this weekend to try to get the signal
> handling / termination code working the way I want it.  Regardless of
> whether I succeed or not I intend to package an RC1 release no later
> than Monday.
> 
> I have a few other bugs reported with patches on Savannah that I will
> at least investigate, as well.
> 
> In order to give the translators etc. time to work on it, as well as
> allow for some more soak time with other testers who may not want to
> build from Git, I will allow at least 2 weeks of test time for the
> release candidate cycle.
> 
> That would put the release sometime in early October, unless issues are
> found that push things out.
> 

This sounds like a solid plan. Cheers!


signature.asc
Description: Message signed with OpenPGP

Re: New release of GNU make

[Sam James]

> On 9 Sep 2022, at 05:36, Sam James  wrote:
> 
> 
> 
>> On 8 Sep 2022, at 22:41, Sam James  wrote:
>> 
>> 
>> 
>>> On 8 Sep 2022, at 08:12, Paul Smith  wrote:
>>> 
>>> On Mon, 2022-09-05 at 03:47 +0100, Sam James wrote:
>>>> I started testing master recently and hit
>>>> https://savannah.gnu.org/bugs/?63016
>>>> which prevented doing any more testing.
>>> 
>> Hi Paul,
> 
> Very preliminary results (only mild testing done so far)
> but the only failure I've hit thus far is autoconf-2.71:
> https://bugs.gentoo.org/869257.
> 
> I'll continue testing.

It's been very quiet indeed, which is good news.

Best,
sam


signature.asc
Description: Message signed with OpenPGP

[bug #63040] autoconf-2.69 and 2.71 fail to build after $(shell ...) environment handlign change

[Sam James]

Follow-up Comment #3, bug #63040 (project make):

Indeed autoconf has fixed it as
https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=31f673434ee402258b45e958c88acc8725d82b1a
but I don't know whether this change in behaviour was intended or not.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

Re: New release of GNU make

[Sam James]

> On 8 Sep 2022, at 22:41, Sam James  wrote:
> 
> 
> 
>> On 8 Sep 2022, at 08:12, Paul Smith  wrote:
>> 
>> On Mon, 2022-09-05 at 03:47 +0100, Sam James wrote:
>>> I started testing master recently and hit
>>> https://savannah.gnu.org/bugs/?63016
>>> which prevented doing any more testing.
>> 
> Hi Paul,

Very preliminary results (only mild testing done so far)
but the only failure I've hit thus far is autoconf-2.71:
https://bugs.gentoo.org/869257.

I'll continue testing.

Best,
sam


signature.asc
Description: Message signed with OpenPGP

Re: New release of GNU make

[Sam James]

> On 8 Sep 2022, at 08:12, Paul Smith  wrote:
> 
> On Mon, 2022-09-05 at 03:47 +0100, Sam James wrote:
>> I started testing master recently and hit
>> https://savannah.gnu.org/bugs/?63016
>> which prevented doing any more testing.
> 
Hi Paul,

> Hopefully this is fixed.  It works for the examples given anyway.
> 
> I also downgraded the required version of autoconf to 2.69 (and tested
> that this works, for now at least).
> 

Thanks for the quick fix. We're resumed testing in Gentoo and I will
let you know in a few days if anything has or hasn't popped up.

I think provided you're planning on a release candidate/alpha
release before the real final release, you should feel free
to go ahead with the process to get some wider testing.

Many thanks!

Best,
sam


signature.asc
Description: Message signed with OpenPGP

Re: New release of GNU make

[Sam James]

> On 6 Sep 2022, at 15:58, Paul Smith  wrote:
> 
> On Mon, 2022-09-05 at 03:47 +0100, Sam James wrote:
>> I started testing master recently and hit
>> https://savannah.gnu.org/bugs/?63016
>> which prevented doing any more testing.
> 
> Just curious: why does this prevent doing any more testing?
> 

We usually try to test new versions of things before they come out
and build all packages against it.

When we started testing in Gentoo (not unleashed onto users),
we had several failures that looks liked this almost immediately.

This tends to be a sign of more to come if things fall out
very quickly.

We had:
- https://bugs.gentoo.org/867892 ("media-gfx/gif2png-2.5.14:0 - 
Makefile:: Recursive variable VERSION references itself (eventually). 
Stop.")
- https://bugs.gentoo.org/867895 ("dev-lang/mercury-22.01.1:0 - Recursive 
variable 'GRADESTRING' references itself (eventually). Stop.")
- https://bugs.gentoo.org/867904 ("games-simulation/simutrans-123.0.1-r1:0 - 
Makefile:: Recursive variable CFLAGS references itself (eventually). 
Stop.")

I didn't bother continuing given:
1. This happened so quickly and I suspect there'd be
many duplicates;
2. Dependencies failing to build makes it more awkward to test other
packages;
3. Any fix for this might end up influencing other results anyway,
so I'd need to test again once this issue is fixed.

If you think this is another issue, I can file
a separate, new bug.

Best,
sam


signature.asc
Description: Message signed with OpenPGP

Re: New release of GNU make

[Sam James]

> On 3 Sep 2022, at 23:55, Paul Smith  wrote:
> 
> Hi all.
> 
> I would like to work on putting out a new release of GNU make.  I've
> fixed, or merged patches for (thanks especially to Dmitry) most of the
> issues that I had in mind for this release, except one: I'd really like
> to fix the problem we currently have with handling fatal signals (like
> SIGINT), because die() is invoked in a signal handler context and it
> does all sorts of things that are not valid in a signal handler.
> 
> I have a partial solution to this but it runs up against the age-old
> problem of trying to both wait for data on a file descriptor and also
> wait for a child to exit, reliably, in a POSIX system.  I'm thinking
> about ways to manage this.
> 
> But in the meantime I wanted to let people know in case they wanted to
> point out particularly egregious bugs that should absolutely be looked
> at before the release (obviously any regressions are most important).

I started testing master recently and hit https://savannah.gnu.org/bugs/?63016
which prevented doing any more testing.

> 
> As always I'll be creating release candidates and announcing them here
> for people to try out who don't want to go through the process of
> bootstrapping from a Git workspace.
> 

Thanks for working on a new release.

Best,
sam


signature.asc
Description: Message signed with OpenPGP

[bug #62223] Release new version of make? 4.3.1?

[Sam James]

Follow-up Comment #1, bug #62223 (project make):

This is now in the works, it seems:
https://lists.gnu.org/archive/html/bug-make/2022-09/msg3.html.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/