On Mon, 22 Apr 2024 at 22:54, Chet Ramey <chet.ra...@case.edu> wrote:
>
> On 4/22/24 11:58 AM, Chet Ramey wrote:
> > On 4/20/24 2:02 AM, Cedric Blancher wrote:
> >
> >>> You can check what env the submake in question has and which recipe
> >>> runs it and see where this setting comes from.
> >>
> >> We were only using
> >> make -j16 all
> >> at the bash base dir. That should NOT trigger this warning.
> >
> > Bash passes ${MFLAGS} to makes in subdirectories; that variable gets
> > whatever make puts in it, which includes the -jN option. It's that
> > submake that decides to print that warning. Bash could mark some
> > subdirectory targets as not parallel, but why would we do that?
>
> Everyone seems to support MAKEFLAGS by now, and it's part of POSIX, so
> maybe we delete $(MFLAGS) and rely on make to pass MAKEFLAGS to submakes
> in the environment.Could you do this for the next alpha release, please? Dan -- Dan Shelton - Cluster Specialist Win/Lin/Bsd
