|Summary:||sys-devel/gcc: libbacktrace is not installed|
|Product:||Gentoo Linux||Reporter:||Jonas Jelten <jj>|
|Component:||[OLD] Development||Assignee:||Gentoo Toolchain Maintainers <toolchain>|
|Package list:||Runtime testing required:||---|
Description Jonas Jelten 2015-06-14 14:20:51 UTC
gcc includes a nice library for getting c/c++ backtraces: libbacktrace. This library should also be installed by the gcc ebuild. Debian includes it in libgcc-4.8-dev and later (https://packages.debian.org/sid/amd64/libgcc-4.9-dev/filelist). The files missing are mainly: * /usr/lib/gcc/x86_64-pc-linux-gnu/$version/include/backtrace.h * /usr/lib/gcc/x86_64-pc-linux-gnu/$version/libbacktrace.a Please adjust the build to also install these files so that programs can use libbacktrace. Reproducible: Always
Comment 1 Jonas Jelten 2015-06-14 14:27:28 UTC
Comment 2 SpanKY 2015-06-17 07:37:10 UTC
gcc specifically does not install it: libbacktrace/Makefile.am: noinst_LTLIBRARIES = libbacktrace.la you could file a request with them to have it be installed (at gcc.gnu.org), but i don't think we want to start exporting what looks like a purely internal library when upstream doesn't intend for it to be used externally.
Comment 3 Jonas Jelten 2015-06-17 14:42:26 UTC
Hmm, but why/how does debian do it then? Anyway, I created a gcc issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66570
Comment 4 SpanKY 2015-06-17 15:15:15 UTC
(In reply to Jonas Jelten from comment #3) a scan of their deb rules looks like they do it all by hand which is what i want to avoid. that they choose to do so is up to their maintainers.
Comment 5 Michael Jones 2020-01-23 19:33:21 UTC
This is negatively effecting me. Most other distributions provide libbacktrace, but Gentoo doesn't, and there's no practical way for an end user to address that. Can't this be a USE flag?
Comment 6 Sergei Trofimovich (RETIRED) 2020-01-23 19:41:40 UTC
(In reply to Michael Jones from comment #5) > This is negatively effecting me. > > Most other distributions provide libbacktrace, but Gentoo doesn't, and > there's no practical way for an end user to address that. > > Can't this be a USE flag? I suggest prodding upstream bug report: https://gcc.gnu.org/PR66570