public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <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 14:33:34 +0000 [thread overview] Message-ID: <bug-109135-4-FCNJBldXLH@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 #7 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Wed, Mar 15, 2023 at 08:35:41AM +0000, rguenth at gcc dot gnu.org wrote: > 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: > > > > 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 No. I simply use '../configure ; gmake -j6 bootstrap'. This has worked for years. I'm currently using GNU make 4.3. If MAKE is not being set to gmake, then I would expect bootstrap to fail. I plan to run gmake with debugging output, and need to check gmake.info to see how to dump the environment information. > 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? I suppose I'll start using the 'MAKE=gmake ..' form or some variation as I use tcsh.
prev parent reply other threads:[~2023-03-15 14:33 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 2023-03-15 14:33 ` sgk at troutmask dot apl.washington.edu [this message]
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-FCNJBldXLH@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: linkBe 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).