public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: alexandre schenberg <ale.schenberg@yandex.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re:Can't I build gcc with multilib support?
Date: Fri, 23 Sep 2022 22:03:22 -0300	[thread overview]
Message-ID: <498751663981402@m5q2bgqovkelfrov.myt.yp-c.yandex.net> (raw)
In-Reply-To: <CAH6eHdTZTjGkHY9ae3ax=5c6XiTwX2XFUy-8HffSwOL_MYdoKg@mail.gmail.com>

Yes, I am trying to build 4.9.4, again. I built it first with multilib support (probably with the help of 32bit libraries installed through the package manager).

However when I try to run any c++ 32bit program (c programs works fine), it ends with segmentation fault. I believe that is due to a conflict  between the 4.9.4 gcc/g++ and libstdc++.so.6.0.20 with the old libraries from gcc 4.4.3 on /usr/lib/...

Finally, I am not sure that only reinstall gcc 4.4.3 would solve it. Reinstall ia32 libs might do it, but first I have a few things to try.

To check Gcc configure.ac and look for the above error messages. Plus, I might created a backup copy of /usr/lib/gcc/x86_64-linux-gnu/4.4.3/ and replace it with /usr/lib/gcc/x86_64-linux-gnu/4.9.4. If that works, I won't even need to do a system wide 4.9.4 install, neither reinstall anything from the package manager (that I would have to uninstall again latter)

  reply	other threads:[~2022-09-24  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  1:35 Can't " alexandre schenberg
2022-09-23  9:35 ` Jonathan Wakely
2022-09-24  1:03   ` alexandre schenberg [this message]
2022-09-24 10:18     ` Jonathan Wakely
2022-09-24 10:19       ` 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=498751663981402@m5q2bgqovkelfrov.myt.yp-c.yandex.net \
    --to=ale.schenberg@yandex.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.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).