Ned Deily n...@acm.org added the comment:
Oleg, thanks. That is consistent with previous reports; so far, this issue has
only been reported with llvm-gcc, not the plain gcc-4.2's shipped in Xcode
prior to 4.2.
--
___
Python tracker
Oleg Plakhotnyuk oleg...@gmail.com added the comment:
Thank you all for help. I finally managed to build it. :-)
So here are complete steps I've taken to build python after OS reinstall:
1. Install XCode 4.2
2. Install MacPorts
3. sudo port -v selfupdate
4. sudo port install gcc46
5. ./configure
Changes by Oleg Plakhotnyuk oleg...@gmail.com:
--
resolution: - works for me
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Changes by Oleg Plakhotnyuk oleg...@gmail.com:
--
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Changes by Oleg Plakhotnyuk oleg...@gmail.com:
--
resolution: works for me - fixed
status: pending - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
Changes by Oleg Plakhotnyuk oleg...@gmail.com:
--
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
___
Ned Deily n...@acm.org added the comment:
In general, I would not recommend using anything other than an Apple-supplied
tool chain for building anything on Mac OS X. To help us better understand the
issues, can you say exactly which compilers you tried originally, i.e. the
complete --version
Oleg Plakhotnyuk oleg...@gmail.com added the comment:
Ah, of course.
Initially I've tried to compile using this:
i686-apple-darwin10-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658)
(LLVM build 2336.1.00)
XCode version 4.2, build 4C199
--
STINNER Victor victor.stin...@haypocalc.com added the comment:
i686-apple-darwin10-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658)
(LLVM build 2336.1.00)
Oh, that's not GCC but llvm-gcc. It is maybe a bug in LLVM?
--
___
Python tracker
New submission from Oleg Plakhotnyuk oleg...@gmail.com:
Trying to build latest development revision:
localhost:repo family$ hg summary
parent: 73044:a985d733b3a3 tip
#12753: Add support for Unicode name aliases and named sequences.
branch: default
commit: (clean)
update: (current)
Constantly
Oleg Plakhotnyuk oleg...@gmail.com added the comment:
Oh yes.
I am building with this command line:
./configure --with-pydebug make -j2
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
STINNER Victor victor.stin...@haypocalc.com added the comment:
It is a compiler bug in GCC 4.2.1 with -O3. Try to compile attached unicode.c
program with gcc -O3. The correct result is:
$ gcc -O3 unicode.c -o unicode ./unicode
is ascii? 0
is compact? 1
is compact ascii? 0
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
components: +Build
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
The bug has been fixed in GCC, try a more recent version using ./configure
CC=gccX.Y.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
Ezio Melotti ezio.melo...@gmail.com added the comment:
It should also work without --with-pydebug, or with a different compiler.
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
Ned Deily n...@acm.org added the comment:
I believe this was a bug specific to the llvm-gcc compiler shipped with Xcode
4.1 and possibly Xcode 4.0. I do not have Xcode 4 on OS X 10.6 but haypo's
test does fail with the llvm-gcc 4.2.1 that comes with Xcode 4.1 on 10.7. Can
you confirm
Ezio Melotti ezio.melo...@gmail.com added the comment:
See also http://mail.python.org/pipermail/python-dev/2011-September/113731.html
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13241
17 matches
Mail list logo
