SOC41USR4 (lnx86) install bug? (wroute 32-bit only!)

N

nonoe

Guest
I recently downloaded SOC41USR4 from Cadence's ESD site.
After installing it on our server, I found that the
UltraRoute program ("wroute 2.4.44") no longer runs in
64-bit mode.

The previous wroute 2.4.43 (which came with soc41usr3)
obeys the environment variable "$CDS_AUTO_64BIT" This
means I could select whether I wanted to run the 32-bit
or 64-bit exe of wroute. But the wroute 2.4.44 launcher
always runs in 32-bit mode, regardless of $CDS_AUTO_64BIT.
I've found that I can manually create a UNIX-link to the
tools.lnx86/fe/bin/64bit/wroute program-exe, but why should
I have to do that?

For now, I've copied the wroute shell-script from
soc41usr3 into our soc41usr4 (tools.lnx86/fe/bin/wroute)
installation-tree. The shell-script is just a bootloader
to detect the user's O/S platform, and this older-script
seems to work just fine with 2.4.44 (and obeys the
$CDS_AUTO_64BIT var, too!)

Anyway, was my soc41usr4 installation damaged, or is this a new
wroute "feature"? Our EDA-environment is primarily Solaris 8,
so the management grudgingly let us put a single Athlon/64
machine in the compute-pool. (But they refused to pay for
Redhat EL 3 when one of the engineers accidentally told them
about the free whiteboxlinux.org clone, so the Athlon/64
box is running WhiteBoxLinux 3.0 Respin 1.)
 
This looks like a bug:

andrewb_38> setenv CDS_AUTO_64BIT ALL
andrewb_39> wroute -debug3264
-------- 32/64 bit wrapper diagnostics -------------
App name: wroute
App path: /cds/lnx86/SOC41_usr4/tools/bin/../fe/bin
OS is 32-bit capable.
The user has selected 64-bit operation via the environment variables.
A 64-bit version of the application exists.
A 32-bit version of the application exists.

Note it is saying that the OS is 32 bit capable, when I'm running this on
an Opteron machine. There has been a change in USR4 to use the common
32/64 wrapper executable, rather than an SOC-specific script.

The same common wrapper that is used with other tools (e.g. layout
from the IC stream):

-------- 32/64 bit wrapper diagnostics -------------
App name: layout.exe
App path: /cds/lnx86/IC5141_hot/tools/dfII/bin
OS is 64-bit capable.
The user has selected 64-bit operation via the environment variables.
A 64-bit version of the application exists.
A 32-bit version of the application exists.

I'll raise this with one of my colleagues who looks after Encounter.

Andrew.

On Thu, 03 Mar 2005 05:50:47 GMT, "nonoe" <nonoe@none.none> wrote:

I recently downloaded SOC41USR4 from Cadence's ESD site.
After installing it on our server, I found that the
UltraRoute program ("wroute 2.4.44") no longer runs in
64-bit mode.

The previous wroute 2.4.43 (which came with soc41usr3)
obeys the environment variable "$CDS_AUTO_64BIT" This
means I could select whether I wanted to run the 32-bit
or 64-bit exe of wroute. But the wroute 2.4.44 launcher
always runs in 32-bit mode, regardless of $CDS_AUTO_64BIT.
I've found that I can manually create a UNIX-link to the
tools.lnx86/fe/bin/64bit/wroute program-exe, but why should
I have to do that?

For now, I've copied the wroute shell-script from
soc41usr3 into our soc41usr4 (tools.lnx86/fe/bin/wroute)
installation-tree. The shell-script is just a bootloader
to detect the user's O/S platform, and this older-script
seems to work just fine with 2.4.44 (and obeys the
$CDS_AUTO_64BIT var, too!)

Anyway, was my soc41usr4 installation damaged, or is this a new
wroute "feature"? Our EDA-environment is primarily Solaris 8,
so the management grudgingly let us put a single Athlon/64
machine in the compute-pool. (But they refused to pay for
Redhat EL 3 when one of the engineers accidentally told them
about the free whiteboxlinux.org clone, so the Athlon/64
box is running WhiteBoxLinux 3.0 Respin 1.)
Click to expand...
 
On Fri, 04 Mar 2005 06:30:52 +0000, Andrew Beckett
<andrewb@DcEaLdEeTnEcTe.HcIoSm> wrote:

This looks like a bug:

andrewb_38> setenv CDS_AUTO_64BIT ALL
andrewb_39> wroute -debug3264
-------- 32/64 bit wrapper diagnostics -------------
App name: wroute
App path: /cds/lnx86/SOC41_usr4/tools/bin/../fe/bin
OS is 32-bit capable.
The user has selected 64-bit operation via the environment variables.
A 64-bit version of the application exists.
A 32-bit version of the application exists.

Note it is saying that the OS is 32 bit capable, when I'm running this on
an Opteron machine. There has been a change in USR4 to use the common
32/64 wrapper executable, rather than an SOC-specific script.

The same common wrapper that is used with other tools (e.g. layout
from the IC stream):

