User forums > Help
crt2.o / Vista headaches, now with -v goodness.
ironlizard:
It's CB. As you can see in the results you got (I noticed this too when recompiling everything), CB doesn't expand the PATH variable for the object by default because the linker's arguments are incorrect. In the wrong order, or something, I forget.They might work under another OS, but not this one. Did you try changing the command line configuration in CB to this: $linker -o $exe_output $libdirs $link_objects $libs $link_options
It works. No seriously. Just do it, you'll thank me. Alternatively, you could go through that entire process that I did in the course of this thread. It's up to you man. Save yourself and run now.
Pecan:
--- Quote from: ironlizard on September 03, 2007, 08:20:28 pm ---It's CB. As you can see in the results you got (I noticed this too when recompiling everything), CB doesn't expand the PATH variable for the object by default because the linker's arguments are incorrect. In the wrong order, or something, I forget.They might work under another OS, but not this one. Did you try changing the command line configuration in CB to this: $linker -o $exe_output $libdirs $link_objects $libs $link_options
It works. No seriously. Just do it, you'll thank me. Alternatively, you could go through that entire process that I did in the course of this thread. It's up to you man. Save yourself and run now.
--- End quote ---
I changed all command line macros such that the pattern followed your suggestion of "$linker -o $exe_output $libdirs ..."
I still get the crt2.o not found error with TDM gcc 4.2.1 on Windows XP.
TDragon:
--- Quote from: Pecan on July 14, 2008, 07:02:35 pm ---I still get the crt2.o not found error with TDM gcc 4.2.1 on Windows XP.
--- End quote ---
This will only, and I mean only, result from an improper MinGW installation. Remove any and all environment variables relating to MinGW/GCC (including PATH entries), reinstall MinGW in an empty directory, and add an entry for the bin subdirectory to PATH (typically C:\MinGW\bin).
If an improperly installed GCC exists anywhere in PATH (or, for 4.2.x and earlier, in /mingw), you WILL have problems. Do NOT install MinGW on top of mSYS or mSYS on top of MinGW. Do NOT have Cygwin and MinGW in PATH at the same time.
If you only ever run MinGW/GCC from Code::Blocks, you don't even need an entry in PATH. No environment variables whatsoever are necessary.
Cheers,
John E. / TDM
Navigation
[0] Message Index
[*] Previous page
Go to full version