On Mon, 2007-04-30 at 15:10 +0100, Martin Ritchie wrote:
> On 30/04/07, Gordon Sim <[EMAIL PROTECTED]> wrote:
> > Martin Ritchie wrote:
> > > Hey C++ fokes,
> > >
> > > I've been following the README but I've hit a sumbling block in
> > > building the C++ broker
> > >
> > > to summerize steps to this points
> > >
> > > Building on Dual Core Xeon under Fedora 6.
> > >
> > > Installed updates apr etc via yum.
> > >
> > > and used the autotools install script to download tools to ~/qpid-tools.
> > >
> > > then
> > > [EMAIL PROTECTED] cpp]$ ./bootstrap
> > > docs/api/Makefile.am:9: wildcard $(top_srcdir: non-POSIX variable name
> > > docs/api/Makefile.am:9: (probably a GNU make extension)
> > >
> > > Is this ok?
> >
> > Yes, that is ok.
> >
> > > and ./configure was quite happy
> > >
> > > but make gets upset about the file format of /usr/lib/libapr-1.so ..
> > > this is a sym-link to libapr-1.so.0.2.7
> > >
> > > I'm a bit rusty on the building of C++, Linux apps.
> > >
> > > Any thoughts? Do you need more info?
> >
> > Could the wrong build of apr perhaps have been installed? Sounds
> > unlikely if you used yum... Does 'apr-1-config --version' work? or
> > running ldd against /usr/lib/libapr-1.so?
> 
> Everything seems to be in place? Could it be a 64bit issue? I can't
> think why the binary file might be the "wrong format".
> 
> [EMAIL PROTECTED] java]$ apr-1-config --version
> 1.2.7
> [EMAIL PROTECTED] java]$ ldd /usr/lib/libapr-1.so
>         linux-gate.so.1 =>  (0xffffe000)
>         libuuid.so.1 => /lib/libuuid.so.1 (0xf7fb7000)
>         libcrypt.so.1 => /lib/libcrypt.so.1 (0xf7f89000)
>         libpthread.so.0 => /lib/libpthread.so.0 (0xf7f72000)
>         libdl.so.2 => /lib/libdl.so.2 (0xf7f6e000)
>         libc.so.6 => /lib/libc.so.6 (0xf7e30000)
>         /lib/ld-linux.so.2 (0x56555000)
> [EMAIL PROTECTED] java]$
> 

I think this is a 64bit problem, I've just started building on a 64bit
box and the "invalid format" for libraries is very familiar to me!

Is /usr/lib64/apr installed on your box? I don't really understand how
RPM manages 64 bit libs yet, you should have what looks like two copies
of the RPM installed, one of which has the 64bit libs.

Here's what I get on the 64bit box I build on: 

[EMAIL PROTECTED] ~]$ rpm -q apr
apr-1.2.7-11
apr-1.2.7-11
[EMAIL PROTECTED] ~]$ rpm -ql apr
/usr/lib/libapr-1.so.0
/usr/lib/libapr-1.so.0.2.7
/usr/share/doc/apr-1.2.7
/usr/share/doc/apr-1.2.7/CHANGES
/usr/share/doc/apr-1.2.7/LICENSE
/usr/share/doc/apr-1.2.7/NOTICE
/usr/lib64/libapr-1.so.0
/usr/lib64/libapr-1.so.0.2.7
/usr/share/doc/apr-1.2.7
/usr/share/doc/apr-1.2.7/CHANGES
/usr/share/doc/apr-1.2.7/LICENSE
/usr/share/doc/apr-1.2.7/NOTICE



Reply via email to