New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 2.5b2 fails to build on Solaris 10 (GCC Compiler) #43726
Comments
Hello, as promised here is the second report because of These are the problems (for full logs please see building '_ctypes' extension building '_curses' extension Regards, Guido |
Logged In: YES Thomas can you check out the ctypes problems? |
Logged In: YES I don't have access to a solaris 10 box myself (only the Guido, can you please try this? |
Logged In: YES Hmmm, I thought this was the report from using sun studio |
Logged In: YES @theller: @nnorwitz: In case it matters, I checked for the GCC version used. I $ gcc -v
Reading specs from
/usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/specs
Configured with:
/gates/sfw10/builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure
--prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as
--with-ld=/usr/ccs/bin/ld --without-gnu-ld
--enable-languages=c,c++ --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath) This is from package $ pkginfo -l SUNWgcc
PKGINST: SUNWgcc
NAME: gcc - The GNU C compiler
CATEGORY: system
ARCH: sparc
VERSION: 11.10.0,REV=2005.01.08.05.16
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: GNU C - The GNU C compiler 3.4.3
PSTAMP: sfw1020050108051924
INSTDATE: Mar 20 2006 14:30
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 296 installed pathnames
6 shared pathnames
5 linked files
25 directories
33 executables
104325 blocks used (approx) Regards, Guido |
Logged In: YES Guido, in SVN revision 51113 a change was committed that Can you try if that helps in your case? Thanks. See also http://python.org/sf/1530448 . |
Clsosing because no response. |
Modules/_ctypes/libffi/src/sparc/v8.S and The python build process seems to pass the gcc compile flags to compile It makes no sense if the debugging option -g is enabled, because C So, as a workaround, just do not pass the gcc "-g" option to the python A clean solution would be to avoid gcc C compiler options being passed |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: