Vivado 2014.1在SLES10上安装失败

嗨，可能是由于下载损坏。
请尝试再次下载＆amp;
安装。要检查文件是否正确下载，下载文件的MD5校验和值应与下载文件的MD5总和值匹配（Xilinx网站 - >支持 - >下载）.MD5sum可以从http：//下载
www.fastsum.com/将.tar文件提供给FastSum工具后，它将显示文件的Checksum  state值。将校验和状态列值与Xilinx下载页面提供的值进行比较。
如果不匹配，则表示下载的文件未完成或已损坏。您必须再次从Xilinx网站下载Vivado。
http://www.xilinx.com/support/download/index.htm如果MD5校验和值与下载的文件匹配，则使用7zip软件解压缩，因为7-zip用于压缩软件。可以从http：//下载
www.7-zip.org/（解压缩时请保持层次结构完整）建议在解压缩或解压缩下载文件时关闭防病毒软件。一些参考线程.http：//forums.xilinx.com/t5/Installation
-and-许可/的PlanAhead-14-4-失败到负载上的Win7-X64 / MP / 283254＃M3985
谢谢，维杰-----------------------------------------------
---------------------------------------------请将帖子标记为
一个答案“接受为解决方案”，以防它有助于解决您的查询。如果一个帖子引导到解决方案，请给予赞誉。



以下为原文

Hi,
May be due to corrupted download. Please try downloading again & install.
To check if the file was downloaded correctly, MD5 checksum value of downloaded file should match with MD5 sum value from where file was downloaded (Xilinx website-->support-->download).
MD5sum can be downloaded from http://www.fastsum.com/

After feeding your .tar file to FastSum tool, it will display Checksumstate value of file.
Compare the checksumstate column value with the value provided at download page on Xilinx.

If there is mismatch, it means that the downloaded files are not complete or corrupted.

You must again download Vivado from Xilinx website. http://www.xilinx.com/support/download/index.htm

If MD5 checksum value matches with downloaded file then Use 7zip software to unzip since 7-zip was used for zipping the software.
It can be downloaded from http://www.7-zip.org/ (Please keep the hierarchy intact when unzipping)

It is recommended to turn off anti-virus when unzipping or extracting downloaded file.


Some reference thread.http://forums.xilinx.com/t5/Installation-and-Licensing/PlanAhead-14-4-fails-to-load-on-Win7-x64/m-p/283254#M3985Thanks,Vijay
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.

维杰，
我已经验证了下载，这是正确的。
加上在SLES11下正确安装的相同下载。
谢谢！



以下为原文

Vijay,
 
I've verified the download and it was correct. Plus the same download installed correctly under SLES11.
 
Thanks!

嗨，似乎根本原因是不支持的操作系统。
SUSE 11是受支持的版本，因此安装过程没有问题。这是受支持的列表Microsoft Windows支持•Windows XP Professional（32位和64位），英语/日语•Windows 7和7 SP1 Professional（32位）
和64位），英语/日语•Windows 8.1专业版（64位），英语/日语Linux支持•红帽企业工作站5.8  -  5.10（32位和64位）•红帽企业工作站6.4  -  6.5（32
-bit和64-bit）•SUSE Linux Enterprise 11（32位和64位）•Cent OS 6.4和6.5（64位）
谢谢，维杰-----------------------------------------------
---------------------------------------------请将帖子标记为
一个答案“接受为解决方案”，以防它有助于解决您的查询。如果一个帖子引导到解决方案，请给予赞誉。



以下为原文

Hi,
Seems like the root cause is unsupported OS.
SUSE 11 is a supported version and hence installation went through without issues.

Here are the supported list
Microsoft Windows Support
• Windows XP Professional (32-bit and 64-bit), English/Japanese
• Windows 7 and 7 SP1 Professional (32-bit and 64-bit), English/Japanese
• Windows 8.1 Professional (64-bit), English/Japanese
Linux Support
• Red Hat Enterprise Workstation 5.8 - 5.10 (32-bit and 64-bit)
• Red Hat Enterprise Workstation 6.4 - 6.5 (32-bit and 64-bit)
• SUSE Linux Enterprise 11 (32-bit and 64-bit)
• Cent OS 6.4 and 6.5 (64-bit)Thanks,Vijay
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.

Vijay，我知道不支持SLES10。
但我有一个大型计算农场，其中大部分仍然是SLES10。
这就是为什么我想找到一种方法来使这些系统工作。安装的软件在SLES10上工作得很好，这让我觉得xsetup需要一些新的库版本存在于SLES11而不是SLES10。
如果你能帮我找到所需的库更改，也许只需在我现有的SLES10机器上修补所需的库就可以找到一些解决方法。谢谢！



以下为原文

Vijay,

I understand SLES10 is not supported. But I have a large computing farm and most of them are still SLES10. That's why I want to find a way to make those systems work.

The installed software worked on SLES10 just fine, which makes me think just the xsetup requires some new library version that exist in SLES11 but not SLES10. If you can help me find what library change it required, maybe I can find some workaround by just patching the needed library on my existing SLES10 machines.

