[m-dev.] Re: mercury: should this package be removed?

Julien Fischer juliensf at csse.unimelb.edu.au
Mon Feb 25 14:53:47 AEDT 2008

On Wed, 20 Feb 2008, Paul Bone wrote:

> On 20/02/2008, at 11:02 AM, Roy Ward wrote:
>> Barry deFreese wrote:
>>> Paul,
>>> I've removed the bug addresses for now so there isn't too much garbage on 
>>> Debian's BTS.
>>> I'm testing a build of mercury 0.13.1 right now with gcc-4.1.  So far it's 
>>> building.  I can probably help you get a minimal package going just to get 
>>> started.
>> I did quite a bit of testing on this on amd64 and i386, and it would build 
>> for a while, then:
>> It was possible to build with 4.1 with a reduced set of grades, or to use a 
>> different version of gcc after Mercury was built, but I don't think that's 
>> stable enough for a Debian package.
> I recommend using the reduced set of grades.  use --enable-libgrades as an 
> argument to configure and specify only some grades.  The grade that it looks 
> like gcc wasn't able to compile was the deep profiling grade.  Which isn't 
> necessary to have a working mercury installation, it just limits some of the 
> profiling that can be done.

IIRC, the deep profiler on the 0.13 branch doesn't work properly anyway,
it's probably best to ignore it in the 0.13.X release series.

mercury-developers mailing list
Post messages to:       mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions:          mercury-developers-request at csse.unimelb.edu.au

More information about the developers mailing list