public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: alexandre schenberg <ale.schenberg@yandex.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Can't I build gcc with multilib support?
Date: Sat, 24 Sep 2022 11:19:29 +0100	[thread overview]
Message-ID: <CAH6eHdSCkks2G3W-O63S_eA9KNLR-cWcurZKc8fH455q2eFfFQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdTcPQEgqNPNhKBpwuDNv=Hhk=G7L2uLdm1nv387UjxYWA@mail.gmail.com>

On Sat, 24 Sept 2022 at 11:18, Jonathan Wakely wrote:
> If you won't do that, I would figure out why the libraries in /usr/libx86_64-linux-gnu/4.4.3 are even being considered by the linker. That's not a standard system path, so GCC 4.9.4 should not be looking in there.
>
> Compile with -v and -Wl,v -Wl,t to see wht paths are being passed to the linker, and which files the linker is looking at. Try that when compiling a C program, and when compiling a C++ program. Check that the 'gcc' nd 'g++' binaries are consistent. It sounds to me like you might have created some kind of hybrid of GCC 4.4.2 and 4.9.4!


And if none of that works, show us **exactly** the configure command
you're using, and the output of 'gcc -v' for all existing GCC
installations on the system, so we can see what's actually happening.
It's hard to debug it from your descriptions so far.

      reply	other threads:[~2022-09-24 10:19 UTC|newest]

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