From: Tadeus Prastowo <tadeus.prastowo@unitn.it>
To: Stefan Ring <stefanrin@gmail.com>
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, 06 Jun 2019 09:46:00 -0000 [thread overview]
Message-ID: <CAA1Ytmuvx04nj_LHP5jVifKCV9by36DALkA2rvZ0H04bCbnKRw@mail.gmail.com> (raw)
In-Reply-To: <CAA1Ytmt+7XJ-Y+J-oXCy_N3MZ4rHGuVxsVPCS7FEFOwh9XE9DA@mail.gmail.com>
On Mon, Jun 3, 2019 at 2:57 PM Tadeus Prastowo <tadeus.prastowo@unitn.it> wrote:
>
> On Mon, Jun 3, 2019 at 2:37 PM Stefan Ring <stefanrin@gmail.com> wrote:
> >
> > On Thu, May 30, 2019 at 11:58 AM Tadeus Prastowo
> > <tadeus.prastowo@unitn.it> wrote:
> > >
> > > 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.
> >
> > It is easily reproducible, and
> >
> > $ ../gcc-9.1.0/configure --prefix=$HOME/gcc9 --enable-languages=c,c++
> > --enable-libstdcxx-debug --disable-multilib
> > $ make profiledbootstrap
> >
> > is enough. The same thing happens on Ubuntu bionic. Apparently
> > --enable-libstdcxx-debug and profiledbootstrap don’t play well
> > together. Either bootstrap or leaving out --enable-libstdcxx-debug
> > work. It’s just the combination of these two that breaks.
>
> Thank you very much for your feedback. I really appreciate it.
>
> Referring to the other thread for context
> (https://gcc.gnu.org/ml/gcc-help/2019-05/msg00154.html), I think the
> DEB packager has a patch for this problem because `debuild' uses both
> the switch --enable-libstdcxx-debug and the `profiledbootstrap' target
> successfully. I am trying to fish that patch out of the patches under
> `debian/patches' directory. I will report back.
I fished out the patch already and have described the solution used by
the PPA to solve this build problem at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90770#c0
--
Best regards,
Tadeus
next prev parent reply other threads:[~2019-06-06 9:46 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 [this message]
[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=CAA1Ytmuvx04nj_LHP5jVifKCV9by36DALkA2rvZ0H04bCbnKRw@mail.gmail.com \
--to=tadeus.prastowo@unitn.it \
--cc=gcc-help@gcc.gnu.org \
--cc=stefanrin@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).