public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "Горбешко Богдан" <bodqhrohro@gmail.com>
To: "Florian Weimer" <fweimer@redhat.com>,
	"Горбешко Богдан via Libc-help" <libc-help@sourceware.org>
Subject: Re: libstdc++ link errors in support/links-dso-program
Date: Fri, 15 Mar 2024 13:51:54 +0200	[thread overview]
Message-ID: <ba1b17e9-7f80-4f34-b092-60428bb4e3c4@gmail.com> (raw)
In-Reply-To: <87msr0hs3n.fsf@oldenburg.str.redhat.com>

I'm not going to install it system-wide, just to build it for 
cross-compiling a Golang project for a Debian Buster system, by 
specifying -rpath and --dynamic-linker.

On 15/03/2024 09:27, Florian Weimer wrote:
> * Горбешко Богдан via Libc-help:
>
>> Is that because it attempts to link against the system libstdc++,
>> which is too new and requires symbols not present in this glibc
>> version? Do I need to compile it myself? Or maybe even the whole GCC?
> Going back before 2.34 if the distribution is on 2.34 or later is not
> really possible.  You need to build a whole cross-toolchain environment.
> It's easier to build on an older version of the distribution?
>
> Why do you need to go back 2.31?  What kind of problem are you trying to
> solve?
>
> Thanks,
> Florian
>


  reply	other threads:[~2024-03-15 11:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  3:09 Горбешко Богдан
2024-03-15  7:27 ` Florian Weimer
2024-03-15 11:51   ` Горбешко Богдан [this message]
2024-03-15 17:07     ` Florian Weimer
2024-03-15 19:22       ` Горбешко Богдан
2024-04-10 12:03         ` Florian Weimer
2024-04-10 12:50           ` Горбешко Богдан
2024-04-10 13:22             ` Konstantin Kharlamov
2024-04-10 13:30               ` Горбешко Богдан
2024-04-10 13:55                 ` Konstantin Kharlamov
2024-04-10 14:02                   ` Горбешко Богдан
2024-04-10 14:11                     ` Konstantin Kharlamov
2024-04-10 14:24                       ` Горбешко Богдан

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=ba1b17e9-7f80-4f34-b092-60428bb4e3c4@gmail.com \
    --to=bodqhrohro@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-help@sourceware.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).