User forums > Help

Seems wrong command line arguments

(1/3) > >>

Denis:
I moved MinGW from c:\MinGW to c:\develop\MinGW directory and change options into project and CodeBlocks in accordance with new path. But after I tryed to compile, I got compiler warning:

--- Quote ---cc1plus.exe: note: obsolete option -I- used, please use -iquote instead
--- End quote ---
And latter got error:

--- Quote ---error: ../bla-bla-bla.h: No such file or directory
--- End quote ---
bla-bla-bla.h - is project file

I found same problem here: http://developer.berlios.de/bugs/?func=detailbug&bug_id=7796&group_id=5358 and solution helped (I changed PCH mode in project properies to first). But I want to use second PCH mode. Developers, please fix this bug.

Biplab:

--- Quote from: Denis on September 15, 2007, 07:11:03 pm ---I moved MinGW from c:\MinGW to c:\develop\MinGW directory and change options into project and CodeBlocks in accordance with new path. But after I tryed to compile, I got compiler warning:

--- Quote ---cc1plus.exe: note: obsolete option -I- used, please use -iquote instead
--- End quote ---
And latter got error:

--- Quote ---error: ../bla-bla-bla.h: No such file or directory
--- End quote ---
bla-bla-bla.h - is project file

I found same problem here: http://developer.berlios.de/bugs/?func=detailbug&bug_id=7796&group_id=5358 and solution helped (I changed PCH mode in project properies to first). But I want to use second PCH mode. Developers, please fix this bug.

--- End quote ---

The problem you are facing is not the same one that you are referring. Please post the full command line so that we can understand the problem.

Also, were you getting the warning message before moving MinGW to c:\develop\MinGW directory??

Denis:
1. How to find out which real command line CodeBlocks uses for compiling?
2. I didn't confronte with this problem before moving from c:\MinGW to c:\develop\MinGW

PS: Wow! Selecting first PCH mode made compile speed really fast. It looks like second PCH mode doesn't works properly

Biplab:

--- Quote from: Denis on September 15, 2007, 07:37:35 pm ---1. How to find out which real command line CodeBlocks uses for compiling?

--- End quote ---

Settings > Compilers and debuggers > Other settings > Compiler logging (Set it to Full logging).


--- Quote from: Denis on September 15, 2007, 07:37:35 pm ---2. I didn't confronte with this problem before moving from c:\MinGW to c:\develop\MinGW

--- End quote ---

Strange. May be the version detection code needs some clean-up. Did you change the Compiler bin path??

I guess C::B is trying to detect the compiler version. But the execution of GCC fails (probably due to the change in path) and the fall back code sets the version to 3.x. Because you shouldn't get this warning as this has been fixed sometimes back and C::B is now equipped to deal with it. :)

Denis:
This is command line is sed for compiling pch.h file:

--- Quote ---mingw32-g++.exe -Wall -pipe -mthreads -Winvalid-pch -finput-charset=utf-8 -Wno-attributes -fno-strict-aliasing -D__GNUWIN32__ -D__WXMSW__ -DwxUSE_UNICODE -DWX_PRECOMP -DqWinOS=1 -DqMacOS=0 -DqDNGLittleEndian=1 -DWIN_ENV=1 -g -D__WXDEBUG__ -DWXUSINGDLL  -Iobj\win\Debug\src -I- -Iobj\win\Debug\src -I. -I. -Isrc -Isrc\dng_sdk -Isrc\xmp_sdk\include -Isrc\xmp_sdk\common -Isrc\expat\include -Isrc\MD5 -Isrc\libexif -IC:\develop\MinGW\lib\gcc_dll\mswud -IC:\develop\MinGW\include  -c D:\GCC\DNG4PS-2\src\src\pch.h -o obj\win\Debug\src\pch.h.gch
--- End quote ---

Yes, I changed compiler bin path to new one

PS: Sorry, forgot to report: MinGW for GCC 4.1.2, C::B SVN 4466

Navigation

[0] Message Index

[#] Next page