On 17 March 2005 23:03, Andy Moran wrote:
Malcolm Wallace wrote:
Andy Moran [EMAIL PROTECTED] writes:
I notice that cpphs understands CPP stringification (if invoked with
--hashes). Most of the gcc 3.4 failures (in fact, all of that I've
seen) have to do with fooling -traditional into
On 17 March 2005 17:23, Malcolm Wallace wrote:
The only real issue currently preventing ghc from adopting cpphs is
ideological (GPL licensing).
We've no objection to making changes to GHC to make it easy to use in
conjuction with cpphs (./configure --with-cpps or whatever), so
3rd-party
Andy Moran [EMAIL PROTECTED] writes:
-- hackery to convice cpp to splice GHC_PKG_VERSION into a string
version :: String
version = tail \
\ GHC_PKG_VERSION
OK, it turns out that this is pretty tricky to do in cpp, even with
full scope of -ansi or -traditional behaviour. In fact, the
Hi all,
I need Haskell to be installed on a Red advance server 3. Could not find
RPM's
for it. Tried compiling for tar file, won't pass the ./configure, giving
me configure: error: GHC is required unless bootstrapping from .hc
files. error.
Could someone give me some pointers on how to do this?
On Thu, Mar 17, 2005 at 10:02:56AM -0500, Francois Meehan wrote:
Hi all,
I need Haskell to be installed on a Red advance server 3. Could not find
RPM's
for it. Tried compiling for tar file, won't pass the ./configure, giving
me configure: error: GHC is required unless bootstrapping from .hc
Tomasz Zielonka wrote:
On Thu, Mar 17, 2005 at 10:02:56AM -0500, Francois Meehan wrote:
Hi all,
I need Haskell to be installed on a Red advance server 3. Could not find
RPM's
for it. Tried compiling for tar file, won't pass the ./configure, giving
me configure: error: GHC is required unless
A million thanks Tomasz,
Worked like a charm.
Have a nice day!
Francois
On Thu, Mar 17, 2005 at 10:02:56AM -0500, Francois Meehan wrote:
Hi all,
I need Haskell to be installed on a Red advance server 3. Could not find
RPM's
for it. Tried compiling for tar file, won't pass the
Andy Moran [EMAIL PROTECTED] writes:
With 3.4, changes were made to the
-traditional version of the C preprocessor that make it incompatible
with the way in which many of the Haskell modules in the GHC source tree
reify make/build variables as Haskell strings.
Malcolm Wallace wrote:
Have we converged on a long-term solution for this problem? Is hscpp
ready for the job?
I believe cpphs is in good shape. There has been one bug report, and
no new feature requests, in the last 4 months since 0.8 was released,
with 235 downloads of that version. Over a
Andy Moran wrote:
I notice that cpphs understands CPP stringification (if invoked with
--hashes). Most of the gcc 3.4 failures (in fact, all of that I've seen)
have to do with fooling -traditional into turning macro constants into
Haskell strings, which can more readily be done with the
Andy Moran [EMAIL PROTECTED] writes:
I notice that cpphs understands CPP stringification (if invoked with
--hashes). Most of the gcc 3.4 failures (in fact, all of that I've seen)
have to do with fooling -traditional into turning macro constants into
Haskell strings, which can more readily
Malcolm Wallace wrote:
Andy Moran [EMAIL PROTECTED] writes:
I notice that cpphs understands CPP stringification (if invoked with
--hashes). Most of the gcc 3.4 failures (in fact, all of that I've seen)
have to do with fooling -traditional into turning macro constants into
Haskell strings, which
12 matches
Mail list logo
