User forums > Help
CB 10.05 unusable under MAC OSX 10.6.4. - Workaround for GCC4.4 under 8.05?
er:
Thanks,
This is the Build log after a rebuild:
-------------- Clean: Debug in cpp_0x ---------------
Cleaned "cpp_0x - Debug"
-------------- Build: Debug in cpp_0x ---------------
g++-4 -Wall -fexceptions -g -I/usr/local/trunk -c /Users/Me/dev/cpp/projects/cpp_0x/main.cpp -o obj/Debug/main.o
g++ -o bin/Debug/cpp_0x obj/Debug/main.o
ld: warning: in obj/Debug/main.o, file was built for i386 which is not the architecture being linked (x86_64)
Undefined symbols:
"_main", referenced from:
start in crt1.10.6.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 1 warnings
For comparison, this is the Build log, after re-setting the compiler settings to the default, and rebuilding:
-------------- Clean: Debug in cpp_0x ---------------
Cleaned "cpp_0x - Debug"
-------------- Build: Debug in cpp_0x ---------------
Compiling: main.cpp
Linking console executable: bin/Debug/cpp_0x
Output size is 8.76 KB
Process terminated with status 0 (0 minutes, 0 seconds)
0 errors, 0 warnings
stahta01:
Why are you mixing two separate commands; please change them to match. Either use "g++-4" or "g++" Not both.
Check the c++ Compiler and the linker command under compiler tool chain.
Please Turn ON Full Compiler Logging for Comparison to default settings.
--- Quote from: er on November 12, 2010, 11:01:17 pm ---For comparison, this is the Build log, after re-setting the compiler settings to the default, and rebuilding:
-------------- Clean: Debug in cpp_0x ---------------
Cleaned "cpp_0x - Debug"
-------------- Build: Debug in cpp_0x ---------------
Compiling: main.cpp
Linking console executable: bin/Debug/cpp_0x
Output size is 8.76 KB
Process terminated with status 0 (0 minutes, 0 seconds)
0 errors, 0 warnings
--- End quote ---
Tim S.
er:
"Why are you mixing two separate commands; please change them to match. Either use "g++-4" or "g++" Not both."
Indeed. This should be the set up
Compiler's installation dir : Auto-detect
Other paths : the path to the non-default compiler, in my case /sw/bin
C compiler : gcc-4
C++ compiler : g++-4
Linker for dynamic libs : g++-4
I had forgotten the last one.
One last question : how do I save the Settings (such as Search directorie)? Saving the project or the workspace does not suffice. If I close and restart CB, the changes are not kept.
stahta01:
--- Quote from: er on November 15, 2010, 06:29:58 pm ---I had forgotten the last one.
One last question : how do I save the Settings (such as Search directorie)? Saving the project or the workspace does not suffice. If I close and restart CB, the changes are not kept.
--- End quote ---
Note: Try doing the search directories changes and then use "save all projects" or/and "save projects" before doing the below steps.
Note: Also, Try doing "project save as"; if it works, it means likely you do not have permission or file is read-only.
If Code::Blocks does not crash on shut-down it should save the setting in the project.
Try turning off/disabling all the plug-ins except for the Compiler Plug-in.
Shut down Code::Blocks.
Re-Open Code::Blocks are all the plug-ins except for the Compiler Plug-in disabled?
If yes, open project and change search directories.
Shut down Code::Blocks.
Re-Open Code::Blocks are all the changes to search directories still there?
If yes, try the turning on the Plugins you use one at a time to figure out which needs to be off to save the project changes.
Tim S.
Navigation
[0] Message Index
[*] Previous page
Go to full version