On Dec 12, 2007 6:52 PM, ??? <longhaitao@xxxxxxxxxxx> 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)? > well,err... > i confused by what you said. > do you mean all the .o files built by 4.1.2? > but your mail title said some of the .o files were built by gcc 3.2.3, > others compiled by 4.1.2. > > if some by 3.2.3 and others by 4.1.2, i do not think it is easy to > combine them togther.it concerns about the c++ abi. > > maybe this URL is useful: > http://gcc.gnu.org/onlinedocs/libstdc++/abi.html > > just suggestions, i am new about gcc, so if i made any stupid mistakes, > i apologize in advance. > > > 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 > Yes thats a mistake in subject we will be using 4.1.2 in both the cases RHEL 3.0 as well as RHEL 4.0. regards Satya
