public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Tadeus Prastowo <tadeus.prastowo@unitn.it>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: [make profiledbootstrap] gcc-9-build/x86_64-linux-gnu/libstdc++-v3/src/debug/Makefile: No such file or directory
Date: Thu, 30 May 2019 10:40:00 -0000	[thread overview]
Message-ID: <CAH6eHdQXcVsJOd_N1dHNarHJTxdYW_W2rqznEU3nc_gNXivsaw@mail.gmail.com> (raw)
In-Reply-To: <CAA1YtmsEfnT92HP9z81qMwXfqbsGDz4xr2hNpSgRLmw27jH7ow@mail.gmail.com>

On Thu, 30 May 2019 at 10:52, Tadeus Prastowo wrote:
>
> On Wed, May 29, 2019 at 11:53 PM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> > You probably want to add -j2 or -j4 to that command (or some other
> > value, depending how many cores you have) so you don't have to wait 10
> > hours.
>
> Thank you, I am aware of that.  I did not parallelize the build on
> purpose to compare the total time with the previous
> non-profiledbootstrap build.

Ah OK. You'd be surprised how many people aren't aware of parallel
make and so complain about how long it takes ;-)

> Any idea on how to find out the cause of the missing Makefile?  I

No sorry, I've not seen that error before.

      parent reply	other threads:[~2019-05-30 10:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 21:34 Tadeus Prastowo
2019-05-29 21:53 ` Jonathan Wakely
2019-05-30  9:58   ` Tadeus Prastowo
2019-06-03 12:37     ` Stefan Ring
2019-06-03 12:58       ` Tadeus Prastowo
2019-06-06  9:46         ` Tadeus Prastowo
     [not found]   ` <CAA1YtmsEfnT92HP9z81qMwXfqbsGDz4xr2hNpSgRLmw27jH7ow@mail.gmail.com>
2019-05-30 10:40     ` Jonathan Wakely [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=CAH6eHdQXcVsJOd_N1dHNarHJTxdYW_W2rqznEU3nc_gNXivsaw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=tadeus.prastowo@unitn.it \
    /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).