> Am 21.02.2021 um 17:52 schrieb Erich Steinböck <erich.steinbo...@gmail.com>: > > Hi P.O., > > > \Microsoft was unexpected at this time. > > I cannot figure out what is wrong in this call? > In my setbuild.bat I can successfully run vcvarsall.bat like this: > > call "C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 > ********************************************************************** > ** Visual Studio 2017 Developer Command Prompt v15.9.5 > ** Copyright (c) 2017 Microsoft Corporation > ********************************************************************** > [vcvarsall.bat] Environment initialized for: 'x64' > This is what puzzles me, I had this running earlier (say a year ago) and I did not intentionally change anything, When I execute the same call I get
C:\Users\po>call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 ********************************************************************** ** Visual Studio 2017 Developer Command Prompt v15.9.33 ** Copyright (c) 2017 Microsoft Corporation ********************************************************************** \Microsoft was unexpected at this time. The 4 first lines seems to indicate that vcvarsall.bat starts to run but chokes on the path? I must have messed up the computer when I was fiddling with Publican. I will see if I can reinstall it fresh and start from scratch. > > > Here the test cases that are failing > SpecialFolders and WindowsEventLog test groups haven't been addressed yet - > this is why we typically exclude them > You're also seeing additional failures and informational messages because you > run tests with a high verbose value > > > Test: TEST_VOLUME_SPECIFICATIONS > > Class: SYSDRIVE.TESTGROUP > > File: ...\ooRexx\base\rexxutil\platform\windows\SysDrive.testGroup > > Line: 103 > Do you have no volume label on your C: drive? > The test tries to verify that SysVolumeLabel works by assuming C: has an > actual volume label set I do have a C: and if I do a dir c: I get a response. Again, maybe the machine is rotten (I do not use it much). I do know that I failed to get the stuff with Nsis_longStrings to work, so some of the errors are from there I think. I will reinstall and see if things get better. > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
