Dustin,
Thank you - failure to read critically, I had to install an updated
curl on the system .2 needed .4, and I was just looking for
unresolved libraries, didn't take the next step.
Thank you, will update and try again.
I'm not sure I understand where this came from though...
something in
Dustin,
I used the same directory and ported the structure to the
new system to run the install, but I rebuilt it and must
have had the libraries incorrect since there there 3 library
problems with the same issue, as well and amcheck itself.
I seem to be up and running now, amlabel runs and
On Curie, I did a make clean in /tmp/ivan/amanda-261-patched/amandad-src
and then a make.
Checking ./.libs/amandad I find no evidence of the 2.4.5 library.
[curie]: /usr/tmp/ivan/amanda-261-patched/amandad-src/.libs ldd amandad |
grep liba
libamandad-2.6.1p1.so =
I'm not at all certain I understand this.
[curie] /usr/local/libexec/amanda 2 hostname
curie
[curie] /usr/local/libexec/amanda 3 pwd
curie:/usr/local/libexec/amanda
[curie] /usr/local/libexec/amanda 4 ldd amandad
libamandad-2.6.1p1.so =
On Fri, Aug 14, 2009 at 1:22 PM, Brian Cuttlerbr...@wadsworth.org wrote:
They look like the same binary but don't act like the same binary.
This is really best handled by those who are skilled in the ways of
Solaris -- the operating system has lots of weird behaviors with
regard to linking.
Chris,
We will remove the old libraries, that should take care of it.
for completeness though, I just don't understand why
we get two different results in the same binary ?
Actually, for the binary on Curie we only search for
object=libamandad-2.6.1p1.so, where on Cascade we
seem to be
Brian Cuttler wrote:
Chris,
We will remove the old libraries, that should take care of it.
for completeness though, I just don't understand why
we get two different results in the same binary ?
Actually, for the binary on Curie we only search for
object=libamandad-2.6.1p1.so, where on
Dustin J. Mitchell wrote:
On Fri, Aug 14, 2009 at 1:22 PM, Brian Cuttlerbr...@wadsworth.org wrote:
They look like the same binary but don't act like the same binary.
This is really best handled by those who are skilled in the ways of
Solaris -- the operating system has lots of weird
I've copied my installation from Solaris 10x86 to another
solaris 10x86 (2.6.1 with patches).
Seemed to be ok, all load libraries present, but an error when
I try to run amlabel.
The named .so file is present, the correct version of Perl seems
to be there...
ls -l
On Thu, Aug 13, 2009 at 3:40 PM, Brian Cuttlerbr...@wadsworth.org wrote:
I'm sure its something minor...but I'm not seeing it.
libDebug.so should require libamanda.so -- is that requirement in
place? and satisfied?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Thu, Aug 13, 2009 at 4:45 PM, Brian Cuttlerbr...@wadsworth.org wrote:
I installed on Cascade using the compilation that I created for/on Curie.
The # make install seemed to go well.
Try running ldd on libDebug.so?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Thu, Aug 13, 2009 at 5:08 PM, Brian Cuttlerbr...@wadsworth.org wrote:
[cascade]: /usr/local/lib/amanda ldd
/usr/perl5/site_perl/5.8.4/auto/Amanda/Debug/libDebug.so
...
libamanda-2.4.5.so = /opt/sfw/lib/libamanda-2.4.5.so
There's your problem right there.. it looks like
On Thu, Aug 13, 2009 at 05:02:12PM -0400, Dustin J. Mitchell wrote:
On Thu, Aug 13, 2009 at 4:45 PM, Brian Cuttlerbr...@wadsworth.org wrote:
I installed on Cascade using the compilation that I created for/on Curie.
The # make install seemed to go well.
Try running ldd on libDebug.so?
Dustin,
On Thu, Aug 13, 2009 at 03:52:23PM -0400, Dustin J. Mitchell wrote:
On Thu, Aug 13, 2009 at 3:40 PM, Brian Cuttlerbr...@wadsworth.org wrote:
I'm sure its something minor...but I'm not seeing it.
libDebug.so should require libamanda.so -- is that requirement in
place? and
14 matches
Mail list logo
