On 13/05/2009 19:53, Donnie Jones wrote:
Hello Dan,
Best place to ask is glasgow-haskell-users@haskell.org since that is
the GHC users list.
I have CC'd your email to the GHC user list.
Cheers.
--
Donnie Jones
On Wed, May 13, 2009 at 1:35 PM, Dandanielkc...@gmail.com wrote:
Hi,
Not sure if
Hello Dan,
Best place to ask is glasgow-haskell-users@haskell.org since that is
the GHC users list.
I have CC'd your email to the GHC user list.
Cheers.
--
Donnie Jones
On Wed, May 13, 2009 at 1:35 PM, Dan danielkc...@gmail.com wrote:
Hi,
Not sure if this is the right place to ask.
GHC
On Tuesday 01 May 2007 13:02, Claus Reinke wrote:
[...] would it be possible
to have a configuration package with nothing but the common checks? then
every package, and ghc itself, could depend on that package being there,
and every package configure could modularly use the information from that
C.M.Brown wrote:
I've noticed that when you run ./configure on a ghc build lot's of
repetition occurs. A lot of the time the same checks are being performed for
each configure file in the ghc hierarchy. Could it be possible if some of
these checks could be done once at a high level and then
Hi Simon,
Mainly this is due to modularity: many of the library packages can be built
entirely separately from GHC, so their configure scripts are designed to be
standalone.
Yes, I guess it would be a fair bit of work to have it check that you are
building the whole of GHC as opposed to
Mainly this is due to modularity: many of the library packages can be built
entirely separately from GHC, so their configure scripts are designed to be
standalone.
library packages are haskell packages, and much of the configuration data
should be common (plus a few package-specific checks).
Hi,
I've noticed that when you run ./configure on a ghc build lot's of
repetition occurs. A lot of the time the same checks are being performed for
each configure file in the ghc hierarchy. Could it be possible if some of
these checks could be done once at a high level and then subsequent
