Firefox Web浏览器称“无法加载XPCOM”

由于上面和网上的其他文件，我想出了如何解决这个问题。
1.问题是Xilinx环境的上述环境迫使firefox（包括其XPCOM模块）使用Xilinx的libstdc ++版本。所以，不是主机系统的libstdc ++。所以。
任何依赖某个版本的libstdc ++的程序，比如firefox（也就是svn，例如）都行不通。
设置环境后，ise，vivado和朋友然后继续使用并依赖firefox，这会导致上述问题。
2.由于ise不服从备用浏览器选择偏好，而vivado没有我能找到的那个，这一事实更加复杂。
3.我通过编辑/ usr / bin / firefox解决了这个问题，这是一个shell脚本，它只是稍后加载二进制可执行文件，并作为脚本的第一行插入：
export LD_LIBRARY_PATH =
结果：firefox忽略LD_LIBRARY_PATH的所有先前设置，并且适用于所有Xilinx应用程序。
4. Xilinx脚本编写者请注意，对于您自己的应用程序，依赖于LD_LIBRARY_PATH的全局设置是不可取的。
应在您的应用程序中进行此类设置。
它绕过了Linux对.so文件的仔细版本管理，并使任何为Xilinx设置的shell无法用于其他一些应用程序。
这种做法是在寻找麻烦，显然必须由客户重新设定。
我怀疑这样的设置甚至可以用于所谓的“支持版本”;
它们在这方面是相同的：系统有一个编号为.so的版本树，安装在正确的位置，确保所有二进制文件都可以加载他们需要的库。
在原帖中查看解决方案



以下为原文

I figured out how to solve this, thanks to the above and other documents on the net.1. The problem is that the above environment by Xilinx environment forces firefox, including its XPCOM module, to use Xilinx's version of libstdc++.so,  not the host system's libstdc++.so. Any program that relies on a certain version of libstdc++, like firefox (an also svn, by example) will not work. After setting the environment, ise, vivado and friends then proceed to use and rely on firefox, which leads to the trouble described above.2. This gets compounded by the fact that ise does not obey to an alternate browser selection preference, and vivado  does not have one I could find.3. I solved the problem by editing /usr/bin/firefox, which mercifully is a shell script that loads the binary executable only later, and inserting, as the first line of the script:export LD_LIBRARY_PATH= Result: firefox ignores all previous settings of LD_LIBRARY_PATH, and works in all Xilinx applications.4. Xilinx script writers please note, it is BAD PRACTICE to rely on a global setting of LD_LIBRARY_PATH for your own applications; such settings should be made IN your applications. It circumvents Linux' careful version management  of .so files, and makes any shell which has been set up for Xilinx unusable for some other applications.This practice is asking for trouble, which obviously has to be set right by customers all over again. I doubt that such setting can even work on the so-called 'supported versions'; they are just the same in this respect: the system has a version tree of numbered .so's, installed in the correct places, that ensure that all binaries can load the librares they need.View solution in original post

克里斯，
哇，今天早上我的第三封电子邮件，提出了同样的建议：提交一个webcase。
这听起来像linux安装中的一个错误。
最好让它进入团队来看待它。
谢谢，
Austin Lesea主要工程师Xilinx San Jose



以下为原文

Kris,

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.
 
Thank you,
Austin Lesea
Principal Engineer
Xilinx San Jose

Tx奥斯汀。
我已经做了。



以下为原文

Tx Austin. I just did.

听起来像是图书馆不兼容。
启动脚本只需将$ XILINX / lib / lin64添加到LD_LIBRARY_PATH，将$ XILINX / bin / lin64添加到PATH。
Xilinx .so库中的某些内容可能存在冲突。
看看这个其他相关主题：
http://forums.xilinx.com/t5/EDK-and-Platform-Studio/No-browser-link-opens-in-SDK-13-1-ubuntu-10-10-x64/td-p/219085



以下为原文

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:
http://forums.xilinx.com/t5/EDK-and-Platform-Studio/No-browser-link-opens-in-SDK-13-1-ubuntu-10-10-x64/td-p/219085

由于上面和网上的其他文件，我想出了如何解决这个问题。
1.问题是Xilinx环境的上述环境迫使firefox（包括其XPCOM模块）使用Xilinx的libstdc ++版本。所以，不是主机系统的libstdc ++。所以。
任何依赖某个版本的libstdc ++的程序，比如firefox（也就是svn，例如）都行不通。
设置环境后，ise，vivado和朋友然后继续使用并依赖firefox，这会导致上述问题。
2.由于ise不服从备用浏览器选择偏好，而vivado没有我能找到的那个，这一事实更加复杂。
3.我通过编辑/ usr / bin / firefox解决了这个问题，这是一个shell脚本，它只是稍后加载二进制可执行文件，并作为脚本的第一行插入：
export LD_LIBRARY_PATH =
结果：firefox忽略LD_LIBRARY_PATH的所有先前设置，并且适用于所有Xilinx应用程序。
4. Xilinx脚本编写者请注意，对于您自己的应用程序，依赖于LD_LIBRARY_PATH的全局设置是不可取的。
应在您的应用程序中进行此类设置。
它绕过了Linux对.so文件的仔细版本管理，并使任何为Xilinx设置的shell无法用于其他一些应用程序。
这种做法是在寻找麻烦，显然必须由客户重新设定。
我怀疑这样的设置甚至可以用于所谓的“支持版本”;
它们在这方面是相同的：系统有一个编号为.so的版本树，安装在正确的位置，确保所有二进制文件都可以加载他们需要的库。



以下为原文

