Bugs item #1212703, was opened at 2005-06-01 15:05
Message generated for change (Comment added) made by ranma
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1212703&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: Vincent Jamart (ranma)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.5 CVS broken for HP-UX platform?
Initial Comment:
While trying to compile Python 2.5 from the nighlty CVS
image, it raises the following errors on HP-UX. (OS
version= HP-UX 11.22 on ia64, compiler= aCC: HP
aC++/ANSI C B3910B A.06.00 [Aug 25 2004])
Compilation flags:
export CC=aCC
export CFLAGS="-Ae +DD64"
export LDFLAGS="+DD64"
make clean
./configure --prefix=/usr/local/python_cvs --with-cxx=aCC
(...)
creating Makefile
aCC -c -DNDEBUG -O -I. -I./Include
-DPy_BUILD_CORE -o
Modules/ccpython.o ./Modules/ccpython.cc
"/usr/include/sys/unistd.h", line 594: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline truncate(const char *a, off_t b) { return
__truncate64(a,b); }
^
"/usr/include/sys/unistd.h", line 595: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline prealloc(int a, off_t b) { return
__prealloc64(a,b); }
^
"/usr/include/sys/unistd.h", line 596: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline lockf(int a, int b, off_t c) { return
__lockf64(a,b,c); }
^
"/usr/include/sys/unistd.h", line 597: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline ftruncate(int a, off_t b) { return
__ftruncate64(a,b); }
^
"/usr/include/sys/stat.h", line 173: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline lstat __((const char *, struct stat *));
^
"./Include/pyport.h", line 612: error #2035: #error
directive: "LONG_BIT
definition appears wrong for platform (bad
gcc/glibc
config?)."
#error "LONG_BIT definition appears wrong for
platform (bad gcc/glibc
config?)."
^
1 error detected in the compilation of
"./Modules/ccpython.cc".
*** Error exit code 2
Stop.
aCC -c -DNDEBUG -O -I. -I./Include
-DPy_BUILD_CORE -o
Modules/ccpython.o ./Modules/ccpython.cc
"/usr/include/sys/unistd.h", line 594: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline truncate(const char *a, off_t b) { return
__truncate64(a,b); }
^
"/usr/include/sys/unistd.h", line 595: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline prealloc(int a, off_t b) { return
__prealloc64(a,b); }
^
"/usr/include/sys/unistd.h", line 596: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline lockf(int a, int b, off_t c) { return
__lockf64(a,b,c); }
^
"/usr/include/sys/unistd.h", line 597: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline ftruncate(int a, off_t b) { return
__ftruncate64(a,b); }
^
"/usr/include/sys/stat.h", line 173: warning #2837-D:
omission of
explicit
type is nonstandard ("int" assumed)
inline lstat __((const char *, struct stat *));
^
"./Include/pyport.h", line 612: error #2035: #error
directive: "LONG_BIT
definition appears wrong for platform (bad
gcc/glibc
config?)."
#error "LONG_BIT definition appears wrong for
platform (bad gcc/glibc
config?)."
^
1 error detected in the compilation of
"./Modules/ccpython.cc".
*** Error exit code 2
Stop.
----------------------------------------------------------------------
>Comment By: Vincent Jamart (ranma)
Date: 2005-06-28 17:05
Message:
Logged In: YES
user_id=150220
This is how we managed to solve the problem here, but it's
not a clean solution:
#install script for HP-UX 11.xx
CPPFLAGS="+DD64 -I/usr/local/bzip2-1.0.3/include"
export CPPFLAGS
CC="/opt/aCC/bin/aCC -Ae +DD64"
export CC
CFLAGS="-Ae +DD64"
export CFLAGS
CXX="/opt/aCC/bin/aCC -Ae"
export CXX
CXXFLAGS="-Ae +DD64"
export CXXFLAGS
LDFLAGS="+DD64 -L/usr/local/bzip2-1.0.3/lib"
export LDFLAGS
cd dist/src
#
# Do not use the --without-gcc flag because the CC env.var.
will be
# reset to 'cc' (which do not want)
# Additionally we're not using --with-cxx because we want
the system to use
# the CC as it is defined above. The reason is that
apparantly CFLAGS is not
# taken into account thus all options should go into the
definition of CC
#
./configure --prefix=/usr/local/python --without-threads
#
# Finally after the configure we need to edit the resulting
Makefile
# by hand because 'ld' will be used to link the extension
modules. However
# 'ld' does not know the '+DD64' flag and we should link
with aCC instead.
# However there is no way to ask 'configure' to link with
aCC instead of ld.
----------------------------------------------------------------------
Comment By: Anthony Baxter (anthonybaxter)
Date: 2005-06-19 11:01
Message:
Logged In: YES
user_id=29957
It's not clear from your message - did you find a fix for
this? It seems like this should be closed as notabug...
----------------------------------------------------------------------
Comment By: Vincent Jamart (ranma)
Date: 2005-06-16 12:09
Message:
Logged In: YES
user_id=150220
We nailed down the problem.
Apparantly the option "+DD64" is not used by 'make'.
Nevertheless we added this to CPPFLAGS and CFLAGS.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1212703&group_id=5470
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
