From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24223 invoked by alias); 12 Dec 2007 14:18:08 -0000 Received: (qmail 24214 invoked by uid 22791); 12 Dec 2007 14:18:07 -0000 X-Spam-Check-By: sourceware.org Received: from smtp116.sbc.mail.sp1.yahoo.com (HELO smtp116.sbc.mail.sp1.yahoo.com) (69.147.64.89) by sourceware.org (qpsmtpd/0.31) with SMTP; Wed, 12 Dec 2007 14:18:01 +0000 Received: (qmail 89199 invoked from network); 12 Dec 2007 14:17:58 -0000 Received: from unknown (HELO ?69.105.73.42?) (timothyprince@sbcglobal.net@69.105.73.42 with plain) by smtp116.sbc.mail.sp1.yahoo.com with SMTP; 12 Dec 2007 14:17:57 -0000 X-YMail-OSG: x2e_cP8VM1kVG_bwyb0noxTdFuiiWbwLcZTVe5xIsPI35ctVVIZyNH0xsCnc9qoURr7pX0fHZQ-- Message-ID: <475FEB57.5000703@computer.org> Date: Wed, 12 Dec 2007 14:18:00 -0000 From: Tim Prince User-Agent: Thunderbird 2.0.0.4 (X11/20070613) MIME-Version: 1.0 To: satyaakam goswami CC: gcc-help@gcc.gnu.org Subject: Re: mixing objects of gcc 3.2.3 and gcc 4.1.2 References: <6491e1350712120442i408714abj98c59cc3321f78bd@mail.gmail.com> In-Reply-To: <6491e1350712120442i408714abj98c59cc3321f78bd@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg00244.txt.bz2 satyaakam goswami wrote: > 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. You may need attention to glibc header and libraries as well. If there are no changes in those header files, you should be OK.