求coretools安装包里面的install readme和check sum
已经有coretools_vI-2014.03 common.tar、linux.tar、amd64.tar，缺少INSTALL_README.txt和check_sum
求coretools安装包里面的INSTALL_README文件和check sum，没有这个版本，其他版本的也行。主要是用来参考环境变量设置。
非常感谢！
没看懂这是什么操作。
想参考INSTALL README里面的环境变量设置
你真是执着，一边想要自己搞，一边还不听大家给你的建议，你那个明显不是环境变量的问题，对于snps的tools基本上设置好license和bin path就可以工作了，如果你的系统安装的是64 bit的，而又想运行x86版本的，你不得不安装32bit compatible glibc才可以兼容适配
good info.
你根本没听懂问题
我发的那个帖子是说coretools可以用，但是会导致make脚本无法使用
This coretools_INSTALL_README.txt document contains installation instructions for
thetool version O-2018.09-SP3-1 in the following sections:
* General Information
* Installation Procedure
* Post-Installation Steps
* Supported Platforms and Required Operating System Patches
-----------------------------------------------------------------
General Information
-----------------------------------------------------------------
This document contains quick-start installation assistance for product files
downloaded from Synopsys by Electronic Software Transfer (EST).
For detailed installation and post-installation setup steps for most Synopsys
software, see the Installation Guide.(This resource also includes CD
installation assistance.)
To view or obtain the Installation Guide for the current release, go to
* The Synopsys Installation Guide Web page at
http://www.synopsys.com/install
To obtain your latest Synopsys license key file, go to the SmartKeys Web page at
http://www.synopsys.com/smartkeys
For information on Synopsys licensing, including download information,
setup help, and other documentation, see the Synopsys Licensing
QuickStart Guide at http://www.synopsys.com/licensing
To obtain information on supported platforms and required operating system
patches, see the "ost-Installation Steps" section of this document.
-----------------------------------------------------------------
Installation Procedure
-----------------------------------------------------------------
This section contains the following information:
- Installation Prerequisites
- Installing by Electronic Software Transfer (EST)
Installation Prerequisites
=====================================================================
The instructions provided in the following section assume that you are
downloading the files by FTP. If you prefer to download the files from
the Web by using HTTPS or FTP, go to http://www.synopsys.com/download/
and click "HTTPS Authenticated Access" or "FTP Authenticated Access."
It is recommended that you have system administrator privileges.
Also, you must have write permission in the installation directory.
Installing by Electronic Software Transfer (EST)
=====================================================================
To download and install the software,
1. Download the required product files to a temporary directory.
For most products, you will need to download
* A platform-independent (common) file, which contains files
that are not platform dependent
* A platform file, which is specific to the operating system and
hardware platform you will be using
* The Synopsys Installer, which includes the scripts for
text or GUI installation. (To determine the latest installer
version, seehttp://www.synopsys.com/install/.) For more
information on downloading and configuring the installer, see
the installer_INSTALL_README.txt file in the rev/installer_x.y
directory, where x.y is the latest version of the installer.
Note:
The Synopsys Installer is required only for products that
have a "common" file. The installer needs to be downloaded
only once per release and can be used to install all software
with a "common" file.
Download example:
% cd/usr/tmp/tmpdir1
% ftp ftp.synopsys.com
220 Synopsys FTP server ready
Name: <your_synopsys_username>
Password: <your_synopsys_password>
230 User <your_synopsys_username> logged in.
ftp> passive # Note:
# Passive mode is required.
# The passive command toggles between passive and active mode.
# If your ftp utility does not support passive mode, use http.
# For more details, see https://solvnet.synopsys.com/retrieve/034308.html
ftp> binary
ftp> cd rev#Use "cd /auth" for patch releases or "cd /rev_o" for old releases
ftp> cd <your product>_vO-2018.09-SP3-1
ftp> get
coretools_INSTALL_README.txt
coretools_vO-2018.09-SP3-1_<platform>.spf
coretools_vO-2018.09-SP3-1_common.spf
checksum_info.txt
where <platform> is one or more of linux64, suse64, and so on.
The checksum_info.txt file will only be present in general availability
production releases. It is not available with beta and other limited
availability releases.
The checksum_info.txt file includes the following information:
CRCsizefilename
----------------------------------------------------------------------
423335234917305600product_version_common.spf
33716670351103744product_version_linux64.spf
----------------------------------------------------------------------
You can use the UNIX cksum command to validate the integrity of the downloaded files.
For example,
UNIX> cksum product_version.common.spf
423335234917305600product_version.common.spf
Note:
It is no longer necessary to download the EST (or FTP) files for
multiple products into a separate temporary directory. For specific
product download instructions, see the SolvNet Download Center at
https://solvnet.synopsys.com/DownloadCenter
# Get the Synopsys Installer 3.4 or higher (if needed)
2. Add the installer directory to your UNIX path.
% set path=(/usr/synopsys/installer $path)
3. To install the software,
In interactive mode, enter one of the following installer commands:
% installer #To use a text script
% installer -gui (or setup.sh) #To use a GUI
% installer -gui -new_installer #To use a GUI with new interface
#Requires installer 3.4 or above
If you invoked the installer from either the installer directory
or a directory that does not contain downloaded product files,
you will be prompted to provide a source path to the temporary
directory containing the downloaded product files.
If you invoke the installer from the temporary directory containing
the downloaded product files. You can just accept the default path.
Note:
Don't use the path that contains files extracted from the downloaded
product files.
In batch mode (requires installer 3.4 or above), enter following installer command:
% installer -batch_installer -source <SOURCE> -target <DEST>
<SOURCE>: directory that containstemporary (*.spf) product files
<DEST>: Destination directory, product(s) will be installed under
Destination_dir/coretools/O-2018.09-SP3-1/...
In batch mode:
- Installer will install all available products under the source directory.
See the Installation Guide for information on configuring installer to
only install selected releases, products, and platforms, and to set destination
directory for each selected product.
- If a product has a license agreement, installation will not continue until
the product's license agreement has been accepted (or declined). Installer
will skip the product if you decline its license agreement.
- Installer also skips the product if one of its components has a mismatched
check sum.
- Installation will continue if the contents of the destination directory cannot
be identified.
- Installation will abort if the destination doesn't have enough free disk space.
4. Answer the installer prompts.
When you are prompted to choose a location for installing the
software, do not select the temporary directory. You must
specify a new location.
If you are installing multiple operating system platforms, you
need to install the platform-independent package only once for
each product. The platform-independent package contains files
that are common to all the supported platforms.
If you encounter any installer problems, please see the SolvNet
article "Synopsys Installer 2.x/3.x Troubleshooting" at
https://solvnet.synopsys.com/retrieve/023842.html
5. After installation is complete, each user must modify the path,
set a licensing variable, and set any product-specific variables.
See the Post-Installation Steps section, below.
-------------------------------------------------------------------------------
Post-Installation Steps
-------------------------------------------------------------------------------
These sections contains the following information:
- Setting up the User Environment
- Verifying the Tool Installation
- Supported Platforms and Required Operating System Patches
Setting Up the User Environment
========================================================
To set up your users, you must create a Synopsys source file, or modify
each user's $HOME setup files (typically .cshrc, .profile, .kshrc, or .bashrc),
as follows. For tool-specific information, see "Setting Up <product_name>
for Each User" in the appropriate Product Installation Note.
1. Set SNPSLMD_LICENSE_FILE, LM_LICENSE_FILE, or a tool-specific licensing variable.
This variable specifies the path to the Synopsys FLEXlm license server.
Note:
SNPSLMD_LICENSE_FILE is supported only for tools based on the Synopsys Common
Licensing (SCL) snpslmd daemon. Earlier versions of Synopsys tools based on legacy
daemons require that you set LM_LICENSE_FILE or another legacy licensing variable.
If your environment includes earlier and more recent tool versions, consider setting
SNPSLMD_LICENSE_FILE and LM_LICENSE_FILE to point to the SCL license servers.
In the following example, it is assumed that the Synopsys license server
is using TCP port 27000, the default port. (However, you can specify another
port by modifying the SERVER line of your site's key file--for example,
"SERVER myserver 8308a297 26585.")
Example:
* Add to .cshrc
setenv SNPSLMD_LICENSE_FILE 27000@myserver
or
setenv LM_LICENSE_FILE 27000@myserver
* Add to .profile, .kshrc, or .bashrc
SNPSLMD_LICENSE_FILE=27000@myserver; export SNPSLMD_LICENSE_FILE
or
LM_LICENSE_FILE=27000@myserver; export LM_LICENSE_FILE
2. Add the tool executable files to the user path.
Example:
* Add to .cshrc:
set path=(synopsys_root/bin $path)
* Add to .profile, .kshrc, or .bashrc:
PATH=synopsys_root/binPATH
export PATH
Note:
The path to the executable bin directory will vary.
For some tools, the appropriate directory is
synopsys_root/<platform>/<product>/bin
3. Set any tool-specific variables.
In many cases, tool-specific environment variables must be set.
Typically, you need to set an environment variable that points
to the root directory for the Synopsys tool.
Example:
setenv SYNOPSYS /path/to/synopsys_root
Note:
Not all tools use the $SYNOPSYS environment variable. In some
cases, other tool-specific variables must be set.See the
Installation Guide for details.
Verifying the Tool Installation
===================================================================
To verify that the Synopsys tools are installed correctly, see the
appropriate tool chapter in the Installation Guide.
The Installation Guide is available on the Web. For more information
on how to access the Installation Guide, see the "General Information"
section at the top of this document.
-----------------------------------------------------------------
Supported Platforms and Required Operating System Patches
-----------------------------------------------------------------
To use Synopsys tools successfully, you must
* Be running on a supported hardware platform
* Be using a supported operating system
* Have applied the required OS patches
For detailed information about supported platforms and operating system
patches, go to
http://www.synopsys.com/qsc
Click the appropriate version-related Foundation link to get a list of
supported OS and patch level information.