public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "abraxa@dar-clan.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/66570] libbacktrace is not installed
Date: Mon, 27 Apr 2020 17:49:37 +0000	[thread overview]
Message-ID: <bug-66570-4-tABXX1X6D9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66570-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66570

--- Comment #3 from Soeren A. <abraxa@dar-clan.de> ---
Thanks for your response, Ian. Do you know how the GCC release managers can be
asked for their stance regarding this? I would assume that they're not CC'ed on
this bug report and I'm not familiar enough with the GCC organization to know
where to check.

So far, I haven't seen a libbacktrace package on any of the distros that I
checked, so my understanding of what you wrote is that an alternative way of
using libbacktrace would be to integrate it into the build process of the
program that wishes to use it and link it to the executable statically. Is this
understanding correct?

  parent reply	other threads:[~2020-04-27 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 14:40 [Bug libgcc/66570] New: " jj at stusta dot net
2020-04-27 16:32 ` [Bug libbacktrace/66570] " abraxa@dar-clan.de
2020-04-27 17:20 ` ian at airs dot com
2020-04-27 17:49 ` abraxa@dar-clan.de [this message]
2020-04-27 20:27 ` ian at airs dot com

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=bug-66570-4-tABXX1X6D9@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).