[mercury-users] Link error with exceptions on x86-64

Michael Day mikeday at yeslogic.com
Wed Oct 20 21:49:34 AEDT 2010


Hi,

When I compile a Mercury program that uses try_io I get a link error:

undefined reference to `<predicate 'exception.wrap_success_or_failure'/2 
mode 0>'

At the C level this translates to:

undefined reference to 
`_entry_mercury__exception__wrap_success_or_failure_2_0'

But when I check asm_fast.gc/libmer_std.a I find these:

0000000000001ab0 t _entry_mercury__exception__wrap_success_or_failure_2_0
0000000000001b00 t _entry_mercury__exception__wrap_success_or_failure_2_1
0000000000001b60 t _entry_mercury__exception__wrap_success_or_failure_2_2
0000000000001bb0 t _entry_mercury__exception__wrap_success_or_failure_2_3

I've checked the Mercury command line and it is definitely linking with 
the standard library. I don't get these errors on 32-bit Linux, only 
x86-64, and on MacOS X in the past.

Does anyone have any idea about this error? The only workaround I have 
is to not catch exceptions, which is not really acceptable.

Best regards,

Michael

-- 
Print XML with Prince!
http://www.princexml.com
--------------------------------------------------------------------------
mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au
--------------------------------------------------------------------------



More information about the users mailing list