Ronald Oussoren added the comment:
I've closed the issue as 'wont fix' because llvm-gcc will miscompile 3.3 due to
bugs in that compiler. CPython won't work around that compiler bug (if that's
even possible).
The workaround: use clang to compile (and on older OSX releases use a different
Ronald Oussoren added the comment:
The configure script for python 3.3 detects llvm-gcc and automatically selects
clang when it is found.
That seems to be the best feasible solution for this issue. I therefore propose
to close this issue.
--
___
Lucas Sinclair added the comment:
I agree to close the issue. I tried following the steps proposed here:
http://docs.python.org/devguide/
And typed these two commands on a OS X 10.8.1 with XCode and command line tools
installed.
$ hg clone http://hg.python.org/cpython.
$ run ./configure
Changes by Anthony Kong anthony.hw.k...@gmail.com:
--
nosy: +Anthony.Kong
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Python-bugs-list
Ronald Oussoren ronaldousso...@mac.com added the comment:
The attached configure.ac is a fragment of a configure script that tries to
detect if AC_PROG_CC would pick llvm-gcc when clang is also available and then
explicitly picks clang.
This would avoid python3.3 won't build on OSX 10.7 bug
Ronald Oussoren ronaldousso...@mac.com added the comment:
The attached patch issue13241-configure-version1.txt implements a number of
changes to configure (although only configure.ac is present in the patch)
1) Autodetect the compiler on OSX, in particular
- detect llvm-gcc and use clang
Hynek Schlawack h...@ox.cx added the comment:
Ned, any progress/problems?
I've closed two dupes already in the last few days and we're still in the
alphas. We really should get this fixed before beta1 or the tracker will be
flooded.
Let me know if you need something. :)
--
Ned Deily n...@acm.org added the comment:
Hynek: Thanks for the offer; I've got it. I'll have a comprehensive update to
support the new multiple dev environments for 10.6 and beyond prior to b1 (and
for 2.7.x and 3.2.x).
--
___
Python tracker
Tom Pinckney thomaspinckn...@gmail.com added the comment:
FWIW, clang from Xcode 4.3.2 build 4E2002 w/ command line tools built
everything fine for me too (i.e., ./configure CC=clang).
LM-SJN-00377886:cpython tom$ uname -a
Darwin LM-SJN-00377886 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12
Trent Nelson tr...@snakebite.org added the comment:
Hi Ned,
On a brand new OS X Lion install with the latest XCode (4.3.2) and command line
tools*, the following worked:
./configure --with-pydebug CC=clang MACOSX_DEPLOYMENT_TARGET=10.7
That is, everything built cleanly, and all tests ran
Michele Orrù maker...@gmail.com added the comment:
./configure --with-pydebug CC=clang MACOSX_DEPLOYMENT_TARGET=10.7
Works on my machine too.
--
nosy: +maker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
Ned Deily n...@acm.org added the comment:
Trent, yes, now that the Xcode 4 situation has settled down a bit, clang is the
compiler of choice for OS X 10.7 with Xcode 4.3 although there are still some
open questions. I intend to update configure in the near future for all active
branches to
Trent Nelson tr...@snakebite.org added the comment:
Once we fix this I can add the build slave
I'm missing the context for this.
Yeah I uh, seemed to have deleted the introductory sentence I wrote that
said I was doing some prep work before adding an OS X 10.7 build slave.
Can't you
Changes by Hynek Schlawack h...@ox.cx:
--
nosy: +hynek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Python-bugs-list mailing list
Changes by Anton Korobeynikov an...@korobeynikov.info:
--
nosy: +Anton.Korobeynikov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Michael Foord mich...@voidspace.org.uk added the comment:
Note that apple have made gcc available, as part of command line tools for
XCode, freely (free developer registration required though) from:
https://developer.apple.com/downloads/
See:
Ned Deily n...@acm.org added the comment:
Note that apple have made gcc available, as part of command line tools for
XCode, freely (free developer registration required though) from:
https://developer.apple.com/downloads
See:
http://kennethreitz.com/xcode-gcc-and-homebrew.html
No. The new
Ned Deily n...@acm.org added the comment:
While the full regression testing of all active branches against all of the
current compiler versions is in progress, my current (and preliminary)
recommendations (despite some test failures):
- for OS X 10.7.x, use the latest released Xcode,
Ronald Oussoren ronaldousso...@mac.com added the comment:
I've found a bug in the curses module that is causing problems:
diff --git a/Modules/_cursesmodule.c b/Modules/_cursesmodule.c
--- a/Modules/_cursesmodule.c
+++ b/Modules/_cursesmodule.c
@@ -2056,7 +2056,8 @@
{encoding,
Nam Nguyen bits...@gmail.com added the comment:
Ronald's patch does fix the segmentation fault with clang-compiled Python. But
this bug report seems to be about LLVM-GCC not compiling correctly.
--
___
Python tracker rep...@bugs.python.org
Ronald Oussoren ronaldousso...@mac.com added the comment:
Both clang and llvm-gcc had problems, the llvm-gcc problem is still there and
is caused by a compiler bug. There is nothing we can do about that beyond
warning Apple.
It's also pretty clear that llvm-gcc (and gcc in general) is on the
Guido van Rossum gu...@python.org added the comment:
On my system (Snow Leopard OSX 10.6.8, Xcode 4.1) there are several different
versions of gcc available in /usr/bin/. Some are symlinks to others; in
particular gcc links to llvm-gccc-4.2. By using ./configure CC=gcc-4.2 I get
a working
Ned Deily n...@acm.org added the comment:
That works for Xcode 4.1, which is now out-of-date. The current releases of
Xcode, 4.2.x for 10.7 Lion and optionally for 10.6 Snow Leopard, no longer
include gcc-4.2, only llvm-gcc and clang. I am working on completing an
extensive set of regression
Ronald Oussoren ronaldousso...@mac.com added the comment:
The version of clang included in Xcode 4.2.1 (the current release) still
miscompiles Python 3.3 and both C files included in this issue.
The same is true for the Xcode 4.3 beta.
Python 2.7 seems to work fine with the same compiler,
Ronald Oussoren ronaldousso...@mac.com added the comment:
I've filed an issue in Apple's tracker, #10667893. Filing more issues would be
helpful, if more issues in their tracker mention this bug it is more likely to
get fixed.
--
___
Python tracker
Nam Nguyen bits...@gmail.com added the comment:
Here's a minimal test case for #define bug in LLVM GCC.
If the base struct is 8-byte long or smaller, the code runs correctly.
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
#include stdio.h
#include stdlib.h
Changes by Nam Nguyen bits...@gmail.com:
--
nosy: +Nam.Nguyen
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Python-bugs-list mailing
Ronald Oussoren ronaldousso...@mac.com added the comment:
The bug in the 'gcc' command is still present when using Xcode 4.2.1 (that is,
the attached unicode.c miscompiles with gcc -O3).
Clang (again from Xcode 4.2.1) compiles the file correctly, but fails to do a
proper build the last few
Michael Foord mich...@voidspace.org.uk added the comment:
Note that this works for me on a Macbook Air that has never had Snow Leopard,
nor XCode 3 installed.
As far as I can tell non-llvm gcc *is* installed by XCode 4.2: /usr/bin/gcc-4.2
--
___
Ned Deily n...@acm.org added the comment:
Lucas, there is nothing particularly special about the configuration parameters
that Michael used other than enabling debug. Prior to Xcode 4, Xcode supplied
a standard (non-LLVM) gcc as the default compiler, 4.2 for 10.6 and 4.0 for
10.5 and 10.4.
Changes by Yury Selivanov yseliva...@gmail.com:
--
nosy: +Yury.Selivanov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Michael Foord mich...@voidspace.org.uk added the comment:
On OS X Lion, with XCode 4.2 installed, I find the following works (no need to
install macports):
./configure CC=gcc-4.2 --prefix=/dev/null --with-pydebug
--
nosy: +michael.foord
___
Python
Michael Foord mich...@voidspace.org.uk added the comment:
Ah, it seems I have XCode 3.2.6 installed alongside XCode 4.2.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
Lucas Sinclair blastoc...@mac.com added the comment:
Well the configure parameters suggested by Michael Foord worked. I was able to
build cpython on a mac. But I could not have guessed how to make it work.
Shouldn't these instructions be added here http://docs.python.org/devguide/ ?
Shouldn't
Lucas Sinclair blastoc...@mac.com added the comment:
I'm on 10.7.2, with XCode is 4.2 and the problem is still present. The command
ggc -v produces the following output:
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
The command ./configure --with-pydebug make -j2
Ned Deily n...@acm.org added the comment:
Lucas, exactly what source version of Python are you trying to build (i.e what
does hg summary say)?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
Lucas Sinclair blastoc...@mac.com added the comment:
I just cloned cpython today. The output of hg summary is:
parent: 73351:2bec7c452b39 tip
Fix C89 incompatibility.
branch: default
commit: (clean)
update: (current)
--
___
Python tracker
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Python-bugs-list mailing
Changes by Julian Berman julian+python@grayvines.com:
--
nosy: +Julian
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Julian Berman julian+python@grayvines.com added the comment:
I was unsuccessful building tip with any of the 3 compilers. Full paste of
output from ./configure and make, along with haypo's test file are attached.
http://paste.pound-python.org/show/14320/
I'm on 10.7.2, XCode is 4.1
Ned Deily n...@acm.org added the comment:
Julian, I am able to build and run the current default (3.3) tip (52b35dae22d1)
on 10.7.2 with the gcc-4.2 from Xcode 4.1, with or without debug enabled. Are
you sure you have pulled all the latest updates and are using a clean build
directory? If
Julian Berman julian+python@grayvines.com added the comment:
Never mind, yes, you're correct, somehow my build dir must have been dirty.
Sorry bout that.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
title: Assertion failed in _PyUnicode_CheckConsistency during build of default
branch on Mac OS X - llvm-gcc-4.2 miscompiles Python (XCode 4.1+ on Mac OS
10.7)
___
Python tracker
STINNER Victor victor.stin...@haypocalc.com added the comment:
I asked for more information about llvm-gcc on IRC (#llvm). Extracts:
- llvm-gcc is not maintained. (Clang and DragonEgg are.) Apple is the
maintainer of Apple's version of llvm-gcc and clang.
- Apple ships a [llvm-gcc] branch at
Ned Deily n...@acm.org added the comment:
Haypo, the OP has a workaround. IMO, we should not be making any
recommendations about which Apple compiler to use on OS X 10.7 until we have
completed test cycles of each. There are too many variables at the moment. I
am doing that and should have
46 matches
Mail list logo
