> > Harbour make system isn't doing any magic with tlib. It's just running >> tlib.exe and uses what's found by normal OS means. >> > > It seems not as if I run > > tlib > > from the same console I get the correct 32 bit tlib. > > Anyway, no problems for me as I renamed the old tlib. > > Could be that own BCC make.exe was looking into its own dir first. >> > > No, it was working fine two days ago with the new make system.
Nothing changed in Harbour in this regard, you can verify the commits on Trac. > Yes, but the problem must be elsewhere, in my opinion. > Since everyone is tweaking their local environments lately I rather suspect it caused by such thing. F.e you already reported old tlib problem a few days ago, plus you've changed your env after switching to mingw32-make.exe AFAIR. I've just put TLIB.EXE (DOS) in my PATH after BCC and it wasn't executed by MinGW make (v 3.81). Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
