[m-dev.] Test failures during porting to ARM

Sergey Khorev iamphet at nm.ru
Wed Nov 23 02:23:15 AEDT 2005

Hello, Julien

JF> No it's not a real failure.  The expected outputs in that directory
JF> assume that the environment variable MERCURY_SUPPRESS_STACK_TRACE has been set
JF> to yes (this will cause the compiler to omit the message about the
JF> unavailable stack trace).  When the tests are run from the bootcheck
JF> script this variable should be set.

Ah, I see. I ran mmake in mercury-test-0.12.0 instead of using bootcheck procedure.

Thanks a lot,
Sergey Khorev
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au

More information about the developers mailing list