[Bug driver/109135] Wrong make utility called with LTO testsuite
rguenth at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Wed Mar 15 08:35:41 GMT 2023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109135
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Steve Kargl from comment #4)
> On Tue, Mar 14, 2023 at 10:36:27PM +0000, sgk at troutmask dot
> apl.washington.edu wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109135
> >
> > --- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
> > On Tue, Mar 14, 2023 at 10:25:53PM +0000, pinskia at gcc dot gnu.org wrote:
> > >
> > > --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> > > This is not a testsuite issue but rather the issue is the lto code is calling
> > > make ...
> > >
> >
> > That explains why groping around in gcc/testsuite for
> > a rogue make or MAKE was coming up empty.
> >
> > I'm in the middle of doing a serial 'gmake check-fortran',
> > which takes a long time on my system. Is there a way
> > to invoke only lto testing?
>
> So, 'gmake check-fortran' finishes without any lto issues.
> It seems one must invoke the checking with 'gmake -j6 check-fortran'
> to get failures.
>
> Looking in obj/gcc/Makefile at line 341 I see the comment
>
> # Make sure the $(MAKE) variable is defined.
>
> followed by no checking to see if MAKE is defined.
Makefile.in has
# Make sure the $(MAKE) variable is defined.
@SET_MAKE@
configure has
if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
SET_MAKE=
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
SET_MAKE="MAKE=${MAKE-make}"
fi
from AC_PROG_MAKE_SET which seems to check whether make sets $MAKE.
That appearantly succeeds for you. Do you "properly" do sth like
MAKE=gmake ../configure
so configure sees which make you are using? I think if your gmake
doesn't set it then even recursive configure invocations from gmake
will resort to 'make'
but then I _think_ that gmake itself sets $MAKE (if it was not set?) for
sub-processes. But maybe only if it thinks its recursive make?
More information about the Gcc-bugs
mailing list