Quantcast
Channel: Cadence Custom IC Design Forum
Viewing all articles
Browse latest Browse all 4944

Running checkSysConf Successfully for AMS tool.

$
0
0

Dear All,

I was able to run checkSysconf for IC618 and MMSIM18.

This pointed me to the uninstalled required patches. After I installed all these patches, checkSysConf gave PASS for both IC618 and MMSIM18.

But, when I tried to run checkSysconf for INCISIVE152, I got following errors. It DOES NOT give me the Valid Release name for AMS tool.

I wonder why it is happening for AMS tool only.

Is there anyway, checkSysConf can allow me to tell the needed uninstalled packages for AMS tool like IC618 and MMSIM18.

Kind Regards,

=====================================================================
[Copyright 2002-2011] Cadence Design Systems, Inc. All rights reserved.

This program and online documentation may not be copied, modified,
re-published, uploaded, executed, or distributed in any way, in any
medium, whether in whole or in part, without prior written permission
from Cadence Design Systems, Inc.
=====================================================================


============== checkSysConf: Version 3.19 ====================

Configuration checks failed on this workstation (hp), status is: FAIL

checkSysConf cannot reliably parse your systems /etc/redhat-release file
It would appear that the file is non-standard and does not contain release
information in the standard readable format.

The contents of your /etc/redhat-release is listed below between
<RELEASE_FILE> tags.
A 'correct' release file should have only one line of content, containing
version information in a standard format.

<RELEASE_FILE>
CentOS Linux release 7.9.2009 (Core)
</RELEASE_FILE>

Please check/correct your /etc/redhat-release file and try again.
There is no OEM datafile for -r for the Linux platform.

Valid OEM images are :
foreach: No match.


Viewing all articles
Browse latest Browse all 4944

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>