On Fri, Oct 17, 2008 at 07:01:41PM +0200, Clemens Fruhwirth wrote: > > The situation at the moment is > > "./configure --enable-shared" gives you stage2 compiler that makes use > of the ghc package in form of a shared lib. So it replaces the static > compiler. With previous incarnations of the build system we had the > possibility to build a "ghc" binary which was the static compiler, and > a "ghc_dyn" binary which was the same compiler but linked to a shared > lib. But now the situation is different, and either "ghc" is produced > shared or not. > > This makes it difficult to integrate into the regular testsuite, as > you can't test shared AND static, you can only test shared OR > static.
So you only want an in-place dynamic ghc, right? i.e. you don't want "make install" to be able to install two executables ghc and ghc_dyn? And therefore we can call both executables 'ghc' but put them in different inplace directories, like we do with the stage1 and stage2 compilers? Thanks Ian _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
