| Summary: | [guru] sys-cluster/wxparaver-4.10.1 fails to find paraver-kernel libraries | ||
|---|---|---|---|
| Product: | GURU | Reporter: | joanalujaoraa5 |
| Component: | Package issues | Assignee: | GURU project <guru-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
emerge --info pkg Build log |
||
Created attachment 863388 [details]
emerge --info
Created attachment 863389 [details]
emerge --info pkg
Created attachment 863390 [details]
Build log
|
Portage installs sys-cluster/wxparaver-4.10.1 and its dependency sys-cluster/paraver-kernel-4.10.1-r1 without reporting errors. But, when trying to launch wxparaver via command line it fails with: > paraver-kernel libraries not found in $PARAVER_HOME/{lib,lib64}/paraver-kernel/ wxparaver can be found in /usr/bin/wxparaver. It's a wrapper script that launches wxparaver.bin The script seems to look for a /usr/{lib,lib64}/paraver-kernel folder, which doesn't exist, and thus fails.