Troubleshooting Mono2Micro

You might encounter an issue when you install or use IBM® Mono2Micro™. To resolve the issue, complete the provided steps.

Mono2Micro command-line tool on Windows shows unsupported characters in non-English languages

The Mono2Micro command-line tool might show unsupported characters for non-English languages on Windows™ computers. The problem might affect any application.

To reproduce the problem, extract the Mono2Micro-CLI.zip file on a Windows computer with a language different than English and then run a mono2micro command. You extract the .zip file when you complete the procedure in Downloading and installing IBM Mono2Micro. For example, after you extract the .zip file on a computer that is set to Portuguese, a command such as mono2micro --help displays the ? question mark character instead of the ã character.

To fix the problem, change the Windows region settings.

  1. Go to Settings for the Windows computer.
  2. Click Time and language > Language and region > Administrative language settings > Change system locale.
  3. In the Region Settings dialog, make sure that the Beta: Use Unicode UTF-8 for worldwide language support checkbox is selected. Click OK to save any changes.
  4. Click Apply.

The no such file or directory error is shown when a mono2micro command is run

When you run Mono2Micro commands such as mono2micro recommend, mono2micro workbench, mono2micro refine, mono2micro transform, or mono2micro analyze -s, you might get the following error:

Error: statfs ... no such file or directory

To get status about the error, add the --verbose option to the command. If the command uses a path as an argument, ensure that the specified path exists and that the current user has access to it.

If you are using Podman and the command uses a path as an argument, the problem might be that Podman cannot mount the equivalent path inside the container that runs in the virtual machine. Podman on Mac or Windows uses a virtual machine. In this case, the problem is with Podman and not Mono2Micro. To fix the problem, re-create the Podman virtual machine and specify a default volume:

  1. Stop the current Podman virtual machine.
    podman machine stop
  2. Delete the Podman virtual machine.
    podman machine rm -f
  3. Create a Podman virtual machine with a default volume.
    podman machine init --volume path
    In this command, path is a root folder for Mono2Micro files. For example, if Mono2Micro files are in /Volumes/m2m-files, you run a command that specifies /Volumes for the path value. 
    podman machine init --volume /Volumes
  4. Start your new Podman virtual machine.
    podman machine start
  5. During the Podman virtual machine (VM) startup, look for a message that indicates Podman mounted the path.
    ...
Waiting for VM ...
Mounting volume... /Volumes:/Volumes
...
Machine "podman-machine-default" started successfully
  6. If you don't see a message that indicates Podman mounted the path successfully, try running the podman machine stop and podman machine start commands again.