User forums > General (but related to Code::Blocks)

GCC 4.2.1 binary release for mingw is available from MINGW

<< < (4/12) > >>

wxLearner:

--- Quote from: stahta01 ---No, I do have libstdc++ DLL
--- End quote ---
Me too. But it depends on a shared libgcc, which I do not find.

I have tried to throw an exception from a dll and catch it in an exe, but it does not work any longer with a statically linked runtime.

TDragon:

--- Quote from: patlecat on August 09, 2007, 09:44:57 am ---Wow finally they did it. But TD can you tell us what took them so long? And when can we expect the next full MingW release?

--- End quote ---
My answer to why it took so long would be to quote Greg Chicares from the MinGW lists:

--- Quote ---If you wait to release until the software becomes stable, then it might be later than you'd like. If you opt to release earlier, then it might be less stable than you'd like. There are some people who choose a less-conservative tradeoff than the MinGW project; ...

--- End quote ---
and Keith Marshall:

--- Quote ---We have one individual, (Danny), who is willing to manage GCC releases; he takes a cautious approach to that, for reasons which only he can definitively explain.

--- End quote ---
The next release? Probably shortly after GCC 4.3.0 is released (which will be labeled 4.4.0 if GCC goes ahead with their totally weird GPLv3 rebranding scheme).


--- Quote from: dwmcqueen on August 09, 2007, 03:51:06 pm ---I can tell you - they were ready to issue the binaries, but not ready to support the release since they were still too busy on the prior release.  Someone stepped in and offered to help support the release - so they released it.

--- End quote ---
I wasn't aware of anything like this; I wonder who it was?

snija:
Somebody can tell me why there`s no include in the root mingw directory and why they use a wired lib\gcc\mingw32\4.2.1-sjlj\include\c++ include directory?

stahta01:

--- Quote --- no include in the root mingw directory
--- End quote ---
You forgot to do BinUtils and Runtime.


--- Quote from: snija on August 10, 2007, 05:20:07 am ---why they use a wired lib\gcc\mingw32\4.2.1-sjlj\include\c++ include directory?

--- End quote ---

Because that is the way MinGW does it; it is in order to do more than one version of GCC in a top level MInGW folder, but I don't try to do that. So, I have no idea how or if it works well.

Tim S

snija:
Thanks, I used to install binutils and w32api in separated folders and add their path into environment variables (C_INCLUDE_PATH & CPLUS_INCLUDE_PATH & LIBRARY_PATH).
If they use it in that way which means that you must unpacked it to c:\ otherwise .....
ignoring nonexistent directory "/mingw/lib/gcc/mingw32/4.2.1-dw2/include/c++"
ignoring nonexistent directory "/mingw/lib/gcc/mingw32/4.2.1-dw2/include/c++/min
gw32"
ignoring nonexistent directory "/mingw/lib/gcc/mingw32/4.2.1-dw2/include/c++/bac
kward"
ignoring nonexistent directory "/mingw/include"
I have to follow it and create a wired include directory "\include\c++\4.2.1-sjlj".
BTW, who actually find that libgcc_s_****.dll?

Navigation

[0] Message Index

[#] Next page

[*] Previous page