I was perusing the README file looking for clues why I'm suddenly unable to build on MacOSX when I noticed a platform note about Minix: Minix: When using ack, use "CC=cc AR=aal RANLIB=: ./configure"! I find it hard to believe Python actually still builds on Minix. On the other hand, I don't see it mentioned in PEP 11. Skip
Skip Montanaro
I was perusing the README file looking for clues why I'm suddenly unable to build on MacOSX when I noticed a platform note about Minix:
Minix: When using ack, use "CC=cc AR=aal RANLIB=: ./configure"!
I find it hard to believe Python actually still builds on Minix. On the other hand, I don't see it mentioned in PEP 11.
Offtopic: When I used minix, I wasn't aware of Python. And minix (the version I had) stopped working on recent PC's because there was a bug in the memory size calculation. The memory size was calculated modulo 16 MB, so it always complains that *no* memory was found. Funny! Thomas
Skip Montanaro
I find it hard to believe Python actually still builds on Minix. On the other hand, I don't see it mentioned in PEP 11.
Python's configure.in still as AC_MINIX, but I agree that that it is likely broken. Under PEP 11, we have to keep the support code in Python 2.3, and can only start removing it in Python 2.4. I've updated PEP 11 accordingly. Regards, Martin
>> I find it hard to believe Python actually still builds on Minix. On >> the other hand, I don't see it mentioned in PEP 11. Martin> Python's configure.in still as AC_MINIX, but I agree that that Martin> it is likely broken. Under PEP 11, we have to keep the support Martin> code in Python 2.3, and can only start removing it in Python Martin> 2.4. I've updated PEP 11 accordingly. So, one of the first things we should do after 2.3 is released is make a pass through PEP 11 and unsupport a bunch of stuff. I just deleted the reference in the README file. Skip
Skip Montanaro
So, one of the first things we should do after 2.3 is released is make a pass through PEP 11 and unsupport a bunch of stuff. I just deleted the reference in the README file.
Actually, *before* 2.3, we will need to add warnings. So anybody using one of the unsupported systems will get a build failure, and thus can step forward to maintain that port. In 2.3, it will be easy to restore the support: Just remove the build failure. In 2.4, the maintainer would have to produce some larger patch, restoring the removed code, and likely fixing it. I don't really expect anybody to step forward, atleast in one case, the user decided that a system upgrade (from SunOS 4 to Solaris) would be easier. But we do need to give users a chance, since experience tells that users want support for strange systems. In the specific case of Minix build instructions, it is probably ok that it is removed already, but I'd like to ask everybody to stick to the plan of PEP 11. Regards, Martin
participants (3)
-
martin@v.loewis.de
-
Skip Montanaro
-
Thomas Heller