[Pvfs2-users] Compiling PVFS 2.6.0 on Suse 10.1 PPC
ckirby3 at colsa.com
Mon Dec 4 12:57:30 EST 2006
Thanks for the quick reply. I tried the settings as you mentioned and had a
problem with the GNU linker. The version of ld is 18.104.22.168.5.
ld: unrecognised emulation mode: 64
Supported emulations: elf32ppclinux elf32ppc elf32ppcsim elf64alpha alpha
armelf_linux armelf hppalinux elf_i386 i386linux elf64_ia64 m68kelf
m68klinux elf64ppc elf_s390 elf64_s390 elf32_sparc sparclinux elf64_sparc
sun4 elf_x86_64 ppcmacos
make: *** [/home/trip3/pvfs-2.6.0/src/kernel/linux-2.6/pvfs2.o] Error 1
make: *** [_module_/home/trip3/pvfs-2.6.0/src/kernel/linux-2.6] Error 2
make: *** [default] Error 2
make: *** [just_kmod] Error 2
Looking at the ld man pages I changed LDFLAGS to -melf64ppc but that did not
> On Mon, Dec 04, 2006 at 11:06:05AM -0600, Kirby Cliff wrote:
>> I have tried the configure script from CVS and the one included. My
>> configure line has the correct kernel source, /configure
>> --with-kernel=/usr/src/linux-22.214.171.124-0.25 --without-openssl
> Your platform and the warnings you are seeing are unfortunately quite common
> on ppc 970 machines, especially when the compiler and toolchain is "biarch"
> -- able to produce 32 or 64 bit executables.
> the PVFS configure script is testing for kernel features, and is probably
> doing so with the compiler in 32 bit mode. Your kernel, however, is 64 bit,
> and all the linux kernel header files are created accordingly.
> To fix this problem, add "-m64" to your CFLAGS and LDFLAGS and re-run
> If you find you do not have the 64 bit versions of the berkely db, that's
> ok. You only need those to make the pvfs server, so when you configure for
> the kernel module you can pass --disable-server.
> Let us know if that doesn't do the trick.
More information about the Pvfs2-users