From: Jim Meyering <jim@meyering.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Avoid link failure...
Date: Sun, 21 Jun 2009 10:18:22 +0200 [thread overview]
Message-ID: <87k536q9td.fsf@meyering.net> (raw)
In-Reply-To: <1245520629.3665.343.camel@cerberus.int.fabbione.net> (Fabio M. Di Nitto's message of "Sat, 20 Jun 2009 19:57:09 +0200")
Fabio M. Di Nitto wrote:
...
>> > I am able to reproduce this error, but there is something that I don't
>> > like about it.
>> >
>> > When installing in different prefixes, isn't the user supposed to update
>> > LD_LIBRARY_PATH accordingly?
>> >
>> > Once I set LD_LIBRARY_PATH to include the new prefix, this error doesn't
>> > show because the linker can find libcoroipcc.
You're right.
I should have set LD_LIBRARY_PATH.
Thanks for keeping me honest ;-)
next prev parent reply other threads:[~2009-06-21 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 17:19 [Cluster-devel] [PATCH] Avoid link failure Jim Meyering
2009-06-20 12:32 ` Fabio M. Di Nitto
2009-06-20 16:23 ` Steven Dake
2009-06-20 17:57 ` Fabio M. Di Nitto
2009-06-21 8:18 ` Jim Meyering [this message]
2009-06-21 8:26 ` Fabio M. Di Nitto
2009-06-21 13:08 ` Jim Meyering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k536q9td.fsf@meyering.net \
--to=jim@meyering.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox