>>>>> On Wed, 11 Aug 2010 01:17:11 -0300, Daniel Bareiro said:
> 
> On Wednesday, 11 August 2010 00:46:06 -0300,
> Daniel Bareiro wrote:
> 
> > > It looks like you are running a 64-bit bacula-sd, so the libraries
> > > should be in /usr/lib64.
> > > 
> > > The files you found are in /usr/lib, which are normally 32-bit.
> > > Either you have the 32-bit libraries installed by accident or the
> > > 64-bit libraries are installed in the wrong place (broken rpm?).
> 
> > Indeed, I'm using CentOS 5.5 amd64. I was not doing the installation
> > with RPM packages, but compile the source code obtained at the
> > official site of Bacula. On sunday, doing tests comparing with the
> > installation done with packages RPM, I realized that the difference
> > was in which the libraries were in /usr/lib64.
> > 
> > Doing again the configuration using this time the --libdir=/usr/lib64
> > parameter, the problem was not reproduced. What it is strange to me is
> > that in an installation of Debian Lenny amd64, I didn't do the
> > configuration using --libdir=/usr/lib64 and in spite of putting the
> > libraries in /usr/lib, I did not have the problem occurred in CentOS.
> 
> I already found the cause:
> 
> # ll /usr/lib
> lib/   lib32/ lib64/
> # ll -d /usr/lib
> drwxr-xr-x 41 root root 20480 ago  8 01:56 /usr/lib
> # ll -d /usr/lib32
> lrwxrwxrwx 1 root root 24 abr 11  2009 /usr/lib32 -> /emul/ia32-linux/usr/lib
> # ll -d /usr/lib64
> lrwxrwxrwx 1 root root 3 abr 11  2009 /usr/lib64 -> lib

Yes, 64-bit Debian and 64-bit CentOS use different layouts for the lib
directories.

__Martin

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users