Repository : ssh://darcs.haskell.org//srv/darcs/testsuite

On branch  : master

http://hackage.haskell.org/trac/ghc/changeset/364e01a45027bd0a0117befb10b3941641973207

>---------------------------------------------------------------

commit 364e01a45027bd0a0117befb10b3941641973207
Author: Ian Lynagh <[email protected]>
Date:   Thu Jun 23 16:23:56 2011 +0100

    Update Windows output for ghcpkg0[35]

>---------------------------------------------------------------

 .../cabal/ghcpkg03.stderr-i386-unknown-mingw32     |   18 +++++++++---------
 .../cabal/ghcpkg05.stderr-i386-unknown-mingw32     |    6 +++---
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/tests/ghc-regress/cabal/ghcpkg03.stderr-i386-unknown-mingw32 
b/tests/ghc-regress/cabal/ghcpkg03.stderr-i386-unknown-mingw32
index 59afce7..71ff88a 100644
--- a/tests/ghc-regress/cabal/ghcpkg03.stderr-i386-unknown-mingw32
+++ b/tests/ghc-regress/cabal/ghcpkg03.stderr-i386-unknown-mingw32
@@ -1,19 +1,19 @@
 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)
diff --git a/tests/ghc-regress/cabal/ghcpkg05.stderr-i386-unknown-mingw32 
b/tests/ghc-regress/cabal/ghcpkg05.stderr-i386-unknown-mingw32
index 45ce648..360783b 100644
--- a/tests/ghc-regress/cabal/ghcpkg05.stderr-i386-unknown-mingw32
+++ b/tests/ghc-regress/cabal/ghcpkg05.stderr-i386-unknown-mingw32
@@ -1,10 +1,10 @@
 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



_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to