cannot find libarary error
I am trying to install a software "W" which requires some non standard packages like "XYZ". I am installing XYZ as instructed in the related site using the following commands
./configure -C
make
make install
after installation of XYZ, I use the following commands to install W (as suggested in the related site):
env PKG_CONFIG_PATH="installation path for XYZ/lib/pkgconfig" cmake
make
however I get usr/bin/ld cannot find -lXYZ.
I have also tried the following, which returned the same results:
export LD_LIBRARY_PATH="installation path for XYZ/lib"
when I am checking the library list associated with LD_LIBRARY_PATH I see something like the following results:
................. libXYZ.la
................. libXYZ.so -> libXYZ.so.1.5.3
................. libXYZ.so.1 -> libXYZ.so.1.5.3
................. libXYZ.so.1.5.3
................. pkgconfig
where ....... are some info like date and other things
Does this problem is caused due to the version number of libraries or what? how can i solve it?
libraries shared-library
asked Dec 28 '18 at 17:23
oscaralioscarali
61
add a comment |
I am trying to install a software "W" which requires some non standard packages like "XYZ". I am installing XYZ as instructed in the related site using the following commands
./configure -C
make
make install
after installation of XYZ, I use the following commands to install W (as suggested in the related site):
env PKG_CONFIG_PATH="installation path for XYZ/lib/pkgconfig" cmake
make
however I get usr/bin/ld cannot find -lXYZ.
I have also tried the following, which returned the same results:
export LD_LIBRARY_PATH="installation path for XYZ/lib"
when I am checking the library list associated with LD_LIBRARY_PATH I see something like the following results:
................. libXYZ.la
................. libXYZ.so -> libXYZ.so.1.5.3
................. libXYZ.so.1 -> libXYZ.so.1.5.3
................. libXYZ.so.1.5.3
................. pkgconfig
where ....... are some info like date and other things
Does this problem is caused due to the version number of libraries or what? how can i solve it?
libraries shared-library
asked Dec 28 '18 at 17:23
oscaralioscarali
61
1
I'd start by examining the output ofcmakeand/or theCMakeCache.txtfile to see what location (if any) was cached for the library. (I'm hazy on the details of how Cmake works, however it has its own rules for finding packages that may or may not involvepkg-config.)
– steeldriver
Dec 28 '18 at 18:22
@steeldriver i cheked it seems to be allright, however, i slightly summerized the quession in fact there are some packeges like xyz, tuv, mln, that are reqiured for W. However some of their libraries are also defined in the others for example xyz/lib has libxyz libtuv,.... can this be the cause of problem?
– oscarali
Dec 28 '18 at 18:51
Can you try withexport LIBRARY_PATH="installation path for XYZ/lib".
– Thomas
Dec 28 '18 at 18:53
@Thomas yes it did! Thanks it realy made me misreable during the past week! But how? What is difference? And also i have read library_path and ld-path are not good choices especially library path
– oscarali
Dec 28 '18 at 19:12
BasicallyLIBRARY_PATHis used during linking,LD_LIBRARY_PATHis used during runtime. But you will find enough resources with a search engine of your choice. Not sure why that should be considered not good. It would be better if theconfigurestep would provide such...
– Thomas
Dec 28 '18 at 19:26
add a comment |
I am trying to install a software "W" which requires some non standard packages like "XYZ". I am installing XYZ as instructed in the related site using the following commands
./configure -C
make
make install
after installation of XYZ, I use the following commands to install W (as suggested in the related site):
env PKG_CONFIG_PATH="installation path for XYZ/lib/pkgconfig" cmake
make
however I get usr/bin/ld cannot find -lXYZ.
I have also tried the following, which returned the same results:
export LD_LIBRARY_PATH="installation path for XYZ/lib"
when I am checking the library list associated with LD_LIBRARY_PATH I see something like the following results:
................. libXYZ.la
................. libXYZ.so -> libXYZ.so.1.5.3
................. libXYZ.so.1 -> libXYZ.so.1.5.3
................. libXYZ.so.1.5.3
................. pkgconfig
where ....... are some info like date and other things
Does this problem is caused due to the version number of libraries or what? how can i solve it?
libraries shared-library
asked Dec 28 '18 at 17:23
oscaralioscarali
61
I am trying to install a software "W" which requires some non standard packages like "XYZ". I am installing XYZ as instructed in the related site using the following commands
./configure -C
make
make install
after installation of XYZ, I use the following commands to install W (as suggested in the related site):
env PKG_CONFIG_PATH="installation path for XYZ/lib/pkgconfig" cmake
make
however I get usr/bin/ld cannot find -lXYZ.
I have also tried the following, which returned the same results:
export LD_LIBRARY_PATH="installation path for XYZ/lib"
when I am checking the library list associated with LD_LIBRARY_PATH I see something like the following results:
................. libXYZ.la
................. libXYZ.so -> libXYZ.so.1.5.3
................. libXYZ.so.1 -> libXYZ.so.1.5.3
................. libXYZ.so.1.5.3
................. pkgconfig
where ....... are some info like date and other things
Does this problem is caused due to the version number of libraries or what? how can i solve it?
libraries shared-library
libraries shared-library
asked Dec 28 '18 at 17:23
oscaralioscarali
61
asked Dec 28 '18 at 17:23
oscaralioscarali
61
asked Dec 28 '18 at 17:23
oscaralioscarali
61
asked Dec 28 '18 at 17:23
oscaralioscarali
61
asked Dec 28 '18 at 17:23
oscaralioscarali
61
61
1
I'd start by examining the output ofcmakeand/or theCMakeCache.txtfile to see what location (if any) was cached for the library. (I'm hazy on the details of how Cmake works, however it has its own rules for finding packages that may or may not involvepkg-config.)
– steeldriver
Dec 28 '18 at 18:22
@steeldriver i cheked it seems to be allright, however, i slightly summerized the quession in fact there are some packeges like xyz, tuv, mln, that are reqiured for W. However some of their libraries are also defined in the others for example xyz/lib has libxyz libtuv,.... can this be the cause of problem?
– oscarali
Dec 28 '18 at 18:51
Can you try withexport LIBRARY_PATH="installation path for XYZ/lib".
– Thomas
Dec 28 '18 at 18:53
@Thomas yes it did! Thanks it realy made me misreable during the past week! But how? What is difference? And also i have read library_path and ld-path are not good choices especially library path
– oscarali
Dec 28 '18 at 19:12
BasicallyLIBRARY_PATHis used during linking,LD_LIBRARY_PATHis used during runtime. But you will find enough resources with a search engine of your choice. Not sure why that should be considered not good. It would be better if theconfigurestep would provide such...
– Thomas
Dec 28 '18 at 19:26
add a comment |
1
I'd start by examining the output ofcmakeand/or theCMakeCache.txtfile to see what location (if any) was cached for the library. (I'm hazy on the details of how Cmake works, however it has its own rules for finding packages that may or may not involvepkg-config.)
– steeldriver
Dec 28 '18 at 18:22
@steeldriver i cheked it seems to be allright, however, i slightly summerized the quession in fact there are some packeges like xyz, tuv, mln, that are reqiured for W. However some of their libraries are also defined in the others for example xyz/lib has libxyz libtuv,.... can this be the cause of problem?
– oscarali
Dec 28 '18 at 18:51
Can you try withexport LIBRARY_PATH="installation path for XYZ/lib".
– Thomas
Dec 28 '18 at 18:53
@Thomas yes it did! Thanks it realy made me misreable during the past week! But how? What is difference? And also i have read library_path and ld-path are not good choices especially library path
– oscarali
Dec 28 '18 at 19:12
BasicallyLIBRARY_PATHis used during linking,LD_LIBRARY_PATHis used during runtime. But you will find enough resources with a search engine of your choice. Not sure why that should be considered not good. It would be better if theconfigurestep would provide such...
– Thomas
Dec 28 '18 at 19:26
1
1
I'd start by examining the output of
cmake and/or the CMakeCache.txt file to see what location (if any) was cached for the library. (I'm hazy on the details of how Cmake works, however it has its own rules for finding packages that may or may not involve pkg-config.)– steeldriver
Dec 28 '18 at 18:22
I'd start by examining the output of
cmake and/or the CMakeCache.txt file to see what location (if any) was cached for the library. (I'm hazy on the details of how Cmake works, however it has its own rules for finding packages that may or may not involve pkg-config.)– steeldriver
Dec 28 '18 at 18:22
@steeldriver i cheked it seems to be allright, however, i slightly summerized the quession in fact there are some packeges like xyz, tuv, mln, that are reqiured for W. However some of their libraries are also defined in the others for example xyz/lib has libxyz libtuv,.... can this be the cause of problem?
– oscarali
Dec 28 '18 at 18:51
@steeldriver i cheked it seems to be allright, however, i slightly summerized the quession in fact there are some packeges like xyz, tuv, mln, that are reqiured for W. However some of their libraries are also defined in the others for example xyz/lib has libxyz libtuv,.... can this be the cause of problem?
– oscarali
Dec 28 '18 at 18:51
Can you try with
export LIBRARY_PATH="installation path for XYZ/lib".– Thomas
Dec 28 '18 at 18:53
Can you try with
export LIBRARY_PATH="installation path for XYZ/lib".– Thomas
Dec 28 '18 at 18:53
@Thomas yes it did! Thanks it realy made me misreable during the past week! But how? What is difference? And also i have read library_path and ld-path are not good choices especially library path
– oscarali
Dec 28 '18 at 19:12
@Thomas yes it did! Thanks it realy made me misreable during the past week! But how? What is difference? And also i have read library_path and ld-path are not good choices especially library path
– oscarali
Dec 28 '18 at 19:12
Basically
LIBRARY_PATH is used during linking, LD_LIBRARY_PATH is used during runtime. But you will find enough resources with a search engine of your choice. Not sure why that should be considered not good. It would be better if the configure step would provide such...– Thomas
Dec 28 '18 at 19:26
Basically
LIBRARY_PATH is used during linking, LD_LIBRARY_PATH is used during runtime. But you will find enough resources with a search engine of your choice. Not sure why that should be considered not good. It would be better if the configure step would provide such...– Thomas
Dec 28 '18 at 19:26
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491338%2fcannot-find-libarary-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491338%2fcannot-find-libarary-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I'd start by examining the output of
cmakeand/or theCMakeCache.txtfile to see what location (if any) was cached for the library. (I'm hazy on the details of how Cmake works, however it has its own rules for finding packages that may or may not involvepkg-config.)– steeldriver
Dec 28 '18 at 18:22
@steeldriver i cheked it seems to be allright, however, i slightly summerized the quession in fact there are some packeges like xyz, tuv, mln, that are reqiured for W. However some of their libraries are also defined in the others for example xyz/lib has libxyz libtuv,.... can this be the cause of problem?
– oscarali
Dec 28 '18 at 18:51
Can you try with
export LIBRARY_PATH="installation path for XYZ/lib".– Thomas
Dec 28 '18 at 18:53
@Thomas yes it did! Thanks it realy made me misreable during the past week! But how? What is difference? And also i have read library_path and ld-path are not good choices especially library path
– oscarali
Dec 28 '18 at 19:12
Basically
LIBRARY_PATHis used during linking,LD_LIBRARY_PATHis used during runtime. But you will find enough resources with a search engine of your choice. Not sure why that should be considered not good. It would be better if theconfigurestep would provide such...– Thomas
Dec 28 '18 at 19:26