User forums > General (but related to Code::Blocks)
GCC 4.4.1-tdm-2 for MinGW (with installer)
ollydbg:
--- Quote from: eranif on March 21, 2010, 06:14:08 am ---
--- Quote ---c:/mingw/bin/../lib/gcc/mingw32/4.4.1/../../../../mingw32/bin/ld.exe: <unknown-file>:0: syntax error
Warning: .drectve `-export:T.848 ' unrecognized
c:/mingw/bin/../lib/gcc/mingw32/4.4.1/../../../../mingw32/bin/ld.exe: <unknown-file>:0: syntax error
Warning: .drectve `-export:T.566 ' unrecognized
--- End quote ---
Its not a TDM-GCC only error. I compiled wxWidgets with GCC4.4.0 (the one that is officially released by the MinGW project) and the same error exists.
Note that the produced import library+DLL are very much usable and I did not notice any errors while using them (for 6 months at least)
Eran
--- End quote ---
I use tdm gcc for nearlly one year, and each time I build wxWdiget library, I have noticed this kind of warning. But these warning never hurt the usage of wxWidget library. :D
So, it seems the problem is in the wxWidgets source itself.
reckless:
not quite its a bug with the ld in binutils-0.20 it seems upgrading to binutils-0.20.1 fixed it for me atleast.
tor lilquist noticed the same with his crosscompiler suite for suse.
stefanos_:
@reckless: Even though I have followed your recommendation and have replaced binutils from MinGW's official website, the warning(s) / error(s) remain the same; BUT, I have also replaced mingw32-make as well some other tools and now Code::Blocks load just fine.
@erafin: It was unnecessary to do such thing because the problem probably was with mingw32-make.
The tools I have replaced are these:
TDM's GCC
========
binutils (2.19.1) ------> Have been replaced with MinGW's binutils (2.20.1-2)
gdb (6.8.3) ------> Has been replaced with MinGW's gdb (7.1-1)
mingw-runtime (3.16) ------> Has been replaced with mingwrt (dev / dll 3.18)
mingw32-make (3.81 - 20080326-3) ------> Has been replaced with mingw32-make (3.81 - 20090914)
And w32api which was the same I have replaced it just for fun.
Now everything seems to work OK. If I have any other issues I will surely let you know.
reckless:
glad it worked out :) i allready had the other updated packages but recieved the same error untill i got latest ld,
i guess some of it actually depended on it hence why i got the error untill i updated my binutils.
Navigation
[0] Message Index
[*] Previous page
Go to full version