RE: Problems with 6.x compilers

2005-11-25 Thread Simon Marlow
On 23 November 2005 15:02, [EMAIL PROTECTED] wrote:

6.4 and 6.4.1: When repeating a build (with ghc --make) all
  modules   are rebuild even if nothing has changed. With
  earlier compilers,   only linking takes place in this setting.
  Can I change this   behaviour? I cannot develop this way.
  
   Should not happen, if it does there is a bug.  Can you tell us how
  to  repeat the behaviour you're seeing?  We aren't seeing any
  unecessary  recompilation here.
 
 I think I had that effect exactly when using   -ddump-minimal-imports

Thanks, that is now fixed.

Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


RE: Problems with 6.x compilers

2005-11-23 Thread Simon Marlow
On 22 November 2005 17:18, Michael Marte wrote:

 I am having some annoying problems with the 6.x compilers:
 
 6.4 and 6.4.1: When repeating a build (with ghc --make) all modules
 are rebuild even if nothing has changed. With earlier compilers,
 only linking takes place in this setting. Can I change this
 behaviour? I cannot develop this way.

Should not happen, if it does there is a bug.  Can you tell us how to
repeat the behaviour you're seeing?  We aren't seeing any unecessary
recompilation here.

 6.2 and up: The object file is named after the module, not after the
 source file as in 5.04. As there are several main modules in my
 project, each in its own source file, all I get is a big mess. Any
 suggestions?

The object file is named after the source file, unless you use -odir.
The behaviour is clearly specified in the user's guide:

http://www.haskell.org/ghc/docs/latest/html/users_guide/separate-compila
tion.html#output-files

the behaviour has been through several revisions before we arrived at
this, and I'm not keen to change it.

You can have several Main modules in the same directory if you don't use
-odir.  If you do use -odir, then you need to use a different value for
-odir for each different program.  Alternatively use -main-is, as Bulat
suggested (actually this is better, IMO).

Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: Problems with 6.x compilers

2005-11-23 Thread kahl
  
   6.4 and 6.4.1: When repeating a build (with ghc --make) all modules
   are rebuild even if nothing has changed. With earlier compilers,
   only linking takes place in this setting. Can I change this
   behaviour? I cannot develop this way.
  
  Should not happen, if it does there is a bug.  Can you tell us how to
  repeat the behaviour you're seeing?  We aren't seeing any unecessary
  recompilation here.

I think I had that effect exactly when using   -ddump-minimal-imports


Wolfram
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


RE: Problems with 6.x compilers

2005-11-23 Thread Michael Marte
Simon,

On Wed, 23 Nov 2005, Simon Marlow wrote:

 On 22 November 2005 17:18, Michael Marte wrote:
 
  I am having some annoying problems with the 6.x compilers:
  
  6.4 and 6.4.1: When repeating a build (with ghc --make) all modules
  are rebuild even if nothing has changed. With earlier compilers,
  only linking takes place in this setting. Can I change this
  behaviour? I cannot develop this way.
 
 Should not happen, if it does there is a bug.  Can you tell us how to
 repeat the behaviour you're seeing?  We aren't seeing any unecessary
 recompilation here.

Like Wolfram Kahl, I am using -ddump-minimal-imports.
I cannot check whether the use of this option causes the problem, because 
I returned to 6.2 already to continue porting my project from ghc 5. 

  6.2 and up: The object file is named after the module, not after the
  source file as in 5.04. As there are several main modules in my
  project, each in its own source file, all I get is a big mess. Any
  suggestions?
 
 The object file is named after the source file, unless you use -odir.
 The behaviour is clearly specified in the user's guide:
 
 http://www.haskell.org/ghc/docs/latest/html/users_guide/separate-compila
 tion.html#output-files
 
 the behaviour has been through several revisions before we arrived at
 this, and I'm not keen to change it.
 
 You can have several Main modules in the same directory if you don't use
 -odir.  If you do use -odir, then you need to use a different value for
 -odir for each different program.  Alternatively use -main-is, as Bulat
 suggested (actually this is better, IMO).

I followed the suggestion of Bulat: I renamed the modules and used 
-main-is.

Thanks everybody!
Michael
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: Problems with 6.x compilers

2005-11-22 Thread Bulat Ziganshin
Hello Michael,

Tuesday, November 22, 2005, 8:18:24 PM, you wrote:

MM 6.2 and up: The object file is named after the module, not after the
MM source file as in 5.04. As there are several main modules in my
MM project, each in its own source file, all I get is a big mess. Any
MM suggestions?

you can give different module names to this modules and use -main-is
option to specify main module in each compilation (see
.../ghc/doc/html/users_guide/flag-reference.html)



-- 
Best regards,
 Bulatmailto:[EMAIL PROTECTED]



___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users