public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: 조안나 <opehn0@gmail.com>
To: libstdc++@gcc.gnu.org
Subject: What is the lowest version of glibc I can use to build gcc 4.8.3 and libstdc++?
Date: Thu, 5 Oct 2023 11:52:37 +0900	[thread overview]
Message-ID: <CAEh9iZMqXYf+x1Ob9yLe9R+6Yy1Y7hXM22aJB82bT4wvVNY9pA@mail.gmail.com> (raw)

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

Situation:
I am attempting to migrate legacy C programs to C++11
For use in older distributions, I static link libstdc++ through the
-static-libstdc++ option
C++11 is supported after version 4.8.3 of gcc, So I built it on CentOS7
where gcc 4.8.5 installed.

Result showed a dependence on glibc and was only available in distributions
with glibc14 and later versions installed.
The required version felt a little high because many customers use old
distribution.
I came up with the idea of building libstdc++ myself using a lower version
of glibc to reduce dependency.

First I tried using glibc 2.5 for gcc 4.8.3
Same, I built it on CentOS7 where gcc 4.8.5 and glibc 2.17 installed.
But failed with the error below:
configure: error: unsupported system, cannot find sizeof (omp_lock_t)

I think I lowered the glibc too much, but I couldn't find a document about
compatibility between gcc or libstdc++ and glibc.
What is the lowest version of glibc I can use to build gcc 4.8.3 and
libstdc++?
Can somebody help?

             reply	other threads:[~2023-10-05  2:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  2:52 조안나 [this message]
2023-10-05  6:53 ` Jonathan Wakely
2023-10-05  8:32   ` Jonathan Wakely

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=CAEh9iZMqXYf+x1Ob9yLe9R+6Yy1Y7hXM22aJB82bT4wvVNY9pA@mail.gmail.com \
    --to=opehn0@gmail.com \
    --cc=libstdc++@gcc.gnu.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).