public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Ruottu <kai.ruottu@wippies.com>
To: "Patel,
	Kiran D. (GSFC-699.0)[GLOBAL SCIENCE & TECHNOLOGY INC]"
	<kiran.d.patel@nasa.gov>,
	"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Has to install gcc-3.4.6 under Centos 7
Date: Sat, 12 Oct 2019 14:02:00 -0000	[thread overview]
Message-ID: <ff473324-fb62-8cd2-ac41-8396b1b44056@wippies.com> (raw)
In-Reply-To: <87C9E151-A8D1-4ADB-9DFA-2793E59090DF@nasa.gov>

Patel, Kiran D. (GSFC-699.0)[GLOBAL SCIENCE & TECHNOLOGY INC] via 
gcc-help kirjoitti 12.10.2019 klo 16.14:
> I tried to fix the compilation issue with gcc3.4.6.


Why you want gcc-3.4.6 to be used with the CentOS 7 native C libraries ? 
(Some quite new glibc there)  The produced native toolchain
would produce executables which as default would only work on CentOS 7 
and newer than that releases. Not on CentOS 6, 5, 4, 3, 2, 1,
on old Fedora releases or RedHat releases...

One sane goal would be to get a toolchain on CentOS 7 which produces 
executables for some older CentOS (or something else) release
which had gcc-3.4.6 as its original native GCC or as a self-made updated 
native GCC. That using some old glibc as its native
C library.  This goal meaning producing a crosstoolchain to the old 
Linux release (building binutils and GCC to use the old
glibc as prebuilt in a $sysroot)

      reply	other threads:[~2019-10-12 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 13:14 Patel, Kiran D. (GSFC-699.0)[GLOBAL SCIENCE & TECHNOLOGY INC] via gcc-help
2019-10-12 14:02 ` Kai Ruottu [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=ff473324-fb62-8cd2-ac41-8396b1b44056@wippies.com \
    --to=kai.ruottu@wippies.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=kiran.d.patel@nasa.gov \
    /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).