"if: Expression syntax" when trying to load 64-bit version o

[DL]

I'm running RedHat Enterprise 4 (64-bit version) and I have downloaded
and installed IC5141 with the 64-bit version of dfII. Whenever I try to
run cadence I get an "if: Expression syntax" error and Library Manager
won't start up. I tried to do LD_ASSUME_KERNEL but doesn't work.

Any ideas?

 

[Bernd Fischer]

We have these tree vars set in RHEL 3.0, maybe one of them
helps, I assume it could be the DD_DONT_DO_OS_LOCKS

setenv DD_DONT_DO_OS_LOCKS set
setenv LANG ""
setenv LD_ASSUME_KERNEL 2.4.1


DL wrote:

I'm running RedHat Enterprise 4 (64-bit version) and I have downloaded
and installed IC5141 with the 64-bit version of dfII. Whenever I try to
run cadence I get an "if: Expression syntax" error and Library Manager
won't start up. I tried to do LD_ASSUME_KERNEL but doesn't work.

Any ideas?

 

[Graeme Bunyan]

DL wrote:

I'm running RedHat Enterprise 4 (64-bit version) and I have downloaded
and installed IC5141 with the 64-bit version of dfII. Whenever I try to
run cadence I get an "if: Expression syntax" error and Library Manager
won't start up. I tried to do LD_ASSUME_KERNEL but doesn't work.

Any ideas?

Hi,

I'm not sure specifically which exe you're trying to run, but it sounds like
there is a problem with the wrapper script which sets up the path and library
path. The structure of the scripts/exes is usually a little something like this:

tools/dfII/bin/<app> - sh wrapper script
tools/dfII/bin/<app>.exe - exe which decides to run 32-bit or 64-bit exe
tools/dfII/bin/32bit/<app>.exe - actual 32-bit exe
tools/dfII/bin/64bit/<app>.exe - actual 64-bit exe

The error you are describing sounds like it may be relying on an environment
variable which is not set. It shouldn't fall over if this is the case,
however... :-(

Can you please try to run:

sh -xv `which <app>`

(Assuming it's an sh wrapper, and they usually are - it should have the shell
name in the first line of the file if that doesn't work).

That just turns on verbose and echo mode so you'll get a pretty clear
indication where the problem is in the script. What to do depends on the
problem - hopefully it's not a syntax error and you won't need to edit the
script. It may be that you need to set an environment variable to some dummy,
non-blank value in order for that part of the script to work.

I'd be interested to know what the problem is - please let me know if you
figure it out.

Regards,
Graeme.

 

[Andrew Beckett]

On Mon, 25 Jul 2005 15:29:45 +0100, Graeme Bunyan
<graemeb@dontlikespam.cadence.com> wrote:

DL wrote:
I'm running RedHat Enterprise 4 (64-bit version) and I have downloaded
and installed IC5141 with the 64-bit version of dfII. Whenever I try to
run cadence I get an "if: Expression syntax" error and Library Manager
won't start up. I tried to do LD_ASSUME_KERNEL but doesn't work.

Any ideas?


Hi,

I'm not sure specifically which exe you're trying to run, but it sounds like
there is a problem with the wrapper script which sets up the path and library
path. The structure of the scripts/exes is usually a little something like this:

tools/dfII/bin/<app> - sh wrapper script
tools/dfII/bin/<app>.exe - exe which decides to run 32-bit or 64-bit exe
tools/dfII/bin/32bit/<app>.exe - actual 32-bit exe
tools/dfII/bin/64bit/<app>.exe - actual 64-bit exe

The error you are describing sounds like it may be relying on an environment
variable which is not set. It shouldn't fall over if this is the case,
however... :-(

Can you please try to run:

sh -xv `which <app>`

(Assuming it's an sh wrapper, and they usually are - it should have the shell
name in the first line of the file if that doesn't work).

That just turns on verbose and echo mode so you'll get a pretty clear
indication where the problem is in the script. What to do depends on the
problem - hopefully it's not a syntax error and you won't need to edit the
script. It may be that you need to set an environment variable to some dummy,
non-blank value in order for that part of the script to work.

I'd be interested to know what the problem is - please let me know if you
figure it out.

Regards,
Graeme.

I certainly have not seen this problem before - I'm guessing that the most
likely explanation is that "cadence" is being started via some non-Cadence
wrapper script which has the problem. But I'm prepared to be surprised - but it
would be useful to know what exactly the command being invoked was, and to do
the experiment that Graeme suggested.

Regards,

Andrew.