Issues compiling with large file support

Discussion in 'Python' started by pruebauno, Jul 15, 2005.

  1. pruebauno

    pruebauno Guest

    Hello all,
    I am having issues compiling Python with large file support. I tried
    forcing the configure script to add it but then it bombs in the make
    process. Any help will be appreciated.

    Information:
    Architecture:
    PowerPc on AIX version 5

    Compiler:
    VisualAge C++ Professional / C for AIX Compiler, Version 6

    Python version:
    Python 2.4.1

    Error Message:
    cc_r -c -DNDEBUG -g -O2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
    -I
    .. -I./Include -DPy_BUILD_CORE -o Objects/fileobject.o
    Objects/fileobject.c
    "Objects/fileobject.c", line 382.2: 1506-205 (S) #error "Large file
    support, but neither off_t nor fpos_t is large enough."
    "Objects/fileobject.c", line 389.27: 1506-046 (S) Syntax error.
    "Objects/fileobject.c", line 423.2: 1506-205 (S) #error "Large file
    support, but no way to fseek."
    "Objects/fileobject.c", line 431.8: 1506-166 (S) Definition of function
    Py_off_t requires parentheses.
    "Objects/fileobject.c", line 432.1: 1506-276 (S) Syntax error: possible
    missing
    '{'?"Objects/fileobject.c", line 446.2: 1506-205 (S) #error "Large file
    support, but no way to ftell."
    "Objects/fileobject.c", line 456.18: 1506-275 (S) Unexpected text
    offset encountered.
    "Objects/fileobject.c", line 456.9: 1506-045 (S) Undeclared identifier
    Py_off_t.
    "Objects/fileobject.c", line 468.9: 1506-045 (S) Undeclared identifier
    offset.
    "Objects/fileobject.c", line 476.48: 1506-099 (S) Unexpected argument.
    "Objects/fileobject.c", line 494.18: 1506-275 (S) Unexpected text
    newsize encountered.
    "Objects/fileobject.c", line 494.9: 1506-045 (S) Undeclared identifier
    Py_off_t.
    "Objects/fileobject.c", line 496.18: 1506-275 (S) Unexpected text
    initialpos encountered.
    "Objects/fileobject.c", line 513.9: 1506-045 (S) Undeclared identifier
    initialpos.
    "Objects/fileobject.c", line 525.17: 1506-045 (S) Undeclared identifier
    newsize.
    "Objects/fileobject.c", line 586.52: 1506-099 (S) Unexpected argument.
    "Objects/fileobject.c", line 604.18: 1506-275 (S) Unexpected text pos
    encountered.
    "Objects/fileobject.c", line 604.9: 1506-045 (S) Undeclared identifier
    Py_off_t.
    "Objects/fileobject.c", line 610.9: 1506-045 (S) Undeclared identifier
    pos.
    make: 1254-004 The error code from the last command is 1.

    Stop.


    More info:

    checking MACHDEP... aix5
    checking EXTRAPLATDIR...
    checking for --without-gcc...
    checking for --with-cxx=<compiler>... no
    checking for c++... no
    checking for g++... no
    checking for gcc... no
    checking for CC... no
    checking for cxx... no
    checking for cc++... no
    checking for cl... no
    checking for gcc... cc_r
    checking for C compiler default output file name... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... no
    checking whether cc_r accepts -g... yes
    checking for cc_r option to accept ANSI C... none needed
    checking how to run the C preprocessor... cc_r -E
    checking for egrep... grep -E
    checking for AIX... yes
    checking for --with-suffix...
    checking for case-insensitive build directory... no
    checking LIBRARY... libpython$(VERSION).a
    checking LINKCC... $(srcdir)/Modules/makexp_aix Modules/python.exp .
    $(LIBRARY);
    $(PURIFY) $(CC)
    checking for --enable-shared... no
    checking for --enable-profiling...
    checking LDLIBRARY... libpython$(VERSION).a
    checking for ranlib... ranlib
    checking for ar... ar
    checking for a BSD-compatible install... ./install-sh -c
    checking for --with-pydebug... no
    checking whether cc_r accepts -OPT:Olimit=0... no
    checking whether cc_r accepts -Olimit 1500... no
    checking whether pthreads are available without options... yes
    checking for ANSI C header files... yes
     
    pruebauno, Jul 15, 2005
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.