Summary: | sys-devel/gcc: libbacktrace is not installed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jonas Jelten <jj> |
Component: | [OLD] Development | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | jj |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://gcc.gnu.org/PR66570 | ||
See Also: | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66570 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jonas Jelten
2015-06-14 14:20:51 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. 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 (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. 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? (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 |