#3598: ghc-stage2 binary name confusing for users
-----------------------------+----------------------------------------------
Reporter:  juhpetersen       |          Owner:                  
    Type:  bug               |         Status:  new             
Priority:  normal            |      Component:  Build System    
 Version:  6.12.0 RC1        |       Severity:  normal          
Keywords:                    |       Testcase:                  
      Os:  Unknown/Multiple  |   Architecture:  Unknown/Multiple
-----------------------------+----------------------------------------------
 ghc-6.12.0.20091010 create a binary called
 $libdir/ghc-6.12.0.20091010/ghc-stage2 and then causing
 the program name ghc-stage2 to appear in compiler output
 and help etc which is confusing for users and a regression
 compared to 6.10.x IMHO.

 eg
 $ ghc
 ghc-stage2: no input files
 Usage: For basic information, try the `--help' option.
 $ ghc --help
 Usage:

     ghc-stage2 [command-line-options-and-input-files]

 To compile and link a complete Haskell program, run the compiler like
 so:

     ghc-stage2 --make Main
 :
 Alternatively, ghc-stage2 can be used to compile files individually.  Each
 input file is guided through (some of the) possible phases of a
 compilation:
 :
 Given the above, here are some TYPICAL invocations of ghc-stage2:

     # compile a Haskell module to a .o file, optimising:
     % ghc-stage2 -c -O Foo.hs
     # link three .o files into an executable called "test":
     % ghc-stage2 -o test Foo.o Bar.o Baz.o
     # compile a Haskell module to C (a .hc file), using a bigger heap:
     % ghc-stage2 -C -H16m Foo.hs
     # compile Haskell-produced C (.hc) to assembly language:
     % ghc-stage2 -S Foo.hc

 etc

 I think either the output text should be changed
 or ghc-stage2 renamed to ghc.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3598>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to