Riad KACED wrote, on 04/22/08 00:45:
> Hi Ahmad,
>
> I've had a similar problem couple of years ago when moved a machine
> from RH 7.2 to RH Entreprise Linux 3.0.
> I think this was because the Redhat Version (kernel version) I was
> using was not sup****ted by Cadence and the solution to make working at
> this time is to set an env variable called LD_ASSUME_KERNEL to 2.4.1
>
> So my first advice is to follow the same, it may help.
> So before running Cadence, set up your Unix environment by adding :
> CSH> setenv LD_ASSUME_KERNEL 2.4.1
> or
> SH> LD_ASSUME_KERNEL="2.4.1" ; ex****t LD_ASSUME_KERNEL
>
> You can get your kernel version by using the following unix command :
> UNIX> uname -r
> ==> 2.6.22.5-31-default (In my linux box). I would have tried
> LD_ASSUME_KERNEL="2.6.2" in my case. Well give it a try and see how it
> goes.
>
> I'm very happy for you if this fixes your problem otherwise you need
> more inverstigation and it's worth involve your Cadence sup****t for
> it.
>
> Anyway, I don't really like this LD_ASSUME_KERNEL and I'm seeing it
> set by default almost everywhere.
> You have to know that this variable has been introduced a while back
> when Linux was changing threading models. Those new models have broken
> many applications like Java.This env variable have been introduced
> then to get back the the old threading behavior. This was ages ago
> when transition was needed but thinks are ine now.Setting
> LD_ASSUME_KERNEL could be harmful for certain applications today. Just
> Google it if you want to read more about this.
>
> What is your opinion Guys ?
>
> Riad.
These days you don't really need to set LD_ASSUME_KERNEL most of the time.
The
particular error message could either be ignored, or in fact in more
recent
versions doesn't happen any more.
LD_ASSUME_KERNEL on RHEL5 (which I'm using, for various reasons, discussed
in an
earlier post - even though it's not fully "sup****ted" for all releases)
breaks
pretty much everything (even "ls"), so I tend not to use it.
Regards,
Andrew.
|
