[Scons-users] Intermiddent build error on Windows - cl : Command line error D8022 : cannot open 'c:\users\admini~1\appdata\local\temp\tmpekylod.lnk'

Wed Sep 7 09:16:36 EDT 2016

Shane,

We can look into that specific revision, but if this is a race condition,
then it's possible that this is a problem in other versions. It doesn't
make much sense that the issue is not reproducible in version 2.4.0 unless
there was a missing patch that was reapplied (which is unlikely but not
impossible).

V/R,
William

On Wed, Sep 7, 2016 at 8:30 AM, Shane Gannon <sgannon200 at gmail.com> wrote:

> I've been testing out some scenarios and here is what I discovered
>
> SCons 2.5.0 with vs2013 - Reproduced the problem
>
> SCons 2.3.6 with vs2013 - Reproduced the problem
>
> SCons 2.3.5 with vs2013 - Reproduced the problem
>
> SCons 2.5.0 with vs2013 on Windows 7 - Reproduced the problem
>
> SCons 2.4.0 on both Windows 10 & Window 7 - *Problem not reproduced*
>
> Seems this bug was introduced by Scons 2.3.5.
>
>
> On Wed, Sep 7, 2016 at 11:19 AM, Shane Gannon <sgannon200 at gmail.com>
> wrote:
>
>> @Bill Deegan
>>
>> Both the 2013 & 2015 builders use Windows version 10.0.102540 Build 10240.
>>
>> Windows Defender is disabled on the build machines. We took the attitude
>> that anti-virus protection was a waste of resources. Plus it introduced
>> unwanted variability to build speed.
>>
>> The Windows Search Indexing Service was enabled. But, after disabling it,
>> the problem persisted.
>>
>> I tested out SCons 2.5.0 with vs2013. It reproduced the problem. So this
>> issue may have been introduced since SCons 2.3.4.
>>
>> @Arvid Rosén
>>
>> Good suggestion. But we use ActivePython which has pywin32 built into it.
>> Verified that with pip list.
>>
>> On Wed, Sep 7, 2016 at 8:20 AM, Arvid Rosén <arvid at softube.com> wrote:
>>
>>> Do you have pywin32 installed btw?
>>>
>>> Arvid
>>>
>>> On 07 Sep 2016, at 01:27, Bill Deegan <bill at baddogconsulting.com> wrote:
>>>
>>> Are you also upgrading your version of windows?
>>> Do you see the problem with scons 2.5.0 and MSVC 2013?
>>>
>>> This is not a known issue.
>>> However as Arvid said.. it can be related to Windows Defender and Search
>>> Indexing.
>>> Perhaps you can disable search indexing and see if it has any impact?
>>> You might try disabling windows defender for a short test as well...
>>> (though I wouldn't advise doing so in an insecure environment or for a long
>>> period of time..)
>>>
>>>
>>> On Tue, Sep 6, 2016 at 9:59 AM, Shane Gannon <sgannon200 at gmail.com>
>>> wrote:
>>>
>>>> Hi all
>>>>
>>>> I'm in the process of upgrading a Windows build machine. It's tool set
>>>> is moving to
>>>>
>>>>    - Visual Studio 2015 Update 3
>>>>    - scons 2.5.0
>>>>    - msbuild 14.0.25420.1
>>>>
>>>> from
>>>>
>>>>    - Visual Studio 2013 Update 4
>>>>    - scons 2.3.4
>>>>    - msbuild 12.0.31101
>>>>
>>>> But I'm getting an unexpected error.
>>>>
>>>> *cl : Command line error D8022 : cannot open
>>>> 'c:\users\admini~1\appdata\local\temp\tmpekylod.lnk'*
>>>>
>>>> This can occur once or multiple times in the first clean build. i.e.
>>>> With each occurence for a different file name. But if I then run a rebuild
>>>> the problem resolves itself.
>>>>
>>>> The .lnk file seems to be SCons specific. It's created in the temp
>>>> folder and contains something like
>>>>
>>>> */nologo /DEBUG /dynamicbase /fixed:no /OPT:REF /OPT:ICF -ignore:4042
>>>> -ignore:4042 -ignore:4099 /nologo /DEBUG /dynamicbase /fixed:no /OPT:REF
>>>> /OPT:ICF -ignore:4042 /dll /out:mylibrary.dll .......*
>>>>
>>>> i.e. The command to execute.
>>>>
>>>> On Windows *cl* eats this up with
>>>>
>>>> *cl @c:\users\admini~1\appdata\local\temp\tmpekylod.lnk*
>>>>
>>>> and executes with the parameters found in the .lnk file.
>>>>
>>>> AFAIK this behaviour has existed in SCons since version 0.9.
>>>>
>>>> See
>>>>
>>>> http://www.scons.org/CHANGES.txt
>>>>
>>>> *RELEASE 0.90 - Wed, 25 Jun 2003 14:24:52 -0500*
>>>>
>>>> *  - Use '.lnk' as the suffix on the temporary file for linking long
>>>>     command lines (necessary for the Phar Lap linkloc linker).*
>>>>
>>>> But, for some reason reason, *some* .lnk files are not generated in time for me. Hence the build fails.
>>>>
>>>> Is this a known issue? Has it been introduced since scons 2.3.4? Is there any work around?
>>>>
>>>> I should mention that my builder
>>>>
>>>>
>>>>    - Is a Windows 10 machine
>>>>    - Has 20 cpu cores and runs scons -j 20
>>>>    - Has 25Gb of RAM
>>>>
>>>> There may be a parallization problem here. But it is not an issue for the current build (which also uses -j 20). I experimented with using -j 10 but the problem persisted.
>>>>
>>>> I also choose to build only a sub-set of the projects. i.e. I excluded the tests. This allowed the build to pass.
>>>>
>>>> Any thoughts/suggestions?
>>>>
>>>> Regards
>>>>
>>>> Shane
>>>>
>>>>
>>>> _______________________________________________
>>>> Scons-users mailing list
>>>> Scons-users at scons.org
>>>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>>>
>>>>
>>> _______________________________________________
>>> Scons-users mailing list
>>> Scons-users at scons.org
>>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>>
>>>
>>>
>>> _______________________________________________
>>> Scons-users mailing list
>>> Scons-users at scons.org
>>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>>
>>>
>>
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20160907/21fa7d99/attachment.html>