-------- 32/64 bit wrapper diagnostics -------------
App name: layout.exe
App path: /cds/lnx86/IC5141_hot/tools/dfII/bin
OS is 64-bit capable.
The user has selected 64-bit operation via the environment variables.
A 64-bit version of the application exists.
A 32-bit version of the application exists.

I'll raise this with one of my colleagues who looks after Encounter.

Andrew.
Click to expand...
Note, if I copy the 32/64 wrapper from (say) the "layout.exe" in
<ic5141isrInstDir>/tools/dfII/bin/layout.exe to replace the "wroute"
in <socusr4InstDir>/tools/fe/bin - it then works OK.

So it does seem that there is a broken wrapper for wroute (and sroute
actually) in the SOC41 USR4 build (note, I used the layout.exe from
the latest ISR, 5.1.41.500.1.12).

I've reported this to my colleague in the ICD team. We'll get a PCR
filed for this.

Andrew.
 
On Fri, 04 Mar 2005 08:48:30 +0000, Andrew Beckett
I've reported this to my colleague in the ICD team. We'll get a PCR
filed for this.

Andrew.
Click to expand...
PCR 783283 was filed for this today.

Andrew.
 
On Fri, 04 Mar 2005 19:19:18 +0000, Andrew Beckett
<andrewb@DcEaLdEeTnEcTe.HcIoSm> wrote:

On Fri, 04 Mar 2005 08:48:30 +0000, Andrew Beckett
I've reported this to my colleague in the ICD team. We'll get a PCR
filed for this.

Andrew.

PCR 783283 was filed for this today.

Andrew.
Click to expand...
In the PCR:

Back to the main topic, there is already a fix available for pcr 783283.
It will be included in the upcoming x.x.45 wroute release.
Click to expand...
The current version is 2.4.44, so I assume it will be available soon. I don't
support SOC tools, so if you need this sooner, I guess you should contact
customer support. In the short term, you could copy the wrapper from another
stream like I suggested before.

Regards,

Andrew.
 
Could you tell me how to install SOC41USR4 which download from cadence
ESD site?thanks!

nonoewrote:
I recently downloaded SOC41USR4 from
Cadence's ESD site.
After installing it on our server, I found that the
UltraRoute program ("wroute 2.4.44") no longer runs in
64-bit mode.

The previous wroute 2.4.43 (which came with soc41usr3)
obeys the environment variable "$CDS_AUTO_64BIT" This
means I could select whether I wanted to run the 32-bit
or 64-bit exe of wroute. But the wroute 2.4.44 launcher
always runs in 32-bit mode, regardless of $CDS_AUTO_64BIT.
I've found that I can manually create a UNIX-link to the
tools.lnx86/fe/bin/64bit/wroute program-exe, but why should
I have to do that?

For now, I've copied the wroute shell-script from
soc41usr3 into our soc41usr4 (tools.lnx86/fe/bin/wroute)
installation-tree. The shell-script is just a bootloader
to detect the user's O/S platform, and this older-script
seems to work just fine with 2.4.44 (and obeys the
$CDS_AUTO_64BIT var, too!)

Anyway, was my soc41usr4 installation damaged, or is this a new
wroute "feature"? Our EDA-environment is primarily Solaris 8,
so the management grudgingly let us put a single Athlon/64
machine in the compute-pool. (But they refused to pay for
Redhat EL 3 when one of the engineers accidentally told them
about the free whiteboxlinux.org clone, so the Athlon/64
box is running WhiteBoxLinux 3.0 Respin 1.)
Click to expand...
 
Hi,

Is whiteboxlinux.org fully compatible with Redhat Enterprise?
I cannot afford Redhat Enterprise.

Kuan

On Thu, 3 Mar 2005, nonoe wrote:

I recently downloaded SOC41USR4 from Cadence's ESD site.
After installing it on our server, I found that the
UltraRoute program ("wroute 2.4.44") no longer runs in
64-bit mode.

The previous wroute 2.4.43 (which came with soc41usr3)
obeys the environment variable "$CDS_AUTO_64BIT" This
means I could select whether I wanted to run the 32-bit
or 64-bit exe of wroute. But the wroute 2.4.44 launcher
always runs in 32-bit mode, regardless of $CDS_AUTO_64BIT.
I've found that I can manually create a UNIX-link to the
tools.lnx86/fe/bin/64bit/wroute program-exe, but why should
I have to do that?

For now, I've copied the wroute shell-script from
soc41usr3 into our soc41usr4 (tools.lnx86/fe/bin/wroute)
installation-tree. The shell-script is just a bootloader
to detect the user's O/S platform, and this older-script
seems to work just fine with 2.4.44 (and obeys the
$CDS_AUTO_64BIT var, too!)

Anyway, was my soc41usr4 installation damaged, or is this a new
wroute "feature"? Our EDA-environment is primarily Solaris 8,
so the management grudgingly let us put a single Athlon/64
machine in the compute-pool. (But they refused to pay for
Redhat EL 3 when one of the engineers accidentally told them
about the free whiteboxlinux.org clone, so the Athlon/64
box is running WhiteBoxLinux 3.0 Respin 1.)
Click to expand...
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top