|
|
#1 |
|
A repair at the apple stored messed up my permissions
as talked about http://forums.macrumors.com/showthread.php?t=1468986
I noticed they downgraded my computer from from 10.6.8 to 10.6.3 and uninstalled a lot of stuff like xcode. This was all part of some diagnostic for my computer to eliminate a software problem apparently. I just wanted to compile a stupid program with allegro I find I have to use sudo to use g++ to use -L/usr/local/lib and this is after trying sudo chmod 755 /usr/local/lib. I try to use cmake to reinstall allegro after it turns out that the original install is screwed up somehow. cmake runs an initial test on gcc and it fails. I re-installed xcode from the 10.6 cd I got 2 years ago. terminal: Code:
jason-danckss-macbook:build Jason$ cmake .. -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- broken CMake Error at /Applications/CMake 2.8-7.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52 (MESSAGE): The C compiler "/usr/bin/gcc" is not able to compile a simple test program. It fails with the following output: Change Dir: /Users/Jason/allegro/build/CMakeFiles/CMakeTmp Run Build Command:/usr/bin/make "cmTryCompileExec/fast" /usr/bin/make -f CMakeFiles/cmTryCompileExec.dir/build.make CMakeFiles/cmTryCompileExec.dir/build "/Applications/CMake 2.8-7.app/Contents/bin/cmake" -E cmake_progress_report /Users/Jason/allegro/build/CMakeFiles/CMakeTmp/CMakeFiles 1 Building C object CMakeFiles/cmTryCompileExec.dir/testCCompiler.c.o /usr/bin/gcc -o CMakeFiles/cmTryCompileExec.dir/testCCompiler.c.o -c /Users/Jason/allegro/build/CMakeFiles/CMakeTmp/testCCompiler.c cc1: error: /usr/local/include: Permission denied make[1]: *** [CMakeFiles/cmTryCompileExec.dir/testCCompiler.c.o] Error 1 make: *** [cmTryCompileExec/fast] Error 2 CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:31 (project) -- Configuring incomplete, errors occurred! I guess I'm open to input but really I'm just venting. I'll try to use Clang instead I'll post back. |
|
|
|
0
|
|
|
#2 |
|
You have a Time Machine backup, don't you?
|
|
|
|
0
|
|
|
#3 |
|
I don't think Time Machine existed in 10.6.x. I thought that was a 10.7 feature.
Anyway, to the O.P., it looks like you're going to have to re-produce whatever custom setup you had before. Looks like the XCode Command-Line tools aren't installed correctly. You'll have to go into the settings menu and make sure they are activated. Of course, that may be difficult since you'll have an older version of XCode. Not sure if it's still supported or not. |
|
|
|
0
|
|
|
#4 |
|
Time machine
Time machine didnt only exist in 10.6 AND 10.7, but it was a new feature in 10.5 Leopard.
It went: 10.5 Leopard 10.6 Snow Leopard 10.7 Lion 10.8 Mountain Lion |
|
|
|
1
|
|
|
#5 |
|
I don't use Time Machine. oops.
I was able to fix some of the problems by re-enabling root and unlocking some system folders. Still doesn't work completely right. Problem is I set it up such a long time ago I don't remember what I have to do. |
|
|
|
0
|
|
|
#6 | |
|
Quote:
Edit: and keep that document backed up somewhere. |
||
|
|
0
|
![]() |
|
«
Previous Thread
|
Next Thread
»
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
All times are GMT -5. The time now is 01:52 PM.







Linear Mode
