You are here: Home / Documentation / How To's / buildout error on Mac OS X 10.6.4 Snow Leopard

buildout error on Mac OS X 10.6.4 Snow Leopard

by nguyen — published Sep 10, 2010 10:25 PM, last modified Aug 16, 2016 10:49 AM
cc1: error: unrecognized command line option "-Wno-long-double"

When building the bootstrap buildout of Plone 3.2.3 from

https://svn.it.uwosh.edu/trac/browser/buildouts/ploneedu/plone-3.2.3 (Trac browser view)

or 

https://svn.it.uwosh.edu/svn/plone/buildouts/ploneedu/plone-3.2.3 (svn repo)

on Mac OS X 10.6.4 (Snow Leopard) I got this error:

creating build/temp.macosx-10.3-i386-2.4/AccessControl
/usr/bin/gcc -I/Users/kim/Plone-3.3.4/Python-2.4/include -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -IExtensionClass -I. -IAcquisition -I/Users/kim/Plone-3.3.4/Python-2.4/include/python2.4 -c AccessControl/cAccessControl.c -o build/temp.macosx-10.3-i386-2.4/AccessControl/cAccessControl.o
cc1: error: unrecognized command line option "-Wno-long-double"
error: command '/usr/bin/gcc' failed with exit status 1
While:
  Installing zope2.

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File "/Users/kim/src/plone/buildouts/ploneedu/plone-3.2.3/eggs/zc.buildout-1.1.2-py2.4.egg/zc/buildout/buildout.py", line 1509, in main
    getattr(buildout, command)(args)
  File "/Users/kim/src/plone/buildouts/ploneedu/plone-3.2.3/eggs/zc.buildout-1.1.2-py2.4.egg/zc/buildout/buildout.py", line 473, in install
    installed_files = self[part]._call(recipe.install)
  File "/Users/kim/src/plone/buildouts/ploneedu/plone-3.2.3/eggs/zc.buildout-1.1.2-py2.4.egg/zc/buildout/buildout.py", line 1091, in _call
    return f()
  File "/Users/kim/src/plone/buildouts/ploneedu/plone-3.2.3/eggs/plone.recipe.zope2install-3.0-py2.4.egg/plone/recipe/zope2install/__init__.py", line 225, in install
    'build_ext', '-i',
AssertionError

The way I got around this is that after reading that maybe this is a gcc version issue, I did a "which gcc" and found that in /usr/bin there is a gcc symlink to gcc-4.2 but there is also a gcc-4.0.  I did an "rm gcc" then "ln -s gcc-4.0 gcc" so that the next time buildout invoked gcc it would really run gcc 4.0, not 4.2.  This worked.

cpe-24-208-79-251:plone-3.2.3 kim$ which gcc
/usr/bin/gcc
cpe-24-208-79-251:plone-3.2.3 kim$ pushd /usr/bin
/usr/bin ~/src/plone/buildouts/ploneedu/plone-3.2.3
cpe-24-208-79-251:bin kim$ ls -l gcc*
lrwxr-xr-x  1 root  wheel       7 Jan 19  2010 gcc -> gcc-4.2
-rwxr-xr-x  1 root  wheel   97392 May 10 19:06 gcc-4.0
-rwxr-xr-x  1 root  wheel  166128 May 10 19:52 gcc-4.2
cpe-24-208-79-251:bin kim$ sudo rm gcc
Password:
cpe-24-208-79-251:bin kim$ sudo ln -s gcc-4.0 gcc 
cpe-24-208-79-251:bin kim$ ll gcc*
lrwxr-xr-x  1 root  wheel       7 Sep 10 22:14 gcc -> gcc-4.0
-rwxr-xr-x  1 root  wheel   97392 May 10 19:06 gcc-4.0
-rwxr-xr-x  1 root  wheel  166128 May 10 19:52 gcc-4.2
 
Navigation