public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexe Stefan <stefanalexe48@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Fwd: Re: [gentoo-user] Bug 919184 - sys-libs/libstdc++-v3-3.3.6-r4
Date: Tue, 10 Sep 2024 15:17:38 +0300	[thread overview]
Message-ID: <CAENw6g7tys=98Tf7trff0cmAa262VsTDi3osjPrKJa4Lmt1-1g@mail.gmail.com> (raw)
In-Reply-To: <edc063bc721a6639fcd7ca1175e21815@shitposting.expert>

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

Resending from a different email, as I got an error sending on my main
email.

---------- Forwarded message ---------
De la: stefan11111 <stefan11111@shitposting.expert>
Date: mar., 10 sept. 2024, 15:13
Subject: Fwd: Re: [gentoo-user] Bug 919184 - sys-libs/libstdc++-v3-3.3.6-r4
To: Stefanalexe48 <stefanalexe48@gmail.com>




-------- Original Message --------
Subject: Re: [gentoo-user] Bug 919184 - sys-libs/libstdc++-v3-3.3.6-r4
Date: 2024-09-10 11:59
 From: stefan11111 <stefan11111@shitposting.expert>
To: gentoo-user@lists.gentoo.org

On 2024-09-10 00:33, 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
>
> Do you know any way of work around this? Maybe copying the binary file
> from
> another distro or try to use another gcc version?
>
> Thank you,
Hi.
I don't know if you tried, but passing -fpermissive via /etc/portage/env
is not enough.
You need to write wrapper scripts to get around the gcc14 issue.

> $ cat /usr/bin/cc
> #!/bin/sh
>
> exec cc.real -fpermissive "$@"
>
> $ cat /usr/bin/gcc
> #!/bin/sh
>
> exec gcc.real -fpermissive "$@"
>
> $ cat /usr/bin/x86_64-pc-linux-gnu-cc
> #!/bin/sh
>
> exec x86_64-pc-linux-gnu-cc.real -fpermissive "$@"
>
> $ cat /usr/bin/x86_64-pc-linux-gnu-gcc
> #!/bin/sh
>
> exec x86_64-pc-linux-gnu-gcc.real -fpermissive "$@"
>

where the original files were moved to the .real files.

-- 
Linux-gentoo-x86_64-Intel-R-_Core-TM-_i5-7400_CPU_@_3.00GHz

COMMON_FLAGS="-O3 -pipe -march=native -fno-stack-protector
-ftree-vectorize -ffast-math -funswitch-loops -fuse-linker-plugin -flto
-fdevirtualize-at-ltrans -fno-plt -fno-semantic-interposition
-falign-functions=64 -fgraphite-identity -floop-nest-optimize"

USE="-* git verify-sig rsync-verify man alsa X grub ssl ipv6 lto
libressl olde-gentoo asm native-symlinks threads jit jumbo-build minimal
strip system-man"

INSTALL_MASK="/etc/systemd /lib/systemd /usr/lib/systemd
/usr/lib/modules-load.d /usr/lib/tmpfiles.d *tmpfiles* /var/lib/dbus
/lib/udev /usr/share/icons /usr/share/applications
/usr/share/gtk-3.0/emoji"

[-- Attachment #2: Type: text/html, Size: 3183 bytes --]

      parent reply	other threads:[~2024-09-10 12:17 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
2024-09-10 14:57   ` Eli Schwartz
     [not found] ` <ed67d337034263d841e97d76c883d734@shitposting.expert>
     [not found]   ` <edc063bc721a6639fcd7ca1175e21815@shitposting.expert>
2024-09-10 12:17     ` Alexe Stefan [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='CAENw6g7tys=98Tf7trff0cmAa262VsTDi3osjPrKJa4Lmt1-1g@mail.gmail.com' \
    --to=stefanalexe48@gmail.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