public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ilja Golshtein" <ilejn@yandex.ru>
To: gcc-help@gcc.gnu.org
Subject: gcc 3.2.2 @ FC4
Date: Wed, 09 Nov 2005 16:42:00 -0000	[thread overview]
Message-ID: <437226E4.000005.24276@ariel.yandex.ru> (raw)

Hello!

Is it possible to build gcc 3.2.2 on
Fedora Core 4 box?

I failed to achieve this goal by native 4.0.0 compiler
(not a big deal) and tried gcc 3.2.3 (compat-gcc32)
included in FC4 distro.

Build was successful, but not self test.
Make check produced

make[4]: Entering directory `./gcc-3.2.2-20030225_objdir/i686-pc-linux-gnu/boehm-gc'
Switched to incremental mode
Emulating dirty bits with mprotect/signals
/bin/sh: line 1:  4537 Segmentation fault      LD_LIBRARY_PATH=../../gcc $dir/$tst
FAIL: gctest
===================
1 of 1 tests failed

Questions.

Am I right thinking newly built gcc 3.2.2
requires shared libraries with old ABI
and incompatible with what I have in the distro?

Am I right thinking compat-gcc32 is very special
thing where old compiler is able to live
with new ABI?

Thanks a lot.

-- 
Best regards
Ilja Golshtein

                 reply	other threads:[~2005-11-09 16:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=437226E4.000005.24276@ariel.yandex.ru \
    --to=ilejn@yandex.ru \
    --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).