Thanks!

嗨，您可以尝试以下步骤：1。
在SLES 11中，打开Vivado并运行tcl命令：report_environment -file system_data.txt2。
上面的命令将生成一个文件，其中包含运行Vivado.3的所有系统信息和所需文件。
在SLES 10中运行以下命令：rpm -qa以了解机器中安装的软件包。
现在将rpm -qa的输出与report_environment输出进行比较，以了解在SLES 10中运行vivado所需的文件。我希望这会有所帮助。谢谢，Vinay
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi,

You can try following steps:

1. In SLES 11, open Vivado and run the tcl command:
report_environment -file system_data.txt
2. The above command will generate a file with all the system information and required files for running Vivado.
3. Run the following command in SLES 10: rpm -qa to know the  packages installed in the machine.
4. Now compare the output of rpm -qa with report_environment output to know the files that are required for running vivado in SLES 10.

I hope this helps.

Thanks,
Vinay--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

Vinay，SLES10和SLES11系统都可以运行Vivado。
这是安装xsetup失败了。我比较了两个系统上的环境，并且差异很大，因为SLES版本之间的所有库版本升级.Below是java崩溃日志文件的一部分，表明失败是在加载一些
DLL。
但我不确定究竟是哪一个。
有什么建议吗？Stack：[0x0000000041e56000,0x0000000041f57000]，sp = 0x0000000041f53e20，free space = 1015kNative frames :( J =编译的Java代码，j =解释，Vv = VM代码，C =本机代码）C [ld-linux-x86-
64.so.2 + 0x882f] do_lookup_x + 0xcfC [ld-linux-x86-64.so.2 + 0xa1c8] _dl_relocate_object + 0x588C [ld-linux-x86-64.so.2 + 0x104e5] dl_open_worker + 0x3d5C [ld-
linux-x86-64.so.2 + 0xc3e6] _dl_catch_error + 0x66C [libdl.so.2 + 0x11fa] dlopen_doit + 0x6aJava frames :( J =编译的Java代码，j =解释，Vv = VM代码）j java.lang。
ClassLoader $ NativeLibrary.load（Ljava / lang / String;）V + 0j java.lang.ClassLoader.loadLibrary1（Ljava / lang / Class; Ljava / io / File;）Z + 302j java.lang.ClassLoader.loadLibrary0（Ljava /
lang / Class; Ljava / io / File;）Z + 2j java.lang.ClassLoader.loadLibrary（Ljava / lang / Class; Ljava / lang / String; Z）V + 48j java.lang.Runtime.load0（Ljava / lang
/ Class; Ljava / lang / String;）V + 57j java.lang.System.load（Ljava / lang / String;）V + 7j net.sf.sevenzip***inding.SevenZip.loadNativeLibraries（Ljava / util / List;）V +
29j net.sf.sevenzip***inding.SevenZ
ip.initSevenZipFromPlatformJARIntern（Ljava / lang / String; Ljava / io / File;）V + 41j net.sf.sevenzip***inding.SevenZip.initSevenZipFromPlatformJAR（Ljava / lang / String;）V + 2j ak（）V + 68v~StubRoutines ::
call_stubj aia（Ljava / util / List; Lcom / xilinx / installer / api / h;）La / e; + 419j oba（Lcom / xilinx / installer / api / h; Ljava / lang / String; Lj / r; Ljava /
util / Set;）La / e; + 390j oba（Lcom / xilinx / installer / api / h; Ljava / lang / String; Lj / r;）La / e; + 16j ocrun（）V + 486v~StubRoutines：
：call_stub



以下为原文

Vinay,

Both SLES10 and SLES11 systems can run Vivado just fine. It is the install xsetup that failed.

I compared the environment on both systems still and the differences are massive because of all the library version upgrade between SLES releases.

Below is a portion of the java crash log files that indicate the failure is at loading some dll. But I'm not sure exactly which one. Any suggestions?

Stack: [0x0000000041e56000,0x0000000041f57000],  sp=0x0000000041f53e20,  free space=1015k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ld-linux-x86-64.so.2+0x882f]  do_lookup_x+0xcf
C  [ld-linux-x86-64.so.2+0xa1c8]  _dl_relocate_object+0x588
C  [ld-linux-x86-64.so.2+0x104e5]  dl_open_worker+0x3d5
C  [ld-linux-x86-64.so.2+0xc3e6]  _dl_catch_error+0x66
C  [libdl.so.2+0x11fa]  dlopen_doit+0x6a

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/String;)V+0
j  java.lang.ClassLoader.loadLibrary1(Ljava/lang/Class;Ljava/io/File;)Z+302
j  java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/io/File;)Z+2
j  java.lang.ClassLoader.loadLibrary(Ljava/lang/Class;Ljava/lang/String;Z)V+48
j  java.lang.Runtime.load0(Ljava/lang/Class;Ljava/lang/String;)V+57
j  java.lang.System.load(Ljava/lang/String;)V+7
j  net.sf.sevenzip***inding.SevenZip.loadNativeLibraries(Ljava/util/List;)V+29
j  net.sf.sevenzip***inding.SevenZip.initSevenZipFromPlatformJARIntern(Ljava/lang/String;Ljava/io/File;)V+41
j  net.sf.sevenzip***inding.SevenZip.initSevenZipFromPlatformJAR(Ljava/lang/String;)V+2
j  a.k.()V+68
v  ~StubRoutines::call_stub
j  a.i.a(Ljava/util/List;Lcom/xilinx/installer/api/h;)La/e;+419
j  o.b.a(Lcom/xilinx/installer/api/h;Ljava/lang/String;Lj/r;Ljava/util/Set;)La/e;+390
j  o.b.a(Lcom/xilinx/installer/api/h;Ljava/lang/String;Lj/r;)La/e;+16
j  o.c.run()V+486
v  ~StubRoutines::call_stub

