05-04-2015 10:50 AM
05-04-2015 03:01 PM
05-04-2015 06:15 PM - edited 05-05-2015 01:51 AM
Debian is unsupported OS and we have not tested Vivado on Debian.
Try using supported OS.
Microsoft Windows Support
• Windows 7 and 7 SP1 Professional (64-bit), English/Japanese.
• Windows 8.1 Professional (64-bit), English/Japanese.
• Vivado® Lab Edition is the only Xilinx toolset that supports Windows 7 SP1
Professional, 32-bit Operating System. Lab Edition also supports the 64-bit systems.
• Red Hat Enterprise Workstation 7.0 (64-bit)
• Red Hat Enterprise Workstation 6.4-6.6 (64-bit)
• SUSE Linux Enterprise 12.0 (64-bit)
• Cent OS 7.0 (64-bit)
• Ubuntu Linux 14.04 LTS (64-bit)
• Vivado Lab Edition is the only Xilinx toolset that supports the Red Hat Enterprise
05-05-2015 01:48 AM
This might be an unsupported OS, but uname -m is the right command to check the architecture ;).
05-05-2015 10:45 AM
I am running Arch Linux too. Solved the problem by:
1\ starting the installer with the --confirm parameter , path to the xsetup file got displayed
2\ finding and modifying the xsetup file (uname -m).
3\ confirmed the execution of xsetup in the installer shell.
05-05-2015 07:46 PM
05-05-2015 10:58 PM
Nobody said that someone installs Vivado 2015.1 on 32-bit platform. However, the usage of 'uname -i' in xsetup is wrong and should be replaced by 'uname -m'. The first one returns the hardware platform (e.g. GenuineIntel, AuthenticAMD, ...) and the latter one returns the machine hardware name (e.g. i386, i686, x86_64, ...).
12-07-2015 04:20 AM
I had the same issue to install Vivado or to install SDK separatly. A colleague from software staff found a solution. In Debians, their is an uname working well (at least for "-i" otpion):
$ /usr/lib/klibc/bin/uname -i
$ sudo dpkg-divert --add --rename --divert /bin/uname.orig /bin/uname $ sudo ln -s /usr/lib/klibc/bin/uname /bin/uname
To go back :
$ sudo dpkg-divert --rename --remove /bin/uname
12-17-2015 01:57 PM
I have downloaded the Linux 64 bit installer (.bin). I am running on a supported 64 bit Linux (Ubuntu 14.04). I am getting this same error. Is there a workaround? I saw mention of a command line option, but I haven't found documentation for that. (Not really sure where to look.) I am running a VMware Ubuntu 14.04.3 (Trusty Tahr).