Oh dear. I'd changed some environment variables when I switched to using python 2.6 and was accidentally using a local version of gcc, which evidently doesn't work correctly. Everything builds fine now. Thanks and sorry for the wasted time.
On Tue, Jul 28, 2009 at 7:57 PM, David Cournapeau<[email protected]> wrote: > On Wed, Jul 29, 2009 at 2:38 AM, Daniel > Wheeler<[email protected]> wrote: >> -Wall -Wstrict-prototypes -fPIC >> >> compile options: '-c' >> gcc: _configtest.c >> gcc: error trying to exec 'cc1': execvp: No such file or directory >> gcc: error trying to exec 'cc1': execvp: No such file or directory > > That's your problem right there: your compiler is broken. What happens > if you call gcc by yourself on a trivial C program ? > > David > _______________________________________________ > NumPy-Discussion mailing list > [email protected] > http://mail.scipy.org/mailman/listinfo/numpy-discussion > -- Daniel Wheeler _______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
