[Python-Dev] Python 2.0 beta 2 pre-release

[Fred L. Drake, Jr.]

Neil Schemenauer writes:
 > I don't know much but having the output from "uname -a" and "ldd python"
 > could be helpful (ie. which kernel and which libc).

Under SuSE 6.3, uname -a says:
Linux linux1.compile.sourceforge.net 2.2.14-5.0.14smp #1 SMP Sun Mar 26 13:03:52 PST 2000 i686 unknown

ldd ./python says:
	libdb.so.3 => /lib/libdb.so.3 (0x4001d000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x4005c000)
	libdl.so.2 => /lib/libdl.so.2 (0x4006e000)
	libutil.so.1 => /lib/libutil.so.1 (0x40071000)
	libm.so.6 => /lib/libm.so.6 (0x40075000)
	libc.so.6 => /lib/libc.so.6 (0x40092000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

Under Caldera 2.3, uname -a says:
Linux linux1.compile.sourceforge.net 2.2.14-5.0.14smp #1 SMP Sun Mar 26 13:03:52 PST 2000 i686 unknown

ldd ./python says:
	libdb.so.3 => /lib/libdb.so.3 (0x4001a000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x40055000)
	libdl.so.2 => /lib/libdl.so.2 (0x40066000)
	libutil.so.1 => /lib/libutil.so.1 (0x4006a000)
	libm.so.6 => /lib/libm.so.6 (0x4006d000)
	libc.so.6 => /lib/libc.so.6 (0x4008a000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

  Now, it may be that something strange is going on since these are
the "virtual environments" on SourceForge.  I'm not sure these are
really the same thing as running those systems.  I'm looking at the
script to start SuSE; there's nothing really there but a chroot call;
perhaps there's a kernel/library mismatch?
  I'll have to see ask about how these are supposed to work a little
more; kernel/libc mismatches could be a real problem in this
environment.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member