Setting LD_LIBRARY_PATH before running an app from a terminal has no effect
I have several builds of an application on my system (a dev build and many older released builds). When I'm trying to run an older release, the system invariably picks up the dynamic libraries from the dev build.
From /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin which is the directory of the older release I'm trying to run:
$ ldd appleseed.studio
[stuff omitted]
libappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fbcb090b000)
libappleseed.shared.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed.shared/libappleseed.shared.so (0x00007fbcb030c000)
[more stuff omitted]
(/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/ is the path to my dev build.)
Naturally I should set LD_LIBRARY_PATH correctly before running an older release:
$ export LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ; ./appleseed.studio
(LD_LIBRARY_PATH is initially empty so I don't bother with concatenation.)
However this doesn't work and the system continues to pick up the dev build of the dynamic libraries.
Am I doing something wrong? Any idea?
I am running a 64-bit build of Ubuntu 10.10 Maverick Meerkat (unsupported as of April 2012).
UPDATE: I have updated my system to Ubuntu 11.10 (Natty) and the problem persists.
shared-library
asked Sep 13 '12 at 11:01
François BeauneFrançois Beaune
11615
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have several builds of an application on my system (a dev build and many older released builds). When I'm trying to run an older release, the system invariably picks up the dynamic libraries from the dev build.
From /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin which is the directory of the older release I'm trying to run:
$ ldd appleseed.studio
[stuff omitted]
libappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fbcb090b000)
libappleseed.shared.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed.shared/libappleseed.shared.so (0x00007fbcb030c000)
[more stuff omitted]
(/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/ is the path to my dev build.)
Naturally I should set LD_LIBRARY_PATH correctly before running an older release:
$ export LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ; ./appleseed.studio
(LD_LIBRARY_PATH is initially empty so I don't bother with concatenation.)
However this doesn't work and the system continues to pick up the dev build of the dynamic libraries.
Am I doing something wrong? Any idea?
I am running a 64-bit build of Ubuntu 10.10 Maverick Meerkat (unsupported as of April 2012).
UPDATE: I have updated my system to Ubuntu 11.10 (Natty) and the problem persists.
shared-library
asked Sep 13 '12 at 11:01
François BeauneFrançois Beaune
11615
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
What doesfile .../libappleseed.sooutput? Maybe you are trying to use an old 32-bit library with your new 64-bt binary.
– Lekensteyn
Sep 13 '12 at 11:10
Everything is 64-bit:$ file ./libappleseed.soreturns./libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped, while$ file /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.soreturns/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped.
– François Beaune
Sep 13 '12 at 11:22
Ok, then you might want to check whetherlddstill reports the other paths withLD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studio
– Lekensteyn
Sep 13 '12 at 20:25
Unfortunately, it doesn't:LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studioreturnslibappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fc27cce5000). I am at loss here. It looks like theLD_LIBRARY_PATHmechanism is somehow disabled on my system.
– François Beaune
Sep 14 '12 at 9:20
add a comment |
I have several builds of an application on my system (a dev build and many older released builds). When I'm trying to run an older release, the system invariably picks up the dynamic libraries from the dev build.
From /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin which is the directory of the older release I'm trying to run:
$ ldd appleseed.studio
[stuff omitted]
libappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fbcb090b000)
libappleseed.shared.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed.shared/libappleseed.shared.so (0x00007fbcb030c000)
[more stuff omitted]
(/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/ is the path to my dev build.)
Naturally I should set LD_LIBRARY_PATH correctly before running an older release:
$ export LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ; ./appleseed.studio
(LD_LIBRARY_PATH is initially empty so I don't bother with concatenation.)
However this doesn't work and the system continues to pick up the dev build of the dynamic libraries.
Am I doing something wrong? Any idea?
I am running a 64-bit build of Ubuntu 10.10 Maverick Meerkat (unsupported as of April 2012).
UPDATE: I have updated my system to Ubuntu 11.10 (Natty) and the problem persists.
shared-library
asked Sep 13 '12 at 11:01
François BeauneFrançois Beaune
11615
I have several builds of an application on my system (a dev build and many older released builds). When I'm trying to run an older release, the system invariably picks up the dynamic libraries from the dev build.
From /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin which is the directory of the older release I'm trying to run:
$ ldd appleseed.studio
[stuff omitted]
libappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fbcb090b000)
libappleseed.shared.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed.shared/libappleseed.shared.so (0x00007fbcb030c000)
[more stuff omitted]
(/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/ is the path to my dev build.)
Naturally I should set LD_LIBRARY_PATH correctly before running an older release:
$ export LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ; ./appleseed.studio
(LD_LIBRARY_PATH is initially empty so I don't bother with concatenation.)
However this doesn't work and the system continues to pick up the dev build of the dynamic libraries.
Am I doing something wrong? Any idea?
I am running a 64-bit build of Ubuntu 10.10 Maverick Meerkat (unsupported as of April 2012).
UPDATE: I have updated my system to Ubuntu 11.10 (Natty) and the problem persists.
shared-library
shared-library
asked Sep 13 '12 at 11:01
François BeauneFrançois Beaune
11615
asked Sep 13 '12 at 11:01
François BeauneFrançois Beaune
11615
edited Sep 14 '12 at 9:21
François Beaune
asked Sep 13 '12 at 11:01
François BeauneFrançois Beaune
11615
asked Sep 13 '12 at 11:01
François BeauneFrançois Beaune
11615
asked Sep 13 '12 at 11:01
François BeauneFrançois Beaune
11615
11615
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
What doesfile .../libappleseed.sooutput? Maybe you are trying to use an old 32-bit library with your new 64-bt binary.
– Lekensteyn
Sep 13 '12 at 11:10
Everything is 64-bit:$ file ./libappleseed.soreturns./libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped, while$ file /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.soreturns/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped.
– François Beaune
Sep 13 '12 at 11:22
Ok, then you might want to check whetherlddstill reports the other paths withLD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studio
– Lekensteyn
Sep 13 '12 at 20:25
Unfortunately, it doesn't:LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studioreturnslibappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fc27cce5000). I am at loss here. It looks like theLD_LIBRARY_PATHmechanism is somehow disabled on my system.
– François Beaune
Sep 14 '12 at 9:20
add a comment |
What doesfile .../libappleseed.sooutput? Maybe you are trying to use an old 32-bit library with your new 64-bt binary.
– Lekensteyn
Sep 13 '12 at 11:10
Everything is 64-bit:$ file ./libappleseed.soreturns./libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped, while$ file /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.soreturns/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped.
– François Beaune
Sep 13 '12 at 11:22
Ok, then you might want to check whetherlddstill reports the other paths withLD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studio
– Lekensteyn
Sep 13 '12 at 20:25
Unfortunately, it doesn't:LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studioreturnslibappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fc27cce5000). I am at loss here. It looks like theLD_LIBRARY_PATHmechanism is somehow disabled on my system.
– François Beaune
Sep 14 '12 at 9:20
What does
file .../libappleseed.so output? Maybe you are trying to use an old 32-bit library with your new 64-bt binary.– Lekensteyn
Sep 13 '12 at 11:10
What does
file .../libappleseed.so output? Maybe you are trying to use an old 32-bit library with your new 64-bt binary.– Lekensteyn
Sep 13 '12 at 11:10
Everything is 64-bit:
$ file ./libappleseed.so returns ./libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped, while $ file /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so returns /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped.– François Beaune
Sep 13 '12 at 11:22
Everything is 64-bit:
$ file ./libappleseed.so returns ./libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped, while $ file /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so returns /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped.– François Beaune
Sep 13 '12 at 11:22
Ok, then you might want to check whether
ldd still reports the other paths with LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studio– Lekensteyn
Sep 13 '12 at 20:25
Ok, then you might want to check whether
ldd still reports the other paths with LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studio– Lekensteyn
Sep 13 '12 at 20:25
Unfortunately, it doesn't:
LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studio returns libappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fc27cce5000). I am at loss here. It looks like the LD_LIBRARY_PATH mechanism is somehow disabled on my system.– François Beaune
Sep 14 '12 at 9:20
Unfortunately, it doesn't:
LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studio returns libappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fc27cce5000). I am at loss here. It looks like the LD_LIBRARY_PATH mechanism is somehow disabled on my system.– François Beaune
Sep 14 '12 at 9:20
add a comment |
1 Answer
1
active
oldest
votes
Make sure that under
/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin
you really have the shared libraries you want to load. Are they really in the
bin/directory of the archive? Notlib/?
Try
/lib/ld-linux.so.2 --library-path /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ./appleseed.studio
You can use the options from that program to control and debug the library loading process.
answered Sep 13 '12 at 11:40
JanuaryJanuary
25.3k106788
Absolutely, thebin/directory does contain the shared libraries I want to load. Is/lib/ld-linux.so.2supposed to be an executable binary? I haven't got it in my system.
– François Beaune
Sep 13 '12 at 11:56
OK, it seems to be Linux's dynamic linker: kernel.org/doc/man-pages/online/pages/man8/ld.so.8.html. Seems like I should be able to install it via the package manager.
– François Beaune
Sep 13 '12 at 12:04
Can't seem to findld-linux-so.2,ld-linux.soorld.soin the package list or viaapt-get.
– François Beaune
Sep 13 '12 at 12:08
The dynamic linker seems to be calledld-linux-x86-64.so.2on my system. So if I run the command you suggested, appleseed.studio starts but immediately complains that it isn't started from thebin/directory of its installation.
– François Beaune
Sep 13 '12 at 12:32
1
Hehe, thanks for the link. I am actually the author of appleseed :)
– François Beaune
Sep 13 '12 at 12:40
|
show 5 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f187286%2fsetting-ld-library-path-before-running-an-app-from-a-terminal-has-no-effect%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Make sure that under
/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin
you really have the shared libraries you want to load. Are they really in the
bin/directory of the archive? Notlib/?
Try
/lib/ld-linux.so.2 --library-path /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ./appleseed.studio
You can use the options from that program to control and debug the library loading process.
answered Sep 13 '12 at 11:40
JanuaryJanuary
25.3k106788
Absolutely, thebin/directory does contain the shared libraries I want to load. Is/lib/ld-linux.so.2supposed to be an executable binary? I haven't got it in my system.
– François Beaune
Sep 13 '12 at 11:56
OK, it seems to be Linux's dynamic linker: kernel.org/doc/man-pages/online/pages/man8/ld.so.8.html. Seems like I should be able to install it via the package manager.
– François Beaune
Sep 13 '12 at 12:04
Can't seem to findld-linux-so.2,ld-linux.soorld.soin the package list or viaapt-get.
– François Beaune
Sep 13 '12 at 12:08
The dynamic linker seems to be calledld-linux-x86-64.so.2on my system. So if I run the command you suggested, appleseed.studio starts but immediately complains that it isn't started from thebin/directory of its installation.
– François Beaune
Sep 13 '12 at 12:32
1
Hehe, thanks for the link. I am actually the author of appleseed :)
– François Beaune
Sep 13 '12 at 12:40
|
show 5 more comments
Make sure that under
/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin
you really have the shared libraries you want to load. Are they really in the
bin/directory of the archive? Notlib/?
Try
/lib/ld-linux.so.2 --library-path /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ./appleseed.studio
You can use the options from that program to control and debug the library loading process.
answered Sep 13 '12 at 11:40
JanuaryJanuary
25.3k106788
Absolutely, thebin/directory does contain the shared libraries I want to load. Is/lib/ld-linux.so.2supposed to be an executable binary? I haven't got it in my system.
– François Beaune
Sep 13 '12 at 11:56
OK, it seems to be Linux's dynamic linker: kernel.org/doc/man-pages/online/pages/man8/ld.so.8.html. Seems like I should be able to install it via the package manager.
– François Beaune
Sep 13 '12 at 12:04
Can't seem to findld-linux-so.2,ld-linux.soorld.soin the package list or viaapt-get.
– François Beaune
Sep 13 '12 at 12:08
The dynamic linker seems to be calledld-linux-x86-64.so.2on my system. So if I run the command you suggested, appleseed.studio starts but immediately complains that it isn't started from thebin/directory of its installation.
– François Beaune
Sep 13 '12 at 12:32
1
Hehe, thanks for the link. I am actually the author of appleseed :)
– François Beaune
Sep 13 '12 at 12:40
|
show 5 more comments
Make sure that under
/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin
you really have the shared libraries you want to load. Are they really in the
bin/directory of the archive? Notlib/?
Try
/lib/ld-linux.so.2 --library-path /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ./appleseed.studio
You can use the options from that program to control and debug the library loading process.
answered Sep 13 '12 at 11:40
JanuaryJanuary
25.3k106788
Make sure that under
/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin
you really have the shared libraries you want to load. Are they really in the
bin/directory of the archive? Notlib/?
Try
/lib/ld-linux.so.2 --library-path /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ./appleseed.studio
You can use the options from that program to control and debug the library loading process.
answered Sep 13 '12 at 11:40
JanuaryJanuary
25.3k106788
answered Sep 13 '12 at 11:40
JanuaryJanuary
25.3k106788
answered Sep 13 '12 at 11:40
JanuaryJanuary
25.3k106788
answered Sep 13 '12 at 11:40
JanuaryJanuary
25.3k106788
25.3k106788
Absolutely, thebin/directory does contain the shared libraries I want to load. Is/lib/ld-linux.so.2supposed to be an executable binary? I haven't got it in my system.
– François Beaune
Sep 13 '12 at 11:56
OK, it seems to be Linux's dynamic linker: kernel.org/doc/man-pages/online/pages/man8/ld.so.8.html. Seems like I should be able to install it via the package manager.
– François Beaune
Sep 13 '12 at 12:04
Can't seem to findld-linux-so.2,ld-linux.soorld.soin the package list or viaapt-get.
– François Beaune
Sep 13 '12 at 12:08
The dynamic linker seems to be calledld-linux-x86-64.so.2on my system. So if I run the command you suggested, appleseed.studio starts but immediately complains that it isn't started from thebin/directory of its installation.
– François Beaune
Sep 13 '12 at 12:32
1
Hehe, thanks for the link. I am actually the author of appleseed :)
– François Beaune
Sep 13 '12 at 12:40
|
show 5 more comments
Absolutely, thebin/directory does contain the shared libraries I want to load. Is/lib/ld-linux.so.2supposed to be an executable binary? I haven't got it in my system.
– François Beaune
Sep 13 '12 at 11:56
OK, it seems to be Linux's dynamic linker: kernel.org/doc/man-pages/online/pages/man8/ld.so.8.html. Seems like I should be able to install it via the package manager.
– François Beaune
Sep 13 '12 at 12:04
Can't seem to findld-linux-so.2,ld-linux.soorld.soin the package list or viaapt-get.
– François Beaune
Sep 13 '12 at 12:08
The dynamic linker seems to be calledld-linux-x86-64.so.2on my system. So if I run the command you suggested, appleseed.studio starts but immediately complains that it isn't started from thebin/directory of its installation.
– François Beaune
Sep 13 '12 at 12:32
1
Hehe, thanks for the link. I am actually the author of appleseed :)
– François Beaune
Sep 13 '12 at 12:40
Absolutely, the
bin/ directory does contain the shared libraries I want to load. Is /lib/ld-linux.so.2 supposed to be an executable binary? I haven't got it in my system.– François Beaune
Sep 13 '12 at 11:56
Absolutely, the
bin/ directory does contain the shared libraries I want to load. Is /lib/ld-linux.so.2 supposed to be an executable binary? I haven't got it in my system.– François Beaune
Sep 13 '12 at 11:56
OK, it seems to be Linux's dynamic linker: kernel.org/doc/man-pages/online/pages/man8/ld.so.8.html. Seems like I should be able to install it via the package manager.
– François Beaune
Sep 13 '12 at 12:04
OK, it seems to be Linux's dynamic linker: kernel.org/doc/man-pages/online/pages/man8/ld.so.8.html. Seems like I should be able to install it via the package manager.
– François Beaune
Sep 13 '12 at 12:04
Can't seem to find
ld-linux-so.2, ld-linux.so or ld.so in the package list or via apt-get.– François Beaune
Sep 13 '12 at 12:08
Can't seem to find
ld-linux-so.2, ld-linux.so or ld.so in the package list or via apt-get.– François Beaune
Sep 13 '12 at 12:08
The dynamic linker seems to be called
ld-linux-x86-64.so.2 on my system. So if I run the command you suggested, appleseed.studio starts but immediately complains that it isn't started from the bin/ directory of its installation.– François Beaune
Sep 13 '12 at 12:32
The dynamic linker seems to be called
ld-linux-x86-64.so.2 on my system. So if I run the command you suggested, appleseed.studio starts but immediately complains that it isn't started from the bin/ directory of its installation.– François Beaune
Sep 13 '12 at 12:32
1
1
Hehe, thanks for the link. I am actually the author of appleseed :)
– François Beaune
Sep 13 '12 at 12:40
Hehe, thanks for the link. I am actually the author of appleseed :)
– François Beaune
Sep 13 '12 at 12:40
|
show 5 more comments
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f187286%2fsetting-ld-library-path-before-running-an-app-from-a-terminal-has-no-effect%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
What does
file .../libappleseed.sooutput? Maybe you are trying to use an old 32-bit library with your new 64-bt binary.– Lekensteyn
Sep 13 '12 at 11:10
Everything is 64-bit:
$ file ./libappleseed.soreturns./libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped, while$ file /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.soreturns/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped.– François Beaune
Sep 13 '12 at 11:22
Ok, then you might want to check whether
lddstill reports the other paths withLD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studio– Lekensteyn
Sep 13 '12 at 20:25
Unfortunately, it doesn't:
LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ldd ./appleseed.studioreturnslibappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fc27cce5000). I am at loss here. It looks like theLD_LIBRARY_PATHmechanism is somehow disabled on my system.– François Beaune
Sep 14 '12 at 9:20