From: Xi Ruoyao <xry111@xry111.site>
To: Kai Ruottu <kai.ruottu@wippies.com>,
Dingjun Chen <Dingjun.Chen@geotechairborne.com>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: How to fix these errors with glibc 2.37?
Date: Wed, 11 Oct 2023 21:46:28 +0800 [thread overview]
Message-ID: <c7cc7e2f5d954ef7aca37e3b6c53a5cc571a3f5c.camel@xry111.site> (raw)
In-Reply-To: <2dd446fb-8fbc-b899-a42c-b00d198b9607@wippies.com>
On Wed, 2023-10-11 at 16:36 +0300, Kai Ruottu wrote:
> Dingjun Chen kirjoitti 11.10.2023 klo 15.20:
> > Hi, guys,
> >
> > I want to install glibc 2.37 for 32-bit applications.
> Is this unrelated to your goal to produce a crosscompiler for the
> "RTD single board computer with Linux 2.4.36.1 2009, i686"?
>
> If not, why you are trying to produce a new glibc from scratch?
> Doesn't the RTD Linux system already have its own glibc-<something>,
> prebuilt and "acid tested"? If it has, why you don't want to use it in
> the crosscompiler as the target C library?
FWIW it's impossible to run Glibc-2.37 on Linux 2.4.36.1. As I've said
in a previous reply, Glibc-2.37 requires Linux 3.2 or later.
Anyway this is off-topic. gcc-help is not a support channel of Glibc.
We often try to help even if the post is off-topic, but now to me we are
just encouraging off-topic posts. PITA.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2023-10-11 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 12:20 Dingjun Chen
2023-10-11 13:36 ` Kai Ruottu
2023-10-11 13:46 ` Xi Ruoyao [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=c7cc7e2f5d954ef7aca37e3b6c53a5cc571a3f5c.camel@xry111.site \
--to=xry111@xry111.site \
--cc=Dingjun.Chen@geotechairborne.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kai.ruottu@wippies.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).