嗨，你有没有在这两台机器上比较java版本？谢谢，Vinay
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi,

Did you compare java versions on both the machines?

Thanks,
Vinay--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

Vinay，安装程序运行Vivado安装包中包含的java，而不是目标平台。
所以他们都是一样的。
包含的Java版本是1.7.0_40。谢谢！



以下为原文

Vinay,

The installer ran the java included inside the Vivado install package, not from the target platform. So they both are the same. The Java version included is 1.7.0_40.

Thanks!

看起来它试图加载一些国际化代码。
您是否尝试过设置LANG = C或LANG = en_US.UTF-8？
丹尼尔



以下为原文

It looks like it was trying to load some Internationalization codes.  Have you tried setting LANG=C or LANG=en_US.UTF-8?
 
Daniel
 

我刚刚在SLES11 SP3上安装了2014.1 viat瘦安装程序时遇到同样的问题
信息：日志文件位置：/root/.Xilinx/xinstall/xinstall_1398424148581.logINFO：验证了Internet连接，可以连接到internet.INFO：安装版：Vivado System EditionINFO：安装目录是/ opt / XilinxINFO：下载了1871051 mili中的所有文件
-sec ## Java运行时环境检测到致命错误：## SIGSEGV（0xb），pc = 0x00007fee172ac5af，pid = 21638，tid = 140660220851968 ## JRE版本：Java（TM）SE运行时环境（7.0_40-
b43）（build 1.7.0_40-b43）#Java VM：Java HotSpot（TM）64位服务器VM（24.0-b56混合模式linux-amd64压缩oops）＃有问题的框架：#C [lib7-Zip-JBinding.so
+ 0x875af] NativeMethodContext :: EndCPPToJava（）+ 0xcf ##写入核心转储。
默认位置：/ tmp / selfgz215708901 / core或core.21638（最大大小1 kB）。
要确保完整的核心转储，请在再次启动Java之前尝试“ulimit -c unlimited”##包含更多信息的错误报告文件保存为：＃/ tmp / selfgz215708901 / hs_err_pid21638.log ##如果您要提交错误
报告，请访问：＃http://bugreport.sun.com/bugreport/crash.jsp#崩溃发生在Java虚拟机外部的本机代码中。＃查看有问题的框架，了解在哪里报告错误。＃。/ xsetup：
第39行：21638中止$ {X_JAVA_HOME} / bin / java $ {ARGS} -cp $ {X_CLASS_PATH} -jar $ {root} /lib/classes/xinstaller.jar



以下为原文

I just had this same issue installing 2014.1 viat the thin installer on SLES11 SP3
 
INFO : Log file location: /root/.Xilinx/xinstall/xinstall_1398424148581.log
INFO : Internet connection validated, can connect to internet.
INFO : Installing Edition: Vivado System Edition
INFO : Installation directory is /opt/Xilinx
INFO : Downloaded all files in 1871051 mili-sec
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fee172ac5af, pid=21638, tid=140660220851968
#
# JRE version: Java(TM) SE Runtime Environment (7.0_40-b43) (build 1.7.0_40-b43)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.0-b56 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [lib7-Zip-JBinding.so+0x875af]  NativeMethodContext::EndCPPToJava()+0xcf
#
# Core dump written. Default location: /tmp/selfgz215708901/core or core.21638 (max size 1 kB). To ensure a full core dump, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/selfgz215708901/hs_err_pid21638.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
./xsetup: line 39: 21638 Aborted                 ${X_JAVA_HOME}/bin/java ${ARGS} -cp ${X_CLASS_PATH} -jar ${root}/lib/classes/xinstaller.jar

嗨，在这里附上install.log文件。
你会在以下位置找到它：/root/.Xilinx/xinstall/xinstall_1398424148581.logThanks,Vinay
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi,

Attach install.log file here. you will find it in the following location: /root/.Xilinx/xinstall/xinstall_1398424148581.log

Thanks,
Vinay--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

我担心我没有抓住那个文件，但是我继续从完整的图像安装而不是瘦身，一切都很成功



以下为原文

I'm afraid I didn't hold onto that file, however I continued to install from the full image rather than the thinstaller and everything was successful