public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Helmut Zeisel <HZ2012@gmx.at>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC 12.1 and C++23 <stacktrace>
Date: Thu, 28 Jul 2022 20:42:09 +0100	[thread overview]
Message-ID: <CAH6eHdTKZ9d-Tk3U7-L045YZbbUKLVLVCyJTK-XiAM5yfk0HPg@mail.gmail.com> (raw)
In-Reply-To: <trinity-fb7d82d7-4642-4961-ac90-180ec4cec0e2-1659033153765@3c-app-gmx-bap18>

On Thu, 28 Jul 2022 at 19:33, Helmut Zeisel via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> I tried to use C++23 <stacktrace> with GCC 12.1.
> I configured GCC 12.1 with
>
>  --enable-libstdcxx-backtrace=yes
>
> built, and installed.
> I built my test program with
>
> -std=c++23 -lstd++_libacktrace
>
> (cf. https://stackoverflow.com/questions/72341483/how-can-i-generate-a-c23-stacktrace-with-gcc-12-1 )
>
> but get the error message
>
> /usr/bin/ld: cannot find -lstd++_libacktrace: No such file or directory

You spelled it wrong. It's stdc++ not std++


>
> Do I need other or additional options? Where can I check whether libstd++_libacktrace was really built?
>
> Thank you,
>
> Helmut
>

      reply	other threads:[~2022-07-28 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 18:32 Helmut Zeisel
2022-07-28 19:42 ` Jonathan Wakely [this message]

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=CAH6eHdTKZ9d-Tk3U7-L045YZbbUKLVLVCyJTK-XiAM5yfk0HPg@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=HZ2012@gmx.at \
    --cc=gcc-help@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).