public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: i.nixman@autistici.org, Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Gcc Help <gcc-help@gcc.gnu.org>
Subject: Re: Extra import symbol in debug build
Date: Fri, 17 Feb 2023 18:23:35 +0800	[thread overview]
Message-ID: <fe6857f369a22cd7d9efd1f2fc0905cbd41fd401.camel@xry111.site> (raw)
In-Reply-To: <1fa9b2598357629dfaac5debd53708b3@autistici.org>

On Fri, 2023-02-17 at 08:51 +0000, i.nixman--- via Gcc-help wrote:

> 1. will the problem be solved by "pushing" a debug version of libstdc++ 
> on the remote machine?

Yes if you set LD_LIBRARY_PATH or something correctly.  But
-static-libstdc++ is easier.

> 2. how can I define this symbol in the project code for debug build to
> avoid having to use the debug version of libstdc++?
> something like this? :
> namespace std {
>     template basic_ios<char, char_traits<char> >::operator bool() const;
> }

You can't.  Defining anything in std namespace is undefined behavior.


-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-02-17 10:23 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 [this message]
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
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=fe6857f369a22cd7d9efd1f2fc0905cbd41fd401.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=gcc-help@gcc.gnu.org \
    --cc=i.nixman@autistici.org \
    --cc=jwakely.gcc@gmail.com \
    /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).