public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: niXman <i.nixman@autistici.org>
Cc: Gcc Help <gcc-help@gcc.gnu.org>
Subject: Re: Extra import symbol in debug build
Date: Fri, 17 Feb 2023 15:30:52 +0000	[thread overview]
Message-ID: <CAH6eHdTe7kzVSyXfNvUFqtBXH0EP307t5Hk6eZN6vOJD=m80CQ@mail.gmail.com> (raw)
In-Reply-To: <d0973d2d1d4c7efd0c64cc80c59b9444@autistici.org>

[-- Attachment #1: Type: text/plain, Size: 811 bytes --]

On Fri, 17 Feb 2023, 14:59 , <i.nixman@autistici.org> wrote:

> On 2023-02-17 12:06, Jonathan Wakely wrote:
>
> >
> > That suggests either you built it wrong, or that library is from an
> > older
> > GCC, not the one you're compiling with.
>
> thank you Jonathan!
>
> will check this now.
>
>
> I have one more question.
>
> just now I rebuild the executable using `-static-libstdc++`, and I can
> confirm I can see that option in the linker cmdline, but the executable
> still depends on libstdc++.so.
> how can this be?
>

If you're linking to some shared library that depends on libstdc++.so then
your executable will depend on it.

I think this thread has gone in too long without any details of what
commands you're actually using to compile and link. There's only so much
people can tell you by guessing.

  parent reply	other threads:[~2023-02-17 15:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 15:23 i.nixman
2023-02-16 15:29 ` Jonathan Wakely
2023-02-16 18:39   ` i.nixman
2023-02-16 20:08     ` Jonathan Wakely
2023-02-17  8:51       ` i.nixman
2023-02-17 10:23         ` Xi Ruoyao
2023-02-17 11:31           ` i.nixman
2023-02-17 11:26         ` Jonathan Wakely
2023-02-17 11:32           ` i.nixman
2023-02-17 12:06             ` Jonathan Wakely
2023-02-17 14:59               ` i.nixman
2023-02-17 15:18                 ` i.nixman
2023-02-17 15:30                 ` Jonathan Wakely [this message]
2023-02-17 15:35                   ` i.nixman

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='CAH6eHdTe7kzVSyXfNvUFqtBXH0EP307t5Hk6eZN6vOJD=m80CQ@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=i.nixman@autistici.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).