| Commit message (Collapse) | Author | Age |
|
|
|
| |
Thanks, Sean T Parsons
|
| |
|
| |
|
|
|
|
| |
I think there'a a cygwin git in path confusing things
|
|
|
|
| |
fatal: Invalid path '/cygdrive/c/jenkins/workspace/git-annex-master/git-annex/.stack-work/downloaded/C:\jenkins\workspace\git-annex-master\git-annex\.stack-work\downloaded\56E6vnUQljVi': No such file or directory
|
|
|
|
|
|
|
|
|
| |
Get ugly reversion out of CHANGELOG.
Also, relocated the windows stack.yaml to top, and updated windows build
instructions.
This commit was sponsored by Henrik Riomar on Patreon.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
and git for windows includes curl which git-annex will use instead.
wget was broken even in the previous old release of the windows bundle,
this is not new breakage. msys-idn-11.dll and probably more would be needed
to use it. git for windows includes msys-idn2-0.dll instead.
|
| |
|
|
|
|
|
| |
git-annex is installed into . by Build/NullSoftInstaller, so use that
for running git-annex test
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
Seems to want to recompile git-annex before running unrelated program.
stack ghc does not have that problem
|
| |
|
| |
|
|
|
|
|
|
| |
Which old witch? The EvilLinker witch!
This commit was sponsored by Thom May on Patreon.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code for terminating processes on Windows is not linking anymore;
made a warning be displayed instead. This breaks restarting the
assistant and git annex assistant --stop.
I hope to see the code added to the Win32 library, where it should fit
better and should avoid whatever problem is making the linker not like it
when included in git-annex. I opened an issue requesting its addition,
here: https://github.com/haskell/win32/issues/91
This commit was sponsored by Thomas Hochstein on Patreon.
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit d6d0b1fe20397bf073f11d579f5c0c38785e071a.
Neither way is working.. The other way failed:
.stack-work\dist\5f9bc736\build\git-annex\git-annex-tmp\Assistant.o:fake:(.text+0x6bb3): undefined reference to `terminatepid'
Seems that winprocess.c is not getting linked in.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Building with stack, it failed:
`_TerminateProcess' referenced in section `.text' of .stack-work\dist\5f9bc736\build\git-annex\git-annex-tmp\Utility\WinProcess.o: defined in discarded section `.text' of C:/Users/jenkins/AppData/Local/Programs/stack/i386-windows/ghc-8.0.2/mingw/bin/../lib/gcc/i686-w64-mingw32/5.2.0/../../../../i686-w64-mingw32/lib/../lib/libkernel32.a(dacgs01154.o)
This is a reversion of 6d66a81ca98f8579bf06f7fb724ed733670d39b9,
to try the other way to implement it, which will hopefully avoid the problem.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
content.
|
|/ |
|
| |
|
| |
|
|
|
|
|
| |
Seeing interrmittent build failures that may be related to stack's
concurrency
|
| |
|
|
|
|
| |
toolchain issue is preventing nightly from building anything on windows
|
|
|
|
|
|
|
|
|
| |
This needs to include unix except on windows, but when I tried
an if (! os(windows)) cabal crashed:
'parseField' called on a non-field. This is possibly a bug in Cabal.
Cabal is able to configure w/o the custom-setup stanza, so omit it.
|
| |
|
| |
|
| |
|
| |
|
| |
|