08-09-2012 08:00 AM
I recently installed ISE 14.2/Vivado/Vivado_HLS 1012.2, but I had this problem already on ISE 12.3.
Whenever the GUI of ise, xps, xsdk needs to access the web, I get "Couldn't load XPCOM." from Firefox and the page does not launch.
$ . /usr/local/binaries/Xilinx/14.2/ISE_DS/settings64.sh
I also get the "Couldn't load XPCOM." error from firefox. But if I then do
$ export LD_LIBRARY_PATH=/usr/lib64:$LD_LIBRARY_PATH
firefox will launch all right. So the xilinx environment variable setup screws up something.
# tries to stop "Couldn't load XPCOMM."
echo "xilinx-firefox: it's me"
echo >&2 "xilinx-firefox: it's me on stderr"
and configured xilinx-firefox in ISE preferences as the web browser, it turns out not to get run!. ISE keeps on using the default browser /usr/bin/firefox.
Any help would be much appreciated. I searched the fora and the web, found some incidents with
XPCOM, but nothing quite similar.
08-16-2012 07:04 AM
08-09-2012 09:07 AM
Wow, my third email this morning with the same advice: file a webcase. This sounds like a bug in the linux install.
Best to get it into the team to look at it.
08-15-2012 10:54 AM
Sounds like a library incompatibility. The startup script just prepends $XILINX/lib/lin64 to LD_LIBRARY_PATH and $XILINX/bin/lin64 to PATH. Something in the Xilinx .so libraries may be conflicting.
Check out this other related thread:
08-16-2012 07:04 AM
10-03-2012 08:28 AM
Many, many thanks for this workaround!
It means I don't need two Unix sessions on parallel, one for the Xilinx tools and one for my homebrew tools.
This LD_LIBRARY_PATH stuff is really bad pratice.
Many thanks once again
10-12-2015 04:17 AM
Yes, I concur fully. This should be implemented properly with rpaths.
08-24-2016 05:38 AM
Hello! I do have a similar problem. This is related to ISE Design Suite. I am using Kubuntu 14.04 LTS and Xilinx ISE 14.7(lin64) Application Version p.20131013
I have tried several approaches to get ISE to use Kubuntu libstdc++.so.6.0.19 library nothing seems to work.
Did insert export LD_LIBRARY_PATH= Result: firefox at the top of firefox script, but do get error on unknown variable Result. I am sorry if i did not understand what you did, are pretty new to Linux.
As attachment is a shell script log where different approaches are tested.
08-30-2016 11:35 PM
Problem solved! Tested out on laptop, ISE asked for libstdc++.so.6 in path /opt/Xilinx/14.7/ISE_DS/common/lib/lin64, stated GLIBCXX_3.4.15 was missing. To se if your libstdc++.so.6 have GLIBCXX_3.4.15, navigate to folder and type
$ sudo strings libstdc++.so.6 | grep GLIBC
I did not have GLIBCXX_3.4.15 so i replaced libstdc++.so.6 with a version that did have GLIBCXX_3.4.15.
To get the new library to take effect close all firefox windows in all desktops, then test out with ISE, this worked for me:)
07-18-2017 10:37 AM
Just wanted to note that, at least in Vivado 2016.4, this issue is STILL not fixed. Vivado still tramples on LD_LIBRARY_PATH.
This thread is 5 years old, and yet the problem remains a problem. Is anyone doing any QC on the software?
01-11-2018 01:33 AM
I'm on Vivado 2017.1 and the problem is still not fixed ...
01-12-2018 06:49 AM
We have encountered similar issues in the past relating to GLIBC errors when starting a tool/or documentation doesn’t work, etc. Could you please try the following steps to backup the conflicting libraries and replace them with system ones?
The last command copies the libstdc++ objects from your OS lib location, you may have to change that path accordingly. Please let me know if this works for your system.
(The following AR walks through a solution for this problem (http //www.xilinx.com/support/answers/52093.htm). I know it’s for ISE, but should be the same with Vivado).
Hope this helps.
01-17-2018 04:36 AM
@anatoli: I managed to correct the problem with this workaround :
$ cd /opt/Xilinx/Vivado/2017.1/ids_lite/ISE/lib/lin64 $ mv libstdc++.so.6 libstdc++.so.6.bak $ ln -s /lib/x86_64-linux-gnu/libstdc++.so.6
01-17-2018 05:02 AM
Thanks for letting us know and I'm glad to hear you have now managed to overcome this issue.
This Workaround will be useful for other users who'd encounter the same problem in the future.
Please note that the Xilinx Software Development team is aware of this problem and are currently working on a permanent fix for this issue.
Hope this meets your satisfaction.
Have a nice day.