From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: SAIFI <saifi@strikr.io>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: backtrace-supported.h not found during build
Date: Mon, 17 Jan 2022 21:09:11 +0000 [thread overview]
Message-ID: <CAH6eHdQXxxO5E-LsRokKXHEDgzT8CFLt12kZwN_unYZz2XVoOA@mail.gmail.com> (raw)
In-Reply-To: <82b5f2b1-69fd-c010-e282-7524e8e9c378@strikr.io>
On Mon, 17 Jan 2022 at 18:54, SAIFI <saifi@strikr.io> wrote:
>
> Hi:
>
> an out-of-tree build of gcc (git:main) was configured with the following option.
>
> --enable-libstdcxx-backtrace=yes
>
> the source tree build went fine, however when it came to building 'libbacktrace' the compilation error'd out as seen below.
>
> Making all in libbacktrace
> make[6]: Entering directory '/strikr/infra/build/gcc/x86_64-pc-linux-gnu/libstdc++-v3/src/debug/libbacktrace'
> /bin/sh ../../../libtool --tag=CC --mode=compile /strikr/infra/build/gcc/./gcc/xgcc -B/strikr/infra/build/gcc/./gcc/ -B/opt/gcc/x86_\
> 64-pc-linux-gnu/bin/ -B/opt/gcc/x86_64-pc-linux-gnu/lib/ -isystem /opt/gcc/x86_64-pc-linux-gnu/include -isystem /opt/gcc/x86_64-pc-linu\
> x-gnu/sys-include -fchecking=1 -DHAVE_CONFIG_H -I. -I/strikr/src/gcc/libstdc++-v3/src/libbacktrace -I../../.. -I /strikr/src/gcc/lib\
> stdc++-v3/../include -I /strikr/src/gcc/libstdc++-v3/../libgcc -I ../../../libgcc -I .. -I /strikr/src/gcc/libstdc++-v3 -I /strikr/src/\
> gcc/libstdc++-v3/../libbacktrace -include /strikr/src/gcc/libstdc++-v3/src/libbacktrace/backtrace-rename.h -DHAVE_ATOMIC_FUNCTIONS=1 -D\
> HAVE_SYNC_FUNCTIONS=1 -DHAVE_FCNTL=1 -DBACKTRACE_ELF_SIZE=64 -W -Wall -Wwrite-strings -Wmissing-format-attribute -Wcast-qual -Werror -\
> Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wno-unused-but-set-variable -fcf-protection -mshstk -g -O2 -c -o atomic\
> .lo `test -f '../../../libbacktrace/atomic.c' || echo '/strikr/src/gcc/libstdc++-v3/src/libbacktrace/'`../../../libbacktrace/atomic.c
> libtool: compile: /strikr/infra/build/gcc/./gcc/xgcc -B/strikr/infra/build/gcc/./gcc/ -B/opt/gcc/x86_64-pc-linux-gnu/bin/ -B/opt/gcc/x\
> 86_64-pc-linux-gnu/lib/ -isystem /opt/gcc/x86_64-pc-linux-gnu/include -isystem /opt/gcc/x86_64-pc-linux-gnu/sys-include -fchecking=1 -D\
> HAVE_CONFIG_H -I. -I/strikr/src/gcc/libstdc++-v3/src/libbacktrace -I../../.. -I /strikr/src/gcc/libstdc++-v3/../include -I /strikr/src/\
> gcc/libstdc++-v3/../libgcc -I ../../../libgcc -I .. -I /strikr/src/gcc/libstdc++-v3 -I /strikr/src/gcc/libstdc++-v3/../libbacktrace -in\
> clude /strikr/src/gcc/libstdc++-v3/src/libbacktrace/backtrace-rename.h -DHAVE_ATOMIC_FUNCTIONS=1 -DHAVE_SYNC_FUNCTIONS=1 -DHAVE_FCNTL=1\
> -DBACKTRACE_ELF_SIZE=64 -W -Wall -Wwrite-strings -Wmissing-format-attribute -Wcast-qual -Werror -Wstrict-prototypes -Wmissing-prototyp\
> es -Wold-style-definition -Wno-unused-but-set-variable -fcf-protection -mshstk -g -O2 -c /strikr/src/gcc/libstdc++-v3/src/libbacktrace/\
> ../../../libbacktrace/atomic.c -fPIC -DPIC -o .libs/atomic.o
> /strikr/src/gcc/libstdc++-v3/src/libbacktrace/../../../libbacktrace/atomic.c:38:10: fatal error: backtrace-supported.h: No such file or\
> directory
> 38 | #include "backtrace-supported.h"
> | ^~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
>
> However, in the build directory, the header file is seen
>
> f$ find . -iname "backtrace-supported.h"
> ./stage1-libbacktrace/backtrace-supported.h
> ./x86_64-pc-linux-gnu/libstdc++-v3/src/libbacktrace/backtrace-supported.h
> ./prev-libbacktrace/backtrace-supported.h
> ./stage1-x86_64-pc-linux-gnu/libstdc++-v3/src/libbacktrace/backtrace-supported.h
> ./libbacktrace/backtrace-supported.h
> ./prev-x86_64-pc-linux-gnu/libstdc++-v3/src/libbacktrace/backtrace-supported.h
>
> Am I missing something here ? Any pointers ?
The build output says:
make[6]: Entering directory
'/strikr/infra/build/gcc/x86_64-pc-linux-gnu/libstdc++-v3/src/debug/libbacktrace'
And the header is not present in that directory.
It looks like I didn't test the combination of
--enable-libstdcxx-debug and --enable-libstdcxx-backtrace
next prev parent reply other threads:[~2022-01-17 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 18:54 SAIFI
2022-01-17 21:09 ` Jonathan Wakely [this message]
2022-01-17 21:41 ` Jonathan Wakely
2022-01-19 15:01 ` 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=CAH6eHdQXxxO5E-LsRokKXHEDgzT8CFLt12kZwN_unYZz2XVoOA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=saifi@strikr.io \
/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).