#40 4.0.2 stable binary identifying as 4.9.6?

[Rob Denton]

I'm downloading mira to work with MITObim. When downloading the stable release required (4.0.2), after installation mirabait -v identifies 4.9.6. Is there a version mix up in the binaries here on sourceforge?

[Bastien Chevreux]

Shouldn't be, that'd be a first. Can you please check wether you are calling the right binary? Either via "which mirabait", then check path, or call the downloaded binary directly with full path.

[Rob Denton]

I uninstalled a previous version that was put on via conda. I downloaded
the linux binary for 4.0.2.

"which mirabait" points to the correct location.

"mirabait -v" produces the following error:

"mirabait: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt <
(sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))'
failed.
Aborted (core dumped)"

This is on ubuntu. Thanks!

On Tue, Apr 2, 2019 at 3:50 PM Bastien Chevreux bach@users.sourceforge.net
wrote:

Shouldn't be, that'd be a first. Can you please check wether you are
calling the right binary? Either via "which mirabait", then check path, or
call the downloaded binary directly with full path.

---

• [tickets:#40] https://sourceforge.net/p/mira-assembler/tickets/40/
  4.0.2 stable binary identifying as 4.9.6?*

Status: open
Version: 4.0.1
Created: Tue Apr 02, 2019 08:46 PM UTC by Rob Denton
Last Updated: Tue Apr 02, 2019 08:46 PM UTC
Owner: Bastien Chevreux

I'm downloading mira to work with MITObim. When downloading the stable
release required (4.0.2), after installation mirabait -v identifies 4.9.6.
Is there a version mix up in the binaries here on sourceforge?

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mira-assembler/tickets/40/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Bastien Chevreux]

A bug of the C++ libraries which I learned to circumvent in later versions of MIRA. Should you insist on using 4.0.2, the workaround is:
export LC_ALL=C
in the shell, then it will work.

Though I would suggest you use mirabait from either 4.9.6 or from 5rc1 (on GitHub). I think I slightly changed the commandline interface for mirabait inbetween 4.0.x and 4.9.x, so MITObim might need slight adaptation. But the core functionality of mirabait remained the same.

[Rob Denton]

That fixed the problem. Thanks!!

On Tue, Apr 2, 2019, 5:02 PM Bastien Chevreux bach@users.sourceforge.net
wrote:

A bug of the C++ libraries which I learned to circumvent in later versions
of MIRA. Should you insist on using 4.0.2, the workaround is:
export LC_ALL=C
in the shell, then it will work.

Though I would suggest you use mirabait from either 4.9.6 or from 5rc1 (on
GitHub). I think I slightly changed the commandline interface for mirabait
inbetween 4.0.x and 4.9.x, so MITObim might need slight adaptation. But the
core functionality of mirabait remained the same.

---

• [tickets:#40] https://sourceforge.net/p/mira-assembler/tickets/40/
  4.0.2 stable binary identifying as 4.9.6?*

Status: open
Version: 4.0.1
Created: Tue Apr 02, 2019 08:46 PM UTC by Rob Denton
Last Updated: Tue Apr 02, 2019 08:50 PM UTC
Owner: Bastien Chevreux

I'm downloading mira to work with MITObim. When downloading the stable
release required (4.0.2), after installation mirabait -v identifies 4.9.6.
Is there a version mix up in the binaries here on sourceforge?

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mira-assembler/tickets/40/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/