Incidentally the method mentioned on python.org for enabling LFS doesn't work; adding the following to config.h does, however: #define LARGEFILE_SOURCE 1 #define _FILE_OFFSET_BITS 64 And don't forget to ./configure --without-pymalloc and --with-threads, too. seb On Wed, 2002-02-06 at 17:44, Andreas Jung wrote:
compilesz.py only byte-compiles the .py files but does has nothing to do with the built-in LFS support. So your solution is to grab the Python sources, check how to enable LFS support (at least for 2.1.X) and then compile and install it.
-aj
----- Original Message ----- From: "marc lindahl" <marc@bowery.com> To: "Andreas Jung" <andreas@zope.com>; <zope@zope.org> Sent: Thursday, February 07, 2002 13:43 Subject: Re: [Zope] how to enable Large File Support with 2.5 release?
Doesn't compilezpy.py make the python binary when you install? (also, for future, I noticed that python 2.2 is supposed to auto-detect during build?)
From: "Andreas Jung" <andreas@zope.com> Organization: Zope Corporation Reply-To: "Andreas Jung" <andreas@zope.com> Date: Wed, 6 Feb 2002 12:31:18 -0500 To: "marc lindahl" <marc@bowery.com>, <zope@zope.org> Subject: Re: [Zope] how to enable Large File Support with 2.5 release?
You have to build Python from scratch because LFS depends on your operating system and a pre-built Python binary with LFS enabled might not run on a system that has no LFS support.
- aj
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )