Relocation error when running `mmc`

Bug #1964 reported by Gintautas Miliauskas
8
Affects Status Importance Assigned to Milestone
mercury (Debian)
Fix Released
Unknown
mercury (Ubuntu)
Invalid
Medium
MOTU

Bug Description

I have just recently upgraded to breezy. When I try to start `mmc`, the Mercury compiler, I get this error:

[~]$ mmc
/usr/lib/mercury/bin/i686-pc-linux-gnu/mercury_compile: relocation error: /usr/lib/mercury/bin/i686-pc-linux-gnu/mercury_compile: symbol __libc_stack_end, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference
[exited with 127]

I rebuilt the package locally and the error went away.

Changed in mercury:
assignee: nobody → motu
Revision history for this message
Daniel Robitaille (robitaille) wrote :

I can confirm this bug is still occuring in Dapper (Beta 2).

Changed in mercury:
status: Unconfirmed → Confirmed
Revision history for this message
Allison Karlitskaya (desrt) wrote :

Uhm. What's up, guys?

Revision history for this message
Daniel Robitaille (robitaille) wrote :

Still occurring in Edgy:

$ mmc
/usr/lib/mercury/bin/i686-pc-linux-gnu/mercury_compile: relocation error: /usr/lib/mercury/bin/i686-pc-linux-gnu/mercury_compile: symbol __libc_stack_end, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference

Changed in mercury:
status: Unknown → Unconfirmed
Revision history for this message
Arthur Peters (amp) wrote :

This problem is still present in feisty.

Also there is a new version of mercury. Is this package actively maintained?

Revision history for this message
Gintautas Miliauskas (gintas) wrote :

The problem seems to be gone now. Mercury starts fine here on Hardy. This bug can probably be closed (although a version update too would not hurt).

Changed in mercury:
status: New → Fix Released
Revision history for this message
Greg A (etulfetulf) wrote :

The mercury package has been removed from Ubuntu Intrepid (and Debian) so I am marking this bug invalid.

Changed in mercury:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.