public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "satyaakam goswami" <satyaakam@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Mixing obejects Built on RHEL 3.0 and RHEL 4.0 using same gcc4.1.2
Date: Tue, 08 Jan 2008 19:32:00 -0000	[thread overview]
Message-ID: <6491e1350801080134u48a4b817g5ea7fe7320acb91b@mail.gmail.com> (raw)

Hi,
      We are using gcc 4.1.2 remotely on our RHEL 3.0 OS to build our
current releases and plan to move our base OS to RHEL 4.0 on 2008. We
will
continue to use the same version of gcc 4.1.2 from the remote
location.  Since not all products will move at the same pace, can we
use the  object code built on RHEL 3.0 to link with the object code
build on  RHEL 4.0 (both built by gcc 4.1.2)? We have both C and C++
source code  and we will always do the link step on RHEL 4.0. Also we
use the libgcc_s.so.1, libstdc++.so.6, etc. from our own gcc 4.1.2
hierarchy at run-time.)

regards
Satya

                 reply	other threads:[~2008-01-08  9:35 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=6491e1350801080134u48a4b817g5ea7fe7320acb91b@mail.gmail.com \
    --to=satyaakam@gmail.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).