backtrace.h not installed with --enable-plugin

[basile@starynkevitch.net]

On 2017-06-14 11:05, Richard Biener wrote:
> On Wed, Jun 14, 2017 at 9:08 AM,  <basile@starynkevitch.net> wrote:
>> Hello All,
>> 
>> I compiled a gcc-7.1 release tree configured with
>> 
>> '../gcc-7.1.0/configure'   '--program-suffix=-7my' '--enable-shared'
>> '--enable-linker-build-id' '--without-included-gettext'
>> '--enable-threads=posix' '--with-sysroot=/' '--enable-clocale=gnu'
>> '--enable-libstdcxx-debug' '--enable-libstdcxx-time=yes'
>> '--with-default-libstdcxx-abi=new' '--enable-gnu-unique-object'
>> '--enable-libmpx' '--enable-plugin' '--enable-default-pie'
>> '--with-system-zlib' '--enable-multiarch' '--with-arch-32=i686'
>> '--with-abi=m64' '--with-multilib-list=m32,m64,mx32' 
>> '--enable-multilib'
>> '--with-tune=native' '--enable-checking=release'
>> '--enable-languages=c,c++,go,lto'

I forgot to tell that my platform is a Linux/Debian/Sid/x86-64

>> 
>> I was expecting the installed built tree to contain the backtrace.h 
>> from Ian
>> Taylor's libbacktrace. This is not the case. Why? What configure 
>> option did
>> I miss?
> 
> libbacktrace is a convenience library only and is not installed so why 
> do
> you expect backtrace.h to be installed?


Because GCC plugins should be able to use it. Also, that library is 
linked into
cc1plus (whose symbols contain backtrace_open, backtrace_free, 
backtrace_create_state and so forth)

So it does not cost much to publish backtrace.h when plugins are enabled 
(the static libbacktrace library is part of the cc1plus)


BTW, on Debian/x86-64 
/usr/lib/gcc/x86_64-linux-gnu/6/include/backtrace.h is part of 
libgcc-6-dev which also provides files 
/usr/lib/gcc/x86_64-linux-gnu/6/libasan.so etc, which are definitely 
provided by GCC.

Cheers.
--
Basile Starynkevitch (France) http://starynkevitch.net/Basile/