[pygr-notify] Issue 135 in pygr: Can't build in Lion, because gcc-4.0 is gone after xcode 4 killed xcode 3

[pygr at googlecode.com]

Status: New
Owner: pygr-bug... at googlegroups.com
Labels: Type-Defect Priority-Medium

New issue 135 by m... at swarm.nu: Can't build in Lion, because gcc-4.0 is  
gone after xcode 4 killed xcode 3
http://code.google.com/p/pygr/issues/detail?id=135

So, on my Lion 10.7.2, and apparently on all Lions, gcc-4.0 is forever  
gone. :-( And thus, pygr can't compile.



python setup.py installrunning install
running bdist_egg
running egg_info
writing pygr.egg-info/PKG-INFO
writing top-level names to pygr.egg-info/top_level.txt
writing dependency_links to pygr.egg-info/dependency_links.txt
reading manifest file 'pygr.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '.gitignore' found anywhere  
in distribution
warning: no previously-included files matching '*.py[co]' found anywhere in  
distribution
writing manifest file 'pygr.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.3-fat/egg
running install_lib
running build_py
creating build
creating build/lib.macosx-10.3-fat-2.7
creating build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/__init__.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/annotation.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/blast.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/classutil.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/coordinator.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/Data.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/dbfile.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/downloader.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/graphquery.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/logger.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/mapping.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/metabase.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/nlmsa_utils.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/parse_blast.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/schema.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/seqdb.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/sequence.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/sequtil.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/sqlgraph.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/translationDB.py -> build/lib.macosx-10.3-fat-2.7/pygr
copying pygr/xnestedlist.py -> build/lib.macosx-10.3-fat-2.7/pygr
creating build/lib.macosx-10.3-fat-2.7/pygr/apps
copying pygr/apps/__init__.py -> build/lib.macosx-10.3-fat-2.7/pygr/apps
copying pygr/apps/catalog_downloads.py ->  
build/lib.macosx-10.3-fat-2.7/pygr/apps
copying pygr/apps/leelabdb.py -> build/lib.macosx-10.3-fat-2.7/pygr/apps
copying pygr/apps/maf2nclist.py -> build/lib.macosx-10.3-fat-2.7/pygr/apps
copying pygr/apps/maf2VSgraph.py -> build/lib.macosx-10.3-fat-2.7/pygr/apps
copying pygr/apps/seqref.py -> build/lib.macosx-10.3-fat-2.7/pygr/apps
copying pygr/apps/splicegraph.py -> build/lib.macosx-10.3-fat-2.7/pygr/apps
copying pygr/apps/ucsc_ensembl_annot.py ->  
build/lib.macosx-10.3-fat-2.7/pygr/apps
running build_ext
building 'pygr.seqfmt' extension
creating build/temp.macosx-10.3-fat-2.7
creating build/temp.macosx-10.3-fat-2.7/pygr
gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -arch ppc -arch i386 -g  
-O2 -DNDEBUG -g -O3  
-I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c  
pygr/seqfmt.c -o build/temp.macosx-10.3-fat-2.7/pygr/seqfmt.o
unable to execute gcc-4.0: No such file or directory
error: command 'gcc-4.0' failed with exit status 1



So I've spent some time looking it up. And with "some time", I mean several  
hours.
http://hints.macworld.com/article.php?story=20110318050811544
http://useyourloaf.com/blog/2011/7/20/hello-lion-goodbye-xcode-3.html

Etc. Hundreds of Mac users, complaining that gcc 4.0 apparently doesn't  
work in Lion anymore. Lion doesn't allow xcode 3.0.

Am I really the first Lion user to try to build pygr, and notice this? Or  
is there a way around this death crippling.