Why is --gen-script creating failing scripts?

Duncan Coutts duncan.coutts at worc.ox.ac.uk
Thu Aug 23 09:51:32 EDT 2007

On Wed, 2007-08-22 at 07:18 +0200, Marc Weber wrote:
> I've been using the recent cabal from ghc-6.7.20070814
> register.sh 
> [...]
> haddock-html: /pr/store/5wivrfz8pmc7hpwqgxgz44i4ihf1ka09-ghc67_filepath-1.0/nix-support/share/filepath-1.0/doc/html/filepath' | /pr/store/khvbwb3whj1c15pg7jrh7w4v2vndr8i7-ghc-6.7.20070814/bin/ghc-pkg update dist/installed-pkg-config -
> marc at localhost /tmp/nix-10368-0/filepath-1.0 $ ghc-pkg list
> /pr/store/khvbwb3whj1c15pg7jrh7w4v2vndr8i7-ghc-6.7.20070814/lib/ghc-6.7.20070814/package.conf:
>     Cabal-1.1.7, [...]
> Please use  either echo and add - or pass the pkg-conf
> dist/installed-pkg-config ..

Yes, it was passing both the file name and - for stdin.

> or did I mess something up?


> If you like I can start debugging the issue and read the source.. But
> propably you know what has been changed ?

Probably a refactoring that changed the behaviour unintentionally. It's
fixed now.

Someone still needs to figure out what --gen-script should do on
Windows. It's almost certainly broken or not useful there as it does not
include the package info inline into the script but relies on being run
from the build tree, which is not very helpful.


More information about the cabal-devel mailing list