public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
	GCC Development <gcc@gcc.gnu.org>
Subject: Re: testsuite requires LTO?
Date: Tue, 12 Apr 2022 11:03:39 -0700	[thread overview]
Message-ID: <YlW++8xm/bkgYSmT@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CAH6eHdQKunKjiXaGjdvO1O+9t6N445UVtRGsBFqYGcjFvoWc4A@mail.gmail.com>

On Tue, Apr 12, 2022 at 06:42:20PM +0100, Jonathan Wakely wrote:
> On Tue, 12 Apr 2022 at 18:32, Steve Kargl wrote:
> > Well, I determined what the problem is.  On FreeBSD,
> > GNU make is gmake.  make(1) on FreeBSD is BSD make.
> >
> > % gmake -j7 check-c
> >
> > Does not pass down the name of the invoking command
> > to sub-make jobs.
> 
> That suggests some makefile is using 'make' directly, not using
> $(MAKE). But if that was the case, then setting MAKE in the
> environment wouldn't help either.
> 
> What version of gmake do you have?

% gmake --version
GNU Make 4.3
Built for amd64-portbld-freebsd13.0

It's the version from FreeBSD port collection.

I just started a new bootstrap with LTO enabled
without any patches in my gcc tree to try to get
a baseline.  It will take a bit.

-- 
Steve

  reply	other threads:[~2022-04-12 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 23:51 Steve Kargl
2022-04-12  7:07 ` Richard Biener
2022-04-12  7:26   ` Richard Biener
2022-04-12 17:30     ` Steve Kargl
2022-04-12 17:42       ` Jonathan Wakely
2022-04-12 18:03         ` Steve Kargl [this message]
2022-04-12  7:41 ` Andreas Schwab

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=YlW++8xm/bkgYSmT@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=richard.guenther@gmail.com \
    /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).