Please verify your BCC 6.20 installation, .cfg files. If these are
wrong,
you can still build all other versions of BCC (which happen to be
configured right).
I tried to rename import32.lib from BCC 6.20 to test if it's being
used and I got the following error:
bcc32.exe -q -tWM -w -w-sig- -Q -d -6 -O2 -OS -Ov -Oi -Oc -e..\..\..
\..\..\bin\win\bcc\hbpp.exe hbpp.obj -L../../../../../lib/win/
bcc ../../../../../lib/win/bcc/hbnortl.lib ../../../../../lib/win/
bcc/hbcommon.lib kernel32.lib user32.lib ws2_32.lib advapi32.lib
gdi32.lib
Fatal: Unable to open file 'IMPORT32.LIB'
mingw32-make.exe[3]: *** [hbpp.exe] Error 1
rm hbpp.obj
mingw32-make.exe[2]: *** [descend] Error 2
mingw32-make.exe[1]: *** [pp.inst] Error 2
mingw32-make.exe: *** [source.inst] Error 2
Anyway, I can stick BCC 5.82 at the moment which is working fine.
Thanks again for your time.
So import32.lib is automatically pulled by BCC linker. We can't
really do too much about it.
Anyhow you should still try to fix your BCC .cfg files. Maybe they
point to other BCC version dir.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
