Author Topic: GCC 4.2.1 binary release for mingw is available from MINGW  (Read 49651 times)

wxLearner

  • Guest
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #15 on: August 09, 2007, 04:10:59 pm »
Quote from: stahta01
No, I do have libstdc++ DLL
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.

Offline TDragon

  • Lives here!
  • ****
  • Posts: 943
    • TDM-GCC
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #16 on: August 09, 2007, 04:56:07 pm »
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?
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; ...
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.
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).

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.
I wasn't aware of anything like this; I wonder who it was?
https://jmeubank.github.io/tdm-gcc/ - TDM-GCC compiler suite for Windows (GCC 9.2.0 2020-03-08, 32/64-bit, no extra DLLs)

Offline snija

  • Multiple posting newcomer
  • *
  • Posts: 20
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #17 on: August 10, 2007, 05:20:07 am »
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?

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7582
    • My Best Post
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #18 on: August 10, 2007, 08:02:13 pm »
Quote
no include in the root mingw directory
You forgot to do BinUtils and Runtime.

why they use a wired lib\gcc\mingw32\4.2.1-sjlj\include\c++ include directory?

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

« Last Edit: August 10, 2007, 08:04:16 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline snija

  • Multiple posting newcomer
  • *
  • Posts: 20
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #19 on: August 10, 2007, 08:30:58 pm »
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?

Offline dwmcqueen

  • Multiple posting newcomer
  • *
  • Posts: 56
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #20 on: August 14, 2007, 01:53:56 pm »
There has been a new release that supposedly fixed some of the bugs people were noticing from MinGW.

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #21 on: August 14, 2007, 02:30:29 pm »
thanks for the info !!!

EDIT : trying to build wx284, with the dwarf (DW2) variant, in bin dir I removed the -dw2 from the gcc exes (not from the mingw32-*.exe)

EDIT2 : failed -> windres ...... on ../../src/msw/version.rc:12:24 error: wx/version.h : no such file or directory  :-(
« Last Edit: August 14, 2007, 02:55:48 pm by killerbot »

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #22 on: August 14, 2007, 02:53:10 pm »
mingw32-g++-dw2.exe -Ldevel -Lsrc\wxAUI -Lbase\tinyxml -LD:\wxMSW-2.8.4\lib\gcc_dll -LC:\gcc42\lib  -o devel\codeblocks.exe .objs\src\app.o .objs\src\appglobals.o .objs\src\associations.o .objs\src\compilersettingsdlg.o .objs\src\crashhandler.o .objs\src\dlgabout.o .objs\src\dlgaboutplugin.o .objs\src\environmentsettingsdlg.o .objs\src\infopane.o .objs\src\ipc.o .objs\src\main.o .objs\src\printdlg.o .objs\src\scriptconsole.o .objs\src\scriptingsettingsdlg.o .objs\src\splashscreen.o .objs\src\startherepage.o  .objs\src\resources\resources.res  --demangle  -lcodeblocks -lwxaui -lwxscintilla -lshfolder -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lcomctl32 -lodbc32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lwxmsw28u  -mwindows
.objs\src\app.o: In function `wxMemoryFSHandler':
Info: resolving SquirrelVM::_VM       by linking to __imp___ZN10SquirrelVM3_VME (auto-import)
D:/wxMSW-2.8.4/include/wx/fs_mem.h:60: undefined reference to `_imp___ZTV17wxMemoryFSHandler'
collect2: ld returned 1 exit status
Process terminated with status 1 (8 minutes, 37 seconds)
1 errors, 1996 warnings


Yay for MinGW! Compiling Code::Blocks works again :)


EDIT:  The linker error is no real error, since I've used the 3.4.5 libraries, this obviously cannot work. But most importantly, the compilation is just fine :)  Now off to rebuild wxWidgets...
« Last Edit: August 14, 2007, 02:56:16 pm by thomas »
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #23 on: August 14, 2007, 04:14:54 pm »


There goes! :)
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #24 on: August 14, 2007, 04:16:22 pm »
did you use the dwarf or the other ? Since I got stuck at wx :-(

EDIT : it seems it has to do with windres.exe, I used the latest snapshot of binutils [remember the one where the fix is there for windres.exe for files/paths containing spaces], well it seems it has new problems now.
So I replaced the windres.exe with the one from the previous release of the binutils and I can get past my error point ...

Fix one, break one, so it seems ...

EDIT2 : I heard a MinGW developer visits our forum, I hope you see this ;-)
« Last Edit: August 14, 2007, 04:39:59 pm by killerbot »

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #25 on: August 14, 2007, 04:58:08 pm »
I used the Dwarf2 version with the whatever-version-binutils that I'm using with my 3.4.5.

First, I edited CC and CPP in build/msw/config.gcc as this should actually be the correct way. Of course it didn't work... lol... now thinking about it, I didn't honestly expect it to work either, that would have been the first painless wxWidgets build :P

But seriously, as this failed, I just renamed the -dw2.exe files, and it worked nicely. Compiling wxWidgets gives about 300,000 compiler warnings, as usual, but hey... compiling Code::Blocks gives about 2000 warnings (almost all of them from wxWidgets). But hey, it works great otherwise :)
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #26 on: August 14, 2007, 05:03:31 pm »
Quote
compiling Code::Blocks gives about 2000 warnings (almost all of them from wxWidgets)

f***, holy crap, I hope those wx guys will do something about their warnings some day.

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #27 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.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline dwmcqueen

  • Multiple posting newcomer
  • *
  • Posts: 56
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #28 on: August 14, 2007, 11:02:52 pm »
So our the nightly builds going to move to 4.2.1 anytime soon ;)

insert_coin()

  • Guest
Re: GCC 4.2.1 binary release for mingw is available from MINGW
« Reply #29 on: August 17, 2007, 08:47:42 am »
Maybe it is not the correct place for this question, but does anyone know how to link mingwm10.dll statically?