public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Filip Kobierski <kobierski.filip@protonmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Bug 919184 - sys-libs/libstdc++-v3-3.3.6-r4
Date: Tue, 10 Sep 2024 06:36:23 +0000	[thread overview]
Message-ID: <XoEhZxAa8zNSsqv-9sYanYcMEWRaRJ5_kUECRTDnTeP9uUf0m_vKzNT551z3hBiQlCYFqRQcO9YTNTzE5gqWsRgQx9GxX8UEzQupf1ST6uw=@protonmail.com> (raw)
In-Reply-To: <258f9b4c2ea7de400646c7119e490f1312420f10.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1568 bytes --]

>  TIL that we have a twenty-year-old libstdc++ in the tree.

Maybe we should mask it?
It is supossed to work with gcc <3.4 and the oldest we have is 8.5.0, which is masked already.


-------- Original Message --------
On 9/10/24 02:50, Michael Orlitzky <mjo@gentoo.org> wrote:

>  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 :)
>  
>  
>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]

  reply	other threads:[~2024-09-10  6:36 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
2024-09-10  6:36   ` Filip Kobierski [this message]
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='XoEhZxAa8zNSsqv-9sYanYcMEWRaRJ5_kUECRTDnTeP9uUf0m_vKzNT551z3hBiQlCYFqRQcO9YTNTzE5gqWsRgQx9GxX8UEzQupf1ST6uw=@protonmail.com' \
    --to=kobierski.filip@protonmail.com \
    --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