Hi Richard,
I did reinstall XCode 1.4.1 (the BSD SDK only) already. It did fix
one error I was having (it wasn't finding gcc at all before)
Would you be able to tell us what fix you made? It might be that the
fix caused the problem that you see now about the C compiler being
unable to cr
On 31.8.2007, at 9.49, Richard Connamacher wrote:
On Aug 30, 2007, at 4:24 PM, Ryan Schmidt wrote:
I can only think that something got royally screwed up when I
restored my Mac from a backup, since it used to work before.
Maybe some critical libraries used by GCC were corrupted in the
p
On Aug 30, 2007, at 4:24 PM, Ryan Schmidt wrote:
I can only think that something got royally screwed up when I
restored my Mac from a backup, since it used to work before. Maybe
some critical libraries used by GCC were corrupted in the process?
I was planning to hold off until Leopard befo
On Aug 30, 2007, at 18:06, Richard Connamacher wrote:
On Aug 30, 2007, at 3:23 PM, Ryan Schmidt wrote:
On Aug 30, 2007, at 16:46, Richard Connamacher wrote:
I'm having a problem with MacPorts (though for all I know it may
be gcc rather than MacPorts itself). After restoring my system
from
Ryan,
Thanks for the advice.
Yep, I have GCC 4.0.1 installed. It's at /usr/bin/gcc and --version
gives:
powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc.
build 5367)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditi
On Aug 30, 2007, at 16:46, Richard Connamacher wrote:
I'm having a problem with MacPorts (though for all I know it may be
gcc rather than MacPorts itself). After restoring my system from a
crash, port now can't compile anything.
I've reinstalled MacPorts 1.5, and I've reinstalled XCode 2.4.
I'm having a problem with MacPorts (though for all I know it may be
gcc rather than MacPorts itself). After restoring my system from a
crash, port now can't compile anything.
I've reinstalled MacPorts 1.5, and I've reinstalled XCode 2.4.1 (BSD
Tools). Still no dice.
The error I'm getting
