Can't compile modules

BlitzMax Forums/BlitzMax Programming/Can't compile modules

xlsior

(Posted 2011) [#1]

Something weird here:

I got a new harddrive, and reinstalled windows.

Reinstalled all my software, but I am no longer able to compile any .cpp code with MinGW. Instead, I get hundreds of these lines:

Compiling:strtok.cpp
Compiling:baseapi.cpp
Compiling:tesseractmain.cpp
C:\Users\Marc\AppData\Local\Temp\cckdJ56G.s: Assembler messages:
C:\Users\Marc\AppData\Local\Temp\cckdJ56G.s:7: Error: invalid instruction suffix for `push'
C:\Users\Marc\AppData\Local\Temp\cckdJ56G.s:9: Error: invalid instruction suffix for `push'
C:\Users\Marc\AppData\Local\Temp\cckdJ56G.s:10: Error: invalid instruction suffix for `push'
C:\Users\Marc\AppData\Local\Temp\cckdJ56G.s:11: Error: invalid instruction suffix for `push'
C:\Users\Marc\AppData\Local\Temp\cckdJ56G.s:45: Error: invalid instruction suffix for `pop'
<-snip->

I even tried to copy over both my old MinGW and blitzmax folders as-is, and still get the same error. All MinGW environment variables and the PATH is identical to my old drive, and the blitzmax IDE does successfully detect the presence and version numbers of FASM and GCC.

Meanwhile, plain .bmx files do appear to compile OK.

Does anyone have any idea what might be going on here?

Last edited 2011

Last edited 2011

GfK	(Posted 2011) [#2]

I had the same problem. Try adding another env var:

Name: CPLUS_INCLUDE_PATH
Value: C:\MinGW\include;C:\MinGW\lib\gcc\mingw32\3.4.5\include

Obviously, make sure the value (particularly the 3.4.5 bit) is correct, and change it accordingly.

xlsior

(Posted 2011) [#3]

That's the weird thing: I already had that environment variable in place, copied from my previous windows install.
I also copied the MinGW install folder as-is from the same windows install, but somehow it didn't work anymore.

Oddly enough, it started working just now as soon as I replaced my PATH with the PATH from my old computer:

It didn't work with this:

C:\Program Files (x86)\ATI Stream\bin\x86_64;C:\Program Files (x86)\ATI Stream\bin\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;c:\MinGW\bin;C:\code\SlikSvn\bin;C:\MinGW\bin

but it does work with this:

C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;
C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;c:\MinGW\bin;C:\code\SlikSvn\bin\;C:\Program Files (x86)\Calibre2\;c:\tools;C:\Program Files (x86)\Mercurial;C:\Program Files (x86)\QuickTime\QTSystem\;c:\code\git\bin;C:\MinGW\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live

Which makes no sense to me, since the only references to MinGW point to the same folder in both.
(And I notice it's listed twice in each case, oddly enough)

And minGW\bin -was- in the path, since I could type "gcc -v" anywhere and see the version info.