I figured out how to solve this, thanks to the above and other documents on the net.1. The problem is that the above environment by Xilinx environment forces firefox, including its XPCOM module, to use Xilinx's version of libstdc++.so,  not the host system's libstdc++.so. Any program that relies on a certain version of libstdc++, like firefox (an also svn, by example) will not work. After setting the environment, ise, vivado and friends then proceed to use and rely on firefox, which leads to the trouble described above.2. This gets compounded by the fact that ise does not obey to an alternate browser selection preference, and vivado  does not have one I could find.3. I solved the problem by editing /usr/bin/firefox, which mercifully is a shell script that loads the binary executable only later, and inserting, as the first line of the script:export LD_LIBRARY_PATH= Result: firefox ignores all previous settings of LD_LIBRARY_PATH, and works in all Xilinx applications.4. Xilinx script writers please note, it is BAD PRACTICE to rely on a global setting of LD_LIBRARY_PATH for your own applications; such settings should be made IN your applications. It circumvents Linux' careful version management  of .so files, and makes any shell which has been set up for Xilinx unusable for some other applications.This practice is asking for trouble, which obviously has to be set right by customers all over again. I doubt that such setting can even work on the so-called 'supported versions'; they are just the same in this respect: the system has a version tree of numbered .so's, installed in the correct places, that ensure that all binaries can load the librares they need.

很多，非常感谢这个解决方法！
这意味着我不需要并行两个Unix会话，一个用于Xilinx工具，一个用于我的自制工具。
这个LD_LIBRARY_PATH的东西真的很糟糕。
非常感谢再次
保罗费雷拉



以下为原文

 
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
 
Paulo Ferreira
 

是的，我完全同意。
这应该使用rpath正确实现。



以下为原文

Yes, I concur fully. This should be implemented properly with rpaths.

帮帮我！
你好！
我确实有类似的问题。
这与ISE Design Suite有关。
我正在使用Kubuntu 14.04 LTS和Xilinx ISE 14.7（lin64）应用程序版本p.20131013
我已经尝试了几种方法让ISE使用Kubuntu libstdc ++。so.6.0.19库似乎没什么用。
插入导出LD_LIBRARY_PATH =结果：firefox位于firefox脚本的顶部，但确实在未知变量Result上出错。
我很抱歉，如果我不明白你做了什么，对Linux来说是新手。
附件是一个shell脚本日志，其中测试了不同的方法。
更改设置-library 12 KB



以下为原文

Help!
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.
 
            changes setup -library ‏12 KB

问题解决了！
在笔记本电脑上测试，ISE在路径/opt/Xilinx/14.7/ISE_DS/common/lib/lin64中询问libstdc ++。so.6，表示缺少GLIBCXX_3.4.15。
如果你的libstdc ++。so.6有GLIBCXX_3.4.15，请导航到文件夹并输入
$ sudo strings libstdc ++。so.6 |
grep GLIBC
我没有GLIBCXX_3.4.15所以我用一个有GLIBCXX_3.4.15的版本替换了libstdc ++。so.6。
为了让新库生效关闭所有桌面上的所有firefox窗口，然后使用ISE测试，这对我有用:)



以下为原文

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:)
 
 
 

只是想注意，至少在Vivado 2016.4中，这个问题仍然没有解决。
Vivado仍然践踏LD_LIBRARY_PATH。
这个帖子已经有5年了，但问题仍然存在。
有人在软件上做任何质量控制吗？



以下为原文

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?

我在Vivado 2017.1上，问题仍未修复......



以下为原文

I'm on Vivado 2017.1 and the problem is still not fixed ...

你好@ martoni，@ rgaddi，
在启动工具/或文档不起作用时，我们在过去遇到过与GLIBC错误相关的类似问题等。您能否尝试以下步骤来备份冲突的库并用系统库替换它们？
cd //Vivado/2017.1/ids_lite/ISE/lib/lin64/
mkdir obsolete_libstdc ++
mv libstdc ++。obsolete_libstdc ++
cp /usr/lib/libstdc++.so。
最后一个命令从您的OS lib位置复制libstdc ++对象，您可能必须相应地更改该路径。
如果这适用于您的系统，请告诉我。
（以下AR介绍了此问题的解决方案（http //www.xilinx.com/support/answers/52093.htm）。我知道它适用于ISE，但应该与Vivado相同）。
希望这可以帮助。
亲切的问候，
阿纳托利
亲切的问候，Anatoli Curran，Xilinx技术支持-----------------------------------------
--------------------------------不要忘记回复，工作，并接受解决方案.----
--------------------------------------------------
-------------------



以下为原文

Hello @martoni , @rgaddi,
 
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?
 

• cd //Vivado/2017.1/ids_lite/ISE/lib/lin64/
  
• mkdir obsolete_libstdc++
  
• mv libstdc++. obsolete_libstdc++
  
• cp /usr/lib/libstdc++.so .
  

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.
 
Kind Regards,
Anatoli
Kind Regards,
Anatoli Curran,
Xilinx Technical Support
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

@anatoli：我设法用这个解决方法纠正了这个问题：
$ 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



以下为原文

@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

你好@ martoni，
感谢您告诉我们，我很高兴听到您无法克服这个问题。
此解决方法对将来遇到相同问题的其他用户非常有用。
请注意，Xilinx软件开发团队了解此问题，目前正在针对此问题进行永久性修复。
希望这符合您的满意度。
祝你今天愉快。
亲切的问候，Anatoli Curran，Xilinx技术支持-----------------------------------------
--------------------------------不要忘记回复，工作，并接受解决方案.----
--------------------------------------------------
-------------------



以下为原文

Hello @martoni,
 
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.
Kind Regards,
Anatoli Curran,
Xilinx Technical Support
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------