I think Avast is acceptable antivirus (boot-time scan is very useful)
and last Delf-Zbot false positive alarm (which hit me as many else)
do not change my opinion))
With the will to help good Avast Team in their syzifical work
i send one more rock… oh no… false alarm))
to their collection))
My ill-story:
i try to configure-make-makeinstall GHC haskell 6.6.1 on win-xp
from sources with mingw gcc-3.4.5 (20060117-3 mingw-vista special r3).
This gcc used - from the not-so-fresh MLton7016.msi (sized 45840012,
MSYS readme.rtf dated 2008-08-26)
which i occasionally have in my disposal when i need some gcc3 compiler.
Avast make false alarms on very beginning of
sh configure
where configure try test if gcc working.
here is C source which configure script try to compile with gcc
—cut-here-8<--------------------------------------
#line 3010 “configure”
/* confdefs.h. */
#define PACKAGE_NAME “The Glorious Glasgow Haskell Compilation System”
#define PACKAGE_TARNAME “ghc”
#define PACKAGE_VERSION “6.6.1”
#define PACKAGE_STRING “The Glorious Glasgow Haskell Compilation System 6.6.1”
#define PACKAGE_BUGREPORT “glasgow-haskell-bugs@haskell.org”
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
—cut-here-8<--------------------------------------
this godly-innocent source is compiled to confdefs.exe
(sized 15671 bytes) by usual command
gcc -o confdefs confdefs.c
and at time of linking… Avast alarms!!!))
Of course my Avast bases is current. 091203-1. I just check it again.
…meanwhile, i already found temporarly solution which helps me.
here is it:
cd mingw\lib
strip -g *.o *.a
and now, without debugging symbols in mingw libs, gcc normally
links stripped confdefs.exe (15183 bytes) on which Avast not alarms…