public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "Горбешко Богдан" <bodqhrohro@gmail.com>
To: Konstantin Kharlamov <Hi-Angel@yandex.ru>,
	Florian Weimer <fweimer@redhat.com>
Cc: "Горбешко Богдан via Libc-help" <libc-help@sourceware.org>
Subject: Re: libstdc++ link errors in support/links-dso-program
Date: Wed, 10 Apr 2024 17:24:22 +0300	[thread overview]
Message-ID: <61fba148-f3aa-4c09-966e-d399cfa32428@gmail.com> (raw)
In-Reply-To: <9385e4b49369793819d44de2e6c5e0658b1c4208.camel@yandex.ru>

On 10/04/2024 17:11, Konstantin Kharlamov wrote:
> On Wed, 2024-04-10 at 17:02 +0300, Горбешко Богдан wrote:
>> It's not a CI and I don't need a patched Glibc actually.
> Ah, sorry, "continuous rebuilds" sentence threw me off, so I thought
> it's about CI 😄
>
>> I mentioned already that I'm just cross-compiling a Golang project to
>> be
>> run and tested during development frequently on an older
>> distribution.
> Okay. I still don't get the whole picture, but as you mentioned that
> you've added lots of bind-mounts, etc, to minimize the redundancy,
> hopefully that part is solved 😊
Technically: yes, to some tolerable level. Though I'd still like to know 
if it's still possible to cross-compile for older Glibc with Glibc ≥2.34 
on the host system. Seems like the changes are too breaking there, so 
others forfeit too: 
https://github.com/wheybags/glibc_version_header/issues/32#issuecomment-1826368565

      reply	other threads:[~2024-04-10 14:24 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   ` Горбешко Богдан
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                       ` Горбешко Богдан [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=61fba148-f3aa-4c09-966e-d399cfa32428@gmail.com \
    --to=bodqhrohro@gmail.com \
    --cc=Hi-Angel@yandex.ru \
    --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).