Relative path / reference link issue #81

Closed
Nerigal opened this Issue Mar 8, 2017 · 0 comments

Comments

Projects
None yet
3 participants
@Nerigal
Contributor

Nerigal commented Mar 8, 2017

The error come from an rpm build using the tar.gz provided by lisk-hq

here is an example:
ERROR 0002: file '/opt/lisk/client/node_modules/sodium/deps/libsodium/test/default/.libs/scalarmult7' contains an invalid rpath '/home/lisk/lisk-build/src/lisk-0.7.0a-Linux-x86_64/node_modules/.staging/sodium-c2c29825/deps/build/lib' in [/home/lisk/lisk-build/src/lisk-0.7.0a-Linux-x86_64/node_modules/.staging/sodium-c2c29825/deps/build/lib]

to find where the problem is, you can just use the command: strings /opt/lisk/client/node_modules/sodium/deps/libsodium/test/default/.libs/scalarmult7

you will see invalid path reference inside the libraries

@Isabello Isabello self-assigned this Mar 8, 2017

@karmacoma karmacoma changed the title from relative path / reference link issue to Relative path / reference link issue Mar 9, 2017

@karmacoma karmacoma added the bug label Mar 9, 2017

@karmacoma karmacoma added this to In Progress in Version 0.7.0 Mar 9, 2017

@karmacoma karmacoma closed this in #82 Mar 9, 2017

karmacoma added a commit that referenced this issue Mar 9, 2017

Merge pull request #82 from LiskHQ/81-Rpath-Links
Correct rpath issues on libsodium libraries - Closes #81

@karmacoma karmacoma removed this from In Progress in Version 0.7.0 Mar 9, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment