User forums > General (but related to Code::Blocks)
GCC 4.2.1 binary release for mingw is available from MINGW
OLDSCHOOL:
--- Quote from: thomas on August 14, 2007, 05:34:30 pm ---It's mostly about WXDLLEXPORT, WXDLLIMPEXP, WXDLLIMPEXP_SCI, and WXDLLIMPEXP_PG.
I have no idea what we need them for, anyway (or if at all?). Since we don't do any dynamic loading, I think those should be not needed at all? The linker should figure out a symbol if it's not exported, too... shouldn't it?
Anyway, that's what triggers the "attribute blah blah cannot blah" style error.
--- End quote ---
Hello, this is why mingw.org call 4.2.1 a Technology Preview. There are a stack of issues about c++ dll's We can get them to work, no problem, now, but, tomorrow ... there are libstdc++ versioning issues (has anybody read the MSDN article entitled something like ("Building DLL's is easy, maintaining them is the problem") there is the question about how do we canonicalize gcc's -Bstatic vs -Bdynamic diff into preprocessor defines that turn on/off dllimport/dllexport attributes (can we just use the MSVC++ precedent of -D_DLL ... well maybe, if we we are C/C++ centric and don't care about languages like Fortran/Ada that don't use a preprocessors), there are issues with .rdata and (yuck) --enable-auto-import vs typeinfo data.
Hacks work today. Hubris is a nice feeling too, today. I see all these smiley faces above me as I type. I prefer the spirit of the GPL that says download the source and submit a patch. Or at least raise the question in a forum where a long-term solution is the focus.
Please help.
Wow, that was heavy.
In the event, when you hit an internal compiler error, please do read the instructions and submit a **useful** bug report .
No fault.
Perseverance Furthers.
Here is a picture of my long-ago friends from another time thinking about Further ...
http://www.lib.virginia.edu/cgi-bin/imgload.cgi/53
OS
pir:
Having a problem getting version 4.2.1 working! (Strictly a mingw/gcc problem, not a CodeBlocks problem but...)
When I try to invoke the compiler (from the command line or from C::B), I get a message:
"mingw32-g++.exe: CreateProcess: No such file or directory"
Here I've renamed the .exe by removing the "-dw2" bits but it makes no difference leaving the "-dw2" naming as is - same error. Flipping the toolchain back to 3.4.5, the thing runs fine with no changes.
Since you guys seem to have got it working OK, any suggestions welcome.
BTW: WinXP-SP2
stahta01:
--- Quote from: pir on August 30, 2007, 11:22:28 am ---Having a problem getting version 4.2.1 working! (Strictly a mingw/gcc problem, not a CodeBlocks problem but...)
When I try to invoke the compiler (from the command line or from C::B), I get a message:
"mingw32-g++.exe: CreateProcess: No such file or directory"
Here I've renamed the .exe by removing the "-dw2" bits but it makes no difference leaving the "-dw2" naming as is - same error. Flipping the toolchain back to 3.4.5, the thing runs fine with no changes.
Since you guys seem to have got it working OK, any suggestions welcome.
BTW: WinXP-SP2
--- End quote ---
Try changing the file name in C::B compiler settings
Under tab "Toolchain Executables" I have
C Compiler: mingw32-gcc.exe
C++ Compiler: mingw32-g++.exe
Linker for Dyn Libs: mingw32-g++.exe
pir:
--- Quote ---Try changing the file name in C::B compiler settings
Under tab "Toolchain Executables" I have
C Compiler: mingw32-gcc.exe
C++ Compiler: mingw32-g++.exe
Linker for Dyn Libs: mingw32-g++.exe
--- End quote ---
Thanks, but I have tried that already. The problem still occurs running the compiler from the command line so it's not really a C::B problem.
thomas:
Do you have the C++ compiler installed at all? This sounds like a stupid question, but it can actually happen.
gcc (or mingw-gcc) is no compiler, you know. It is only a frontend to about half a dozen different compilers that all work via one common interface, and g++ being one of these compilers.
If gcc complains that there is no such file as mingw32-g++.exe, this suggests that you have downloaded the base package, but not the C++ package (or, it could be that paths are set up badly).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version