User forums > Help
CB 10.05 unusable under MAC OSX 10.6.4. - Workaround for GCC4.4 under 8.05?
stahta01:
See http://wiki.codeblocks.org/index.php?title=Installing_a_supported_compiler#Compiler-neutral_setup_steps
If the Compiler Name you want already has a Valid Path that differs from what you want.
Copy the Compiler giving it a new name and change the toolchain path to the correct path.
Tim S.
er:
--- Quote from: stahta01 on August 17, 2010, 12:42:05 am ---See http://wiki.codeblocks.org/index.php?title=Installing_a_supported_compiler#Compiler-neutral_setup_steps
If the Compiler Name you want already has a Valid Path that differs from what you want.
Copy the Compiler giving it a new name and change the toolchain path to the correct path.
Tim S.
--- End quote ---
Thanks. This has worked with compiler gcc4.4 that I installed with fink. Specifically, in
Settings > Compiler > Toolchain
I replaced C-compiler by by gcc-4 and the C++ compiler by g++-4. Since make, ar and gdb were left out by the fink install, rather than replace the "compiler's installation directory" with the new one, /sw/bin, I put the latter under Additional Pathname.
And yes, I was able to use C++0x with the flat -std=c++0x. Let's see if it works upon exhaustive use.
er:
Hi,
I'm retracing my steps, above, and stumble upon this problem:
||warning: in obj/.../libs/assign/v2/src/main.o, file was built for i386 which is not the architecture being linked (x86_64)|
||=== Build finished: 0 errors, 1 warnings ===|
Any suggestion for troubleshooting? Thanks.
stahta01:
--- Quote from: er on November 11, 2010, 09:05:27 pm ---Hi,
I'm retracing my steps, above, and stumble upon this problem:
||warning: in obj/.../libs/assign/v2/src/main.o, file was built for i386 which is not the architecture being linked (x86_64)|
||=== Build finished: 0 errors, 1 warnings ===|
Any suggestion for troubleshooting? Thanks.
--- End quote ---
Find the Compiler or Linker Option needed to specify the machine/instruction set.
Put the right option in the project extra compiler or linker area.
Tim S.
er:
Thanks. I guess you mean this
http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html
?
In Build Options > Compiler Settings > Compiler Flags there is a flag for i386, but not x86_64...
I tried -march=core2 which seemed like a related match, but no change : the same warning.
Still stuck.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version