public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/109135] Wrong make utility called with LTO testsuite
Date: Wed, 15 Mar 2023 08:35:41 +0000 [thread overview]
Message-ID: <bug-109135-4-T0qVDDXOhI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109135-4@http.gcc.gnu.org/bugzilla/>
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?
next prev parent reply other threads:[~2023-03-15 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 22:23 [Bug testsuite/109135] New: " kargl at gcc dot gnu.org
2023-03-14 22:25 ` [Bug driver/109135] " pinskia at gcc dot gnu.org
2023-03-14 22:30 ` pinskia at gcc dot gnu.org
2023-03-14 22:36 ` sgk at troutmask dot apl.washington.edu
2023-03-14 23:06 ` sgk at troutmask dot apl.washington.edu
2023-03-14 23:14 ` sgk at troutmask dot apl.washington.edu
2023-03-15 8:35 ` rguenth at gcc dot gnu.org [this message]
2023-03-15 14:33 ` sgk at troutmask dot apl.washington.edu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-109135-4-T0qVDDXOhI@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).