TDM-GCC 4.9 series (Latest: 4.9.2-tdm-1 - 2014-12-08)

[gd_on]

Quote from: gd_on on December 13, 2014, 08:02:13 pm

   

        On windows, wxWidgets does NOT officially support 2.8 as being 64 bit compatible.

    I have already seen this information. Nevetheless, I have myself compiled wxwidgets 2.8.12 in 64 bits

I can hardly believe that, since wxWidgets 2.8 contains code that casts pointers to int. Which of course doesn't work too well under 64 bits, even if you somehow get the compiler to do this without bailing out.

May be I'm very lucky !!
I have not found any problem in compiling and using C::B 64 with my wxwidgets 2.8.12 64 bits version. All the wxwidgets tests cases I tried, worked as expected.
May be, one day, I'll use such code with int pointers (certainly specific to Windows code), but until this, I cross my fingers !

gd_on

[P@S@f]

I'm very sorry if that question was already asked.

But what I'm supposed to do with that compiler if I want to build something more complicated than "Hello world!" from GNU world?

Am I need to put it in installation of mingw? Or mingw-w64? Or cygwin? Or MSYS? Or MSYS2?

With all mentioned software it is all simple - I could install packages in predefined environment and they will be detected afterwards when needed as dependencies for compiling something else. But what to do with bare metal Windows command  prompt? Add every directory in PATH? Or TDM-GCC do it for me?
I've tried to find at least small tutorial on how to setup environment for TDM-GCC but with no luck.
So I need some help with that.
Oh, to avoid X Y problem - I'm currently trying to build gcc-4.9.2 with non-POSIX mingw-w64-x86_64-gcc and... yep, no luck, <sys/wait.h> not found and so on...
I hope TDM GCC could help me with that.

[stahta01]

I'm very sorry if that question was already asked.

But what I'm supposed to do with that compiler if I want to build something more complicated than "Hello world!" from GNU world?

Am I need to put it in installation of mingw? Or mingw-w64? Or cygwin? Or MSYS? Or MSYS2?

With all mentioned software it is all simple - I could install packages in predefined environment and they will be detected afterwards when needed as dependencies for compiling something else. But what to do with bare metal Windows command  prompt? Add every directory in PATH? Or TDM-GCC do it for me?
I've tried to find at least small tutorial on how to setup environment for TDM-GCC but with no luck.
So I need some help with that.
Oh, to avoid X Y problem - I'm currently trying to build gcc-4.9.2 with non-POSIX mingw-w64-x86_64-gcc and... yep, no luck, <sys/wait.h> not found and so on...
I hope TDM GCC could help me with that.

Trying to build MinGW GCC on Windows is very hard  (I believe it is possible; I could be wrong) most people building Ming GCC builds it under Linux OS after setting up a cross GCC toolchain.

NOTE: Using the TDM GCC Compiler for a more complex program is just like using any compiler with a more complex program.

Edit: If you need Linux GNU compatible environment to run your program then Cygwin is better than MSys.
If you just need a build environment instead run env. then MSys is normally good enough unless you are doing socket programming Cygwin socket programming is closer to Unix/Linux Msys socket programming is like Windows OS.

My copy of Cygwin has a sys/wait.h header for its native gcc compiler.
No idea about TDM GCC or Msys.

Tim S.

[P@S@f]

No, my goal is diametric.
I want to compile gcc for specific target (SH4) to use it in Windows just like TDM-GCC I guess with some IDE without any POSIX environment shells like Cygwin or MSYS. Because if I build something in cygwin or msys that means that I need to run it in that shell or copy thousands of dlls which emulates something I don't need at all and slows down execution speeds of program.
And on the contrary I aspire to native speeds, so I need to avoid using of any POSIX-emulations.

[stahta01]

No, my goal is diametric.
I want to compile gcc for specific target (SH4) to use it in Windows just like TDM-GCC I guess with some IDE without any POSIX environment shells like Cygwin or MSYS. Because if I build something in cygwin or msys that means that I need to run it in that shell or copy thousands of dlls which emulates something I don't need at all and slows down execution speeds of program.
And on the contrary I aspire to native speeds, so I need to avoid using of any POSIX-emulations.

I suggest trying to say what you really want to do!

Edit: If you want to build GCC I strongly suggest using Linux!!

I still DO NOT know if you want to build or use GCC!!

And, you have no idea what Msys is; and only a slight idea what an IDE is.

Edit2: I suggest read the rules before you are banned from this site http://forums.codeblocks.org/index.php/topic,9996.0.html

Tim S.

