[mercury-users] Errors while building rpm for Fedora

[Paul Bone]

On Tue, Aug 19, 2008 at 03:35:03PM +0400, Peter Lemenkov wrote:
> Hello All!
> I'm interested in Mercury after reading some online articles
> describing it. In order to do this in a comfortable way (and,
> probably, help those who also interested in) I decided to to make rpm
> for Fedora/RHEL compatible distributives.  Unfortunately, I
> encountered strange build errors while building using Fedora Build
> Infrastructure:
> 

Hi Peter,

We've aware of an incompatibility between Mercury and GCC 4.2 on some
systems, your observations could be symptoms of this issue.  I've
written a FAQ entry that describes two work-arounds for this problem,
however this may not appear on the website for a couple of days, due to
our peer-review process.  In the meantime here is my draft, note that it
doesn't yet have approval from the rest of the team.

Hope this helps.

-----------------

This is an extract from the Mercury Frequently Asked Questions List, It
contains a list of frequently asked questions about Mercury, with
answers.

Copyright (C) 1995-1997,1999,2001-2008 The University of Melbourne.

Permission is granted to make and distribute verbatim copies of
this FAQ list provided the copyright notice and this permission notice
are preserved on all copies.

Permission is granted to copy and distribute modified versions of this
FAQ list under the conditions for verbatim copying, provided also that
the entire resulting derived work is distributed under the terms of a
permission notice identical to this one.

Permission is granted to copy and distribute translations of this FAQ list
into another language, under the above conditions for modified versions.

@item
@emph{The compiler crashes during the ``make install'' phase}
@sp 1

An incompatibility between Mercury's low-level C backend and some GCC
optimizations in GCC 4.2 seems to be causing problems.  Try using a different
version of GCC, otherwise the following instructions may help.

After unpacking the tarball but before running @samp{configure}, create a file in
the root directory of the unpacked source named @samp{Mmake.params} containing
the line @samp{-EXTRA_CFLAGS=-O0}, and run @samp{configure} as
@samp{./configure --with-llds-base-grade=none --with-default-grade=hlc.gc}.
This disables GCC's optimizations and some of Mercury's optimizations for the
low-level C backend.  Programs build using this Mercury installation will use
the high-level C backend by default.

See bugs 66 and 77.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/users/attachments/20080820/7f696351/attachment.sig>