| 1 |
dev-lang/python-3.1.2-r3 has been stabilised, but python-2.6 is still |
| 2 |
the 'active' interpretter and is used by portage when building outside |
| 3 |
catalyst. However catalyst is using python-3.1 in its chroot when |
| 4 |
building stages. On an amd64 system, stages 1 & 2 built with no problems |
| 5 |
but the stage3 build is failing to build cracklib with a python error |
| 6 |
|
| 7 |
x86_64-pc-linux-gnu-gcc -shared .libs/_cracklibmodule.o -L/var/tmp/portage/sys-libs/cracklib-2.8.15/image//usr/lib64 -L/usr/lib64 -lcrack -lpython3.1 -lz -march=nocona -Wl,-O1 -Wl,-soname -Wl,_cracklibmodule.so -o .libs/_cracklibmodule.so |
| 8 |
/usr/bin/install -c .libs/_cracklibmodule.soT /var/tmp/portage/sys-libs/cracklib-2.8.15/image//usr/lib64/python3.1/site-packages/_cracklibmodule.so |
| 9 |
/usr/bin/install -c .libs/_cracklibmodule.lai /var/tmp/portage/sys-libs/cracklib-2.8.15/image//usr/lib64/python3.1/site-packages/_cracklibmodule.la |
| 10 |
/usr/bin/install -c .libs/_cracklibmodule.a /var/tmp/portage/sys-libs/cracklib-2.8.15/image//usr/lib64/python3.1/site-packages/_cracklibmodule.a |
| 11 |
chmod 644 /var/tmp/portage/sys-libs/cracklib-2.8.15/image//usr/lib64/python3.1/site-packages/_cracklibmodule.a |
| 12 |
x86_64-pc-linux-gnu-ranlib /var/tmp/portage/sys-libs/cracklib-2.8.15/image//usr/lib64/python3.1/site-packages/_cracklibmodule.a |
| 13 |
libtool: install: warning: remember to run `libtool --finish /usr/lib64/python3.1/site-packages' |
| 14 |
test -z "/usr/lib64/python3.1/site-packages" || /bin/mkdir -p "/var/tmp/portage/sys-libs/cracklib-2.8.15/image//usr/lib64/python3.1/site-packages" |
| 15 |
/usr/bin/install -c -m 644 'cracklib.py' '/var/tmp/portage/sys-libs/cracklib-2.8.15/image//usr/lib64/python3.1/site-packages/cracklib.py' |
| 16 |
File "<string>", line 6 |
| 17 |
print 'Byte-compiling python modules...' |
| 18 |
^ |
| 19 |
SyntaxError: invalid syntax |
| 20 |
make[2]: *** [install-pythonPYTHON] Error 1 |
Archives