[P@S@f]

I wrote twice that I want to build regular GCC 4.9.2 with targetting of SH4 (Hitachi SuperH 4 processor) outwards of any POSIX environment.

I following the rules because I'm not asking general programming questions and I do not ask to do something for me. Is this thread not for supporting TDM-GCC users? If no then sorry, but I need confirmation from topic starter and it is not you.

And please do not share your opinion about my knowing of things. It is not gentle.

[stahta01]

I wrote twice that I want to build regular GCC 4.9.2 with targetting of SH4 (Hitachi SuperH 4 processor) outwards of any POSIX environment.

I following the rules because I'm not asking general programming questions and I do not ask to do something for me. Is this thread not for supporting TDM-GCC users? If no then sorry, but I need confirmation from topic starter and it is not you.

And please do not share your opinion about my knowing of things. It is not gentle.

So ask a question on topic in this thread or for this site.
Ask TDM what steps he used to build TDM.

Because building GCC (for an non window target) is NOT an valid topic for this site; please read and follow the rules or I will ask that you be banned!

Tim S.

[P@S@f]

You don't get it.
I said that just to avoid X-Y problem.
What I'm asking is strongly related to this topic.

My question was - how to setup TGM-GCC in MSYS or something that allow me to build UNIX programs easily (jus by typing ./configure && make)?

[thomas]

You don't get it.
I said that just to avoid X-Y problem.
What I'm asking is strongly related to this topic.

My question was - how to setup TGM-GCC in MSYS or something that allow me to build UNIX programs easily (jus by typing ./configure && make)?

Well no, it's not strongly related, although I can see where your confusion comes from.

This site/forum is about Code::Blocks, and to keep the noise level down, our rules don't allow non-Code::Blocks content (for legal reasons -- server being located in Germany -- the moderators have to read through all posts, so there is a practical reason to keep noise down).

That actually means that the entirety of TDM threads don't belong here since they're not related to Code::Blocks at all,  but it so happens that John is a cool guy and he makes cool compiler build which is also the best fit both for building and using Code::Blocks, so whatever the rules are,  this is OK for us, and we're not going super-prick on him   

Now of course, your question about setting up a Unix-like build environment is a totally different thing (and besides, it's nowhere like you type ./configure && make to build GCC, only in your dreams -- I wish it was that easy!). Which is what stahta01 tried to point out.

[MortenMacFly]

Is there a possibility to share the bfd libs from the build so we can build a new exchndl (crash handler) against this version of GCC? Without it the build will not succeed and the old version will not work (at least for me - it makes C::B and other wx apps hang forever).

[MortenMacFly]

That actually means that the entirety of TDM threads don't belong here since they're not related to Code::Blocks at all,  [...]

Well, no:
1.) C::B is build using exactly these compilers
2.) C::B ships wit exactly this (and only this) compiler.

So I'd say its definitely a C::B topic... but maybe more for the C::B developers.

[TDragon]

I think this forum is the perfect place for both developers of Code::Blocks and developers that use TDM-GCC with Code::Blocks to be apprised of updates. If at any time TDM-GCC becomes no longer relevant, I will happily cease.

Regarding bfd, GCC itself doesn't include it, so do you mean the bfd from TDM64 binutils, or

[ollydbg]

Regarding bfd, GCC itself doesn't include it, so do you mean the bfd from TDM64 binutils, or

bfd is built when you build gdb. Normally, running "make -C gdb install" is enough, which means libbfd is not installed.

[TDragon]

The 32-bit TDM-GCC uses the MinGW project's binutils package - that's probably where you should get libbfd.a from:
https://sourceforge.net/projects/mingw/files/MinGW/Base/binutils/binutils-2.24/binutils-2.24-1-mingw32-dev.tar.xz/download

[MortenMacFly]

The 32-bit TDM-GCC uses the MinGW project's binutils package - that's probably where you should get libbfd.a from:
https://sourceforge.net/projects/mingw/files/MinGW/Base/binutils/binutils-2.24/binutils-2.24-1-mingw32-dev.tar.xz/download

Yes, there it is. :-) Thank you...

However, I just figured out that we (I) use a completely outdated version of exchndl. "jrfonseca" did a great job in continuously further developing it - he just switched from SVN to GIT and I didn't realise. So maybe we don't even need to compile it ourselves any longer. He ships binaries (Version 0.6.4 currently) for 32 and 64 bit also supporting DWARF meanwhile.

If at any time TDM-GCC becomes no longer relevant, I will happily cease.

NOOOOOOOOO! ;-)