From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12986] New: Mtools: Error converting to codepage 850
Date: Mon, 08 Jun 2020 16:18:43 +0000 [thread overview]
Message-ID: <bug-12986-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12986
Bug ID: 12986
Summary: Mtools: Error converting to codepage 850
Product: buildroot
Version: 2020.05
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: melanie at trash-mail.com
CC: buildroot at uclibc.org
Target Milestone: ---
The 'BR2_PACKAGE_MTOOLS' program builds fine but on the target system some of
the mtools-commands (i.e. mdir) fails to execute with the following message:
Error converting to codepage 850 Invalid argument
As described in the mtools-manual [1], codepage 850 is used by default.
I've solved the problem by adding 'BR2_TOOLCHAIN_GLIBC_GCONV_LIBS_COPY=y' to my
buildroot-configuration.
From my point of view, the config option 'BR2_PACKAGE_MTOOLS' should
automatically select 'BR2_TOOLCHAIN_GLIBC_GCONV_LIBS_COPY' to make sure that
the required gconv libraries are available on the target system.
[1]
https://www.gnu.org/software/mtools/manual/mtools.html#miscellaneous-variables
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-08 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 16:18 bugzilla at busybox.net [this message]
2020-06-11 6:31 ` [Buildroot] [Bug 12986] Mtools: Error converting to codepage 850 bugzilla at busybox.net
2020-06-21 7:18 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12986-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.