赛灵思
直播中

罗茵

7年用户 192经验值
私信 关注
[问答]

在centos上安装docnav,Selinux被禁用

我已经在最新的centos 7上安装了vivado 2017.4(我认为是7.4) -  KDE桌面。
Selinux被禁用。
我已经安装并以root身份运行
使用脱机下载的PDF文件
除了docnav,一切似乎都很好
我确实在centos 6上工作正常,但仍然在windows7上工作,所以我熟悉所需的步骤
(除非我忘记了什么)
我似乎无法在Vivado之外启动docnav  - 没有显示错误消息
在vivado里面我无法识别下载的PDF文件。
但它确实运行
设置“运行时环境”面板中的“探索”按钮也不起作用(不要打开窗口)
我已经移动了downloads.xml文件并编辑了路径
我尝试过共享和非共享下载 - 没有区别
我已多次检查文件的路径。
有谁知道这是我错过了什么或与centos或其他任何问题?
还有其他人有离线Centos-7安装吗?
谢谢

以上来自于谷歌翻译


以下为原文


I've installed vivado 2017.4 on centos 7 latest (7.4 I think) - KDE desktop.
Selinux is disabled.
I've installed and am running as root
Using offline downloaded PDF files
Everything seems fine except docnav

I did have this working OK on centos 6 and still do on windows7  so I am familiar with the steps required
(unless I've forgotten something)

I can't seem to get docnav to start outside of Vivado at all - no error messages shown
Inside vivado I can't get it to recognise the downloaded PDF's. but it does run
Also  the "explore" buttons in the settings "runtime Environment" panel don't function (dont open windows)

I have moved  the  downloads.xml file and edited the paths
I've tried shared and non-shared downloads - no difference
I've checked the paths the files are in multiple times.

Does anyone know if this is me missing something or a problem with centos or anything else?
Does anyone else have an offline Centos-7 install working?

Thanks

回帖(4)

李俊

2018-12-28 11:04:49
首先尝试安装32位库
yum install glibc.i686
然后从bash shell启动Docnav,并查找任何错误消息..你得到了什么?
不要忘记通过接受帖子作为解决方案来尽可能地关闭线程。

以上来自于谷歌翻译


以下为原文

First try installing the 32 bit libraries with
 
yum install glibc.i686
 
Then launch Docnav from a bash shell, and look for any error messages..    What do you get?
Don't forget to close a thread when possible by accepting a post as a solution.
举报

李海

2018-12-28 11:23:02
你好
谢谢 - 我已经完成了,现在我收到了一条错误消息。
“无法将不兼容的Qt库(版本0x40805)与此库混合(0x40806)中止”
一个快速的雅虎搜索告诉我,Qt库之前已经引发了问题。
我不知道如何在不干扰其他程序的情况下解决这个问题 - 你有什么建议吗?
谢谢

以上来自于谷歌翻译


以下为原文

Hi
 
Thanks - I've done that and I do get an error message now.
"Cannot mix incompatible Qt library (version 0x40805) with this library (0x40806) aborted"
 
a quick yahoo search tells me that Qt libraries have caused issues before.
I'm not sure how to resolve this without interfering with other programs though - do you have suggestions?
 
thanks
 
 
举报

李俊

2018-12-28 11:36:53
之前已经看到过这个问题:
https://forums.xilinx.com/t5/Installation-and-Licensing/docnav-fails-to-start-when-Qt-libs-are-installed-libQtDBus/td-p/763521
我认为让Qt库版本匹配可能会解决问题......要么升级Docnav中的qt库,要么降级系统中的Qt库。
或者取消设置QTP_PLUGIN_PATH环境变量(这看起来像是一个Hail Mary游戏)。
我首先尝试重命名Docnav Qt库文件,然后使用正确的版本删除新文件。
但是在重命名文件之后启动Docnav以查看它如何响应丢失的库文件。这可能会让您感到惊讶。
不要忘记通过接受帖子作为解决方案来尽可能地关闭线程。

以上来自于谷歌翻译


以下为原文

This problem has been seen before here: 
 
https://forums.xilinx.com/t5/Installation-and-Licensing/docnav-fails-to-start-when-Qt-libs-are-installed-libQtDBus/td-p/763521
 
I'm thinking that getting the Qt library versions to match might fix things...  Either upgrading the qt libraries found in Docnav, or by downgrading the Qt libraries in the system.     Or unsetting the QTP_PLUGIN_PATH environment variable (which seems like a Hail Mary play).  
 
I'd first try renaming the Docnav Qt library files, and then dropping in new ones with the right version.    But launch Docnav after renaming the files to see how it responds to the missing library files..  It might surprise you.
Don't forget to close a thread when possible by accepting a post as a solution.
举报

李海

2018-12-28 11:50:49
是的我看到了上一条消息,但删除变量似乎没有做任何事情。
我现在尝试的是/ opt / Xilinx / DocNav
将lib *移动到./backup
从/ user / lib64复制Qt库
这允许docnav从shell启动但阻止它从Vivado启动
可能有一个组合正常,但我还没有找到它
正如你所指出的那样,这个问题似乎已经存在很长时间了 - 这会很好
为此ASAP获得官方修复。
(特别是因为我不知道还有什么可能会受到影响)

以上来自于谷歌翻译


以下为原文

Yes I saw the previous message but deleting the variable didnt seem to do anything.
 
What I have tried now is in /opt/Xilinx/DocNav
move lib* to ./backup
copy Qt libs from /user/lib64 
 
This allows docnav to boot from a shell but prevents it starting in Vivado
There may be a combination that works correctly but I haven't found it
This issue seems to be quite long standing as you pointed out - it would be good
to get an official fix for this ASAP.
(Especially as I don't know what else may be affected down the line)
 
 
举报

更多回帖

发帖
×
20
完善资料,
赚取积分