[m-users.] Mercury packages on Debian 8 (jessie)

Julien Fischer jfischer at opturion.com
Thu Jan 17 12:40:41 AEDT 2019

On Wed, 16 Jan 2019, Paul Bone wrote:

> On Thu, Jan 17, 2019 at 01:05:42AM +1300, Richard O'Keefe wrote:
>> Does this mean GCC 4,8 exactly, or 4.8 or later?
> 4.8 exactly.  This version of Mercury wasn't compatible (for faster grades)
> with newer GCCs.  It'll work on older GCCs but since the compiler name
> "gcc-4.8" gets hard-coded into the Mercury configuration the binary packages
> must depend on exactly the compiler name that was used to build them.
>> I'm using Ubuntu 18, and the GCC version is 7.3.0-3ubuntu2.1.
>> Clang is 6.0-41~exp5~ubuntu1 and
>> pgcc is pgcc 18.10-1 64-bit target on x86-64 Linux -tp gh
>> Should I expect any difficulty building Mercury with these?
> Your GCC should be compatible, it's the same as mine.  I'm not sure about
> clang, I just havn't tested it.

It's tested with clang on Linux as part the ROTD testing.  When building
Mercury from source versions of clang from about 3.0 onwards should be
fine.  Since clang doesn't support most of the GCC extensions that
Mercury is interested in the set of (C) grades supported is restricted
to the hlc* and none* ones.

However, I would imagine that for the Debian packages the C compiler
has been configured to be GCC.


More information about the users mailing list