error compiling python, and "plat-linux2" versus "plat-linux3"

Robert P. J. Day rpjday at
Thu Aug 4 17:28:09 CEST 2011

  i may have asked about this once upon a time but i'm still fighting
with it so i'll throw myself on the mercy of the list and ask again.
(and if there's a better forum for this question, let me know.)

  i'm using the development environment wind river linux 4.2
(hereafter just "WRL") to configure and build an entire embedded
system, and that build is failing when it comes to compile
python-2.6.2.  i *think* i have an idea what the general problem is,
but i need help to narrow it down.

  here's the tail end of the build process:

===== begin snippet =====

Checking for unpackaged file(s): /home/rpjday/WindRiver/projects/42/glibc_std/host-cross/bin/../lib64/rpm/check-files /home/rpjday/WindRiver/projects/42/glibc_std/build/INSTALL_STAGE/python-2.6.2
error: Installed (but unpackaged) file(s) found:

RPM build errors:
    File not found: /home/rpjday/WindRiver/projects/42/glibc_std/build/INSTALL_STAGE/python-2.6.2/usr/lib64/python2.6/plat-linux2
    Installed (but unpackaged) file(s) found:
/home/rpjday/WindRiver/projects/42/glibc_std/scripts/ *** [python.install] Error 1
/home/rpjday/WindRiver/projects/42/glibc_std/scripts/ *** [python.buildlogger] Error 2
/home/rpjday/WindRiver/projects/42/glibc_std/scripts/Makefile.common.epilogue:37: *** [all] Error 2
GNUmakefile:55: *** [all] Error 2

#0  all at /home/rpjday/WindRiver/projects/42/glibc_std/build/GNUmakefile:55
remake[2]: Leaving directory `/home/rpjday/WindRiver/projects/42/glibc_std/build'
Command-line arguments:
Makefile:831: *** [all-recursive] Error 1

#0  all-recursive at /home/rpjday/WindRiver/projects/42/glibc_std/Makefile:831
remake[1]: Leaving directory `/home/rpjday/WindRiver/projects/42/glibc_std'
Command-line arguments:
make: *** [all] Error 2

===== end snippet =====

  note the references to "plat-linux3" above -- i think that's what's
killing me as i'm doing all this on a ubuntu 11.04 system with my own
hand-rolled 3.x kernel and i think there's a step in the python build
process that can't handle a running kernel with version "3.*".  this
is my suspicion as i've already found another location in the WRL
build that clearly never imagined it would be run on a 3.x kernel (it
recognized only "2.x" kernels as a hardcoded value.)

  another reason i think it's something like this is if i run just the
prep step -- that is, untar the python-2.6.2 tarball and apply the
WRL patches -- here's what i get in the resulting directory:

$ grep -r plat-linux2 *
Doc/install/index.rst:   ['', '/usr/local/lib/python2.3',
Doc/install/index.rst:'/www/python/lib/pythonX.Y/plat-linux2', ...]``.
Misc/HISTORY:	* Lib/plat-sunos5/, Lib/plat-linux2/
Misc/HISTORY:e.g. lib-tk, lib-stdwin, plat-win, plat-linux2,
plat-sunos5, dos-8x3.

  as you can see, it's all *hardcoded* references to "plat-linux2" so
it's a mystery as to where the references to "plat-linux3" are coming
from during the build process, which is why i suspect the reason i
gave above -- that nothing took into account that this build would be
done on a 3.x kernel.

  can anyone shed light on this?  can anyone else *try* this on a
system with a 3.x kernel and let me know what they get?  i'm about to
just hack the source and change that to "plat-linux3" to see what
happens, but it would be nice to do something more intelligent.



Robert P. J. Day                                 Ottawa, Ontario, CANADA


More information about the Python-list mailing list