public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tadeus Prastowo <tadeus.prastowo@unitn.it>
To: 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 09:58:00 -0000	[thread overview]
Message-ID: <CAA1Ytmv-65MzfEnajaUvXzKODiZsdqsDZ4Y_ecTCAQYBbXgcbQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdQDzWSEOBLe2f5VOqjEinLZtwaTnGcWSgoekz=WOSGziw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]

On Wed, May 29, 2019 at 11:53 PM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> On Wed, 29 May 2019 at 22:34, Tadeus Prastowo wrote:
> >
> > Hello,
> >
> > I  am building GCC 9.1 in Ubuntu 16.04 (the host compiler is GCC 5.5.0).
> >
> > The GCC 9.1 source is the tarball released earlier this month after
> > the release announcement.
> >
> > The build is done in a separate build directory with the following
> > configure command:
> > ../gcc-9/configure --program-suffix=-9 --enable-languages=c,c++
> > --with-gcc-major-version-only --enable-shared --enable-linker-build-id
> > --without-included-gettext --enable-threads=posix --enable-nls
> > --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug
> > --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
> > --enable-gnu-unique-object --disable-vtable-verify --enable-plugin
> > --with-system-zlib --with-target-system-zlib=auto
> > --enable-objc-gc=auto --enable-multiarch --disable-werror
> > --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
> > --enable-multilib --with-tune=generic
> > --enable-offload-targets=nvptx-none --without-cuda-driver
> > --enable-checking=release --build=x86_64-linux-gnu
> > --host=x86_64-linux-gnu --target=x86_64-linux-gnu

Sorry, I left out the following configuration options during copy-paste:
--prefix=/home/eus/gcc-9 --srcdir=/home/eus/gcc-9

> > Afterwards, I issue the following command: make profiledbootstrap
> >
> > After 10 hours or so,
>
> 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.

Any idea on how to find out the cause of the missing Makefile?  I
attach the config.log file that I found under
`$buildir/x86_64-linux-gnu/libstdc++-v3/' as there is only one
config.log file under that directory according to: find
/homd/eus/buildzone/gcc-9-build/x86_64-linux-gnu/libstdc++-v3/ -iname
'*.log*', and the attached file ends with: configure: exit 0.

Thank you.

-- 
Best regards,
Tadeus

[-- Attachment #2: config.log.bz2 --]
[-- Type: application/x-bzip, Size: 24405 bytes --]

  reply	other threads:[~2019-05-30  9:58 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 [this message]
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

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=CAA1Ytmv-65MzfEnajaUvXzKODiZsdqsDZ4Y_ecTCAQYBbXgcbQ@mail.gmail.com \
    --to=tadeus.prastowo@unitn.it \
    --cc=gcc-help@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).