Re: RH9 and gcc version problem
From: tquan (tquanle_at_yahoo.com)
Date: 01/15/04
- Next message: Jens.Toerring_at_physik.fu-berlin.de: "Re: Unresolved symbol errors on upgrade Redhat 9 driver"
- Previous message: Robert Redelmeier: "Re: how to achieve microsecond granuality using setitimer"
- In reply to: Silviu Minut: "Re: RH9 and gcc version problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 15 Jan 2004 11:10:13 -0500
Silviu Minut wrote:
> On Wed, 07 Jan 2004 16:08:27 -0500, tquan wrote:
>
>
>>Hi,
>>
>> Not sure if this is the appropriate group to post this question so
>>please bare with me.
>>
>> I am running RH9.0 with the stock gcc compiler 3.2.2-5. Other related
>>libraries already upgraded are:
>> glibc-common-2.3.2-27.9.7
>> glibc-devel-2.3.2-27.9.7
>> glibc-2.3.2-27.9.7
>>
>> Now that I find out this gcc version (3.2.2-5) breaks some of my
>>programs, I would like to upgrade the compiler to 3.3.2 (current release
>>version). How do I go about it? Do I need to completely uninstall the
>>old compiler and install the new one, or is there a way to just upgrade
>>it? I already found out that upgrading it is not an easy task.
>>
>> Any advice is greatly appreciated here.
>> regards,
>> tquan.
>
>
> If you're code is not standard compatible, you probably want to
> downgrade the compiler, not upgrade it. gcc-3.3 won't make your
> code any more compatible, than 3.2. Obviously, the alternative is
> to upgrade the code, which is in fact not that hard, though it might
> take you a couple of days.
>
> I did change the compiler, and I did that from rpms. Try to
> install whatever compiler you want, say 2.9x, and it will complain
> about dependencies. The only one I had troubles with was libstdc++.
> Yes, some programs do depend on this library (not on the compiler
> itself), so you have to keep the libstdc++ you have, so for the
> new one you do
>
> rpmn -ivh libstdc++-new
>
> rather than Uvh. You can keep 2 versions of libstdc++ and they
> can coexist peacefully. Of course, you can do rpm --test for
> whatever you want to install, to make sure everything is ok.
>
> Off the top of my head, I think I needed
>
> cpp, gcc, gcc-c++, libgcc, libstdc++, libstdc++-devel.
>
>
>
Thank you all for helping me out on this. I think I owe you some
clafification on my posts:
- the code I am dealing with is a proprietary, legacy code and which I
don't have the right to modify, unfortunately. I was written by some guy
in Fortran and using automate conversion tool to convert it to c/c++.
It's rather ugly looking and real annoy to debug.
- You are right in that I need to downgrade my compiler rather than
upgrade. The thing is I never done any compiler downgrading nor
upgrading and I am scared as hell as dependencies go. Would you clarify
if installing 2 diff. versions of glibc is OK for my system?
Again, thanks alot for all you folks' help. I will try them all out and
let you know.
regards,
tquan.
- Next message: Jens.Toerring_at_physik.fu-berlin.de: "Re: Unresolved symbol errors on upgrade Redhat 9 driver"
- Previous message: Robert Redelmeier: "Re: how to achieve microsecond granuality using setitimer"
- In reply to: Silviu Minut: "Re: RH9 and gcc version problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
