On Mon, Jun 3, 2019 at 2:37 PM Stefan Ring <stefanrin@xxxxxxxxx> wrote: > > On Thu, May 30, 2019 at 11:58 AM Tadeus Prastowo > <tadeus.prastowo@xxxxxxxx> 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. -- Best regards, Tadeus
