From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Bug 919184 - sys-libs/libstdc++-v3-3.3.6-r4
Date: Mon, 09 Sep 2024 20:50:16 -0400 [thread overview]
Message-ID: <258f9b4c2ea7de400646c7119e490f1312420f10.camel@gentoo.org> (raw)
In-Reply-To: <CAP4tJZJK4P=urtSt87z-B=fqDjw2O+r8Gx5rQg16wHimdDkfzw@mail.gmail.com>
On Mon, 2024-09-09 at 21:33 -0300, João Matos wrote:
> Dear list,
>
> I'm trying to install the Checkpoint client for linux (cshell_install). It
> requires sys-libs/libstdc++-v3, 32 bits. I couldn't compile it and found
> this bug: https://bugs.gentoo.org/919184
TIL that we have a twenty-year-old libstdc++ in the tree.
> Do you know any way of work around this? Maybe copying the binary file from
> another distro or try to use another gcc version?
It's running a test program to find the glibc minor version:
#include <features.h>
main(argc, argv)
int argc;
char *argv[];
{
printf("%d\n", __GLIBC_MINOR__);
return 0;
}
But this test program, having been written 20+ years ago, is crap. It's
missing <stdio.h> and a correct signature for "main" at least. Newer
GCCs (like the one that you're using) will refuse to compile it. So the
test fails unexpectedly, and the build stops. You might be able to
trick it by disabling -Wimplicit-int, -Wimplicit-function-declaration,
and whatever other warnings that program raises... but then you have to
actually compile the rest of it with a new GCC. Good luck :)
next prev parent reply other threads:[~2024-09-10 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 0:33 [gentoo-user] Bug 919184 - sys-libs/libstdc++-v3-3.3.6-r4 João Matos
2024-09-10 0:50 ` Michael Orlitzky [this message]
2024-09-10 6:36 ` Filip Kobierski
2024-09-10 14:57 ` Eli Schwartz
[not found] ` <ed67d337034263d841e97d76c883d734@shitposting.expert>
[not found] ` <edc063bc721a6639fcd7ca1175e21815@shitposting.expert>
2024-09-10 12:17 ` Fwd: " Alexe Stefan
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=258f9b4c2ea7de400646c7119e490f1312420f10.camel@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-user@lists.gentoo.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