# Can not compile ROOT macro on Win10: picking up paths to other SW

XMLWordPrintable

#### Details

• Type: Bug
• Status: Closed
• Priority: Low
• Resolution: Fixed
• Affects Version/s: 6.22/00
• Fix Version/s:
• Component/s: None
• Labels:
None
• Environment:

Windows 10

HP ProtectTools

• Development:

#### Description

Dear developers,

when trying to compile a ROOT macro in ROOT 6.22.00 on windows, beside the problem mentioned in #ROOT-10925, I am getting another error at the linking stage:

LINK : fatal error LNK1181: cannot open input file 'c:\program.obj'

It is due to the following path being used while linking:

C:\Program Files (x86)\HP\HP ProtectTools Security Manager\Bin\DpoFeedb.dll

(thus obviously specific to my setup). However, would you have any idea why this path is picked up by ROOT and how I could prevent it ? I can see the HP path in the list returned by:

gSystem->GetLibraries()

I do not see that HP in %PATH% environmental variable of Windows 10. The only place where it is defined is a specific system variable(s) PTSMINSTALLPATH(_X86) and thus I am confused why ROOT tries to pick that up.

Thanks, Pavel

PS: Of course I have in mind other solution that removing the HP SW. It is quite likely such interference can also happen with other SW and thus would be useful to find the mechanism of that happening.

#### People

Assignee:
Bertrand Bellenot
Reporter:
Pavel Reznicek