Commit f2a3fac6 authored by Ian Lynagh's avatar Ian Lynagh
Browse files

Update Windows output for ghcpkg0[35]

parent cbc8f104
testpkg-1.2.3.4: Warning: library-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
testpkg-1.2.3.4: Warning: include-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
testpkg-1.2.3.4: import-dirs: /usr/local/lib/testpkg is a relative path (ignoring)
testpkg-1.2.3.4: import-dirs: /usr/local/lib/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-1.2.3.4: import-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory (ignoring)
testpkg-1.2.3.4: library-dirs: /usr/local/lib/testpkg is a relative path (ignoring)
testpkg-1.2.3.4: include-dirs: /usr/local/include/testpkg is a relative path (ignoring)
testpkg-1.2.3.4: library-dirs: /usr/local/lib/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-1.2.3.4: include-dirs: /usr/local/include/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-1.2.3.4: file A.hi is missing (ignoring)
testpkg-1.2.3.4: file B.hi is missing (ignoring)
testpkg-1.2.3.4: file C\D.hi is missing (ignoring)
testpkg-1.2.3.4: cannot find libtestpkg-1.2.3.4.a on library path (ignoring)
testpkg-2.0: Warning: library-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
testpkg-2.0: Warning: include-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
testpkg-2.0: import-dirs: /usr/local/lib/testpkg is a relative path (ignoring)
testpkg-2.0: import-dirs: /usr/local/lib/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-2.0: import-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory (ignoring)
testpkg-2.0: library-dirs: /usr/local/lib/testpkg is a relative path (ignoring)
testpkg-2.0: include-dirs: /usr/local/include/testpkg is a relative path (ignoring)
testpkg-2.0: library-dirs: /usr/local/lib/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-2.0: include-dirs: /usr/local/include/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-2.0: file A.hi is missing (ignoring)
testpkg-2.0: file B.hi is missing (ignoring)
testpkg-2.0: file C\D.hi is missing (ignoring)
......@@ -21,10 +21,10 @@ testpkg-2.0: file C\E.hi is missing (ignoring)
testpkg-2.0: cannot find libtestpkg-2.0.a on library path (ignoring)
testpkg-1.2.3.4: Warning: library-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
testpkg-1.2.3.4: Warning: include-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
testpkg-1.2.3.4: import-dirs: /usr/local/lib/testpkg is a relative path (ignoring)
testpkg-1.2.3.4: import-dirs: /usr/local/lib/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-1.2.3.4: import-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory (ignoring)
testpkg-1.2.3.4: library-dirs: /usr/local/lib/testpkg is a relative path (ignoring)
testpkg-1.2.3.4: include-dirs: /usr/local/include/testpkg is a relative path (ignoring)
testpkg-1.2.3.4: library-dirs: /usr/local/lib/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-1.2.3.4: include-dirs: /usr/local/include/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}. (ignoring)
testpkg-1.2.3.4: file A.hi is missing (ignoring)
testpkg-1.2.3.4: file B.hi is missing (ignoring)
testpkg-1.2.3.4: file C\D.hi is missing (ignoring)
......
There are problems in package testpkg-2.0:
Warning: library-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
Warning: include-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
import-dirs: /usr/local/lib/testpkg is a relative path
import-dirs: /usr/local/lib/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}.
import-dirs: c:/Program Files/testpkg doesn't exist or isn't a directory
library-dirs: /usr/local/lib/testpkg is a relative path
include-dirs: /usr/local/include/testpkg is a relative path
library-dirs: /usr/local/lib/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}.
include-dirs: /usr/local/include/testpkg is a relative path which makes no sense (as there is nothing for it to be relative to). You can make paths relative to the package database itself by using ${pkgroot}.
file A.hi is missing
file B.hi is missing
file C\D.hi is missing
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment