> > It is, but since nothing changed in this regard inside Harbour, >> probably you have an old (DOS) tlib.exe hanging in the PATH. >> > > Yes, I have an old tlib.exe in the PATH but it was there since years > without problems. It seems that the PATH order is not respected anymore. I > specified > > SET PATH=e:\bcc55\bin;%PATH% > > and if I run > > tlib > > from the console I get the correct 32 bit one that is in e:\bcc55\bin while > the new Harbour make system use the old one that is in e:\utl (it is in > %PATH%). Why? Any ideas? > > For now I've renamed the old tlib.exe in tlib16.exe but I don't think this > is a proper fix. Isn't it?
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. Could be that own BCC make.exe was looking into its own dir first. Mixing different compiler tools in PATH is never a good practice IMO. There are several ways to avoid that, maybe the simplest is to use 'mingw make dir', 'c compiler dir', '%PATH% or nothing' in your PATH. Your mileage may vary. Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
