mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alan Hourihane <alanh@fairlite.co.uk>
To: musl@lists.openwall.com
Subject: Re: CP850 & IBM850 codepages
Date: Tue, 25 Feb 2014 22:31:46 +0000	[thread overview]
Message-ID: <530D19D2.4020800@fairlite.co.uk> (raw)
In-Reply-To: <20140225222557.GH184@brightrain.aerifal.cx>

On 02/25/14 22:25, Rich Felker wrote:
> On Tue, Feb 25, 2014 at 09:44:05PM +0000, Alan Hourihane wrote:
>> Hi all,
>>
>> First post to the list, so thank you for musl.
>>
>> I was just compiling samba against musl and got this.....
>>
>> checking for iconv in /usr/lib... yes
>> checking can we convert from CP850 to UCS2-LE?... no
>> checking can we convert from IBM850 to UCS2-LE?... no
>> checking can we convert from ASCII to UCS2-LE?... ASCII
>> checking can we convert from UTF-8 to UCS2-LE?... UTF-8
>> checking for iconv in /usr/local/lib... yes
>> checking can we convert from CP850 to UCS2-LE?... no
>> checking can we convert from IBM850 to UCS2-LE?... no
>> checking can we convert from ASCII to UCS2-LE?... ASCII
>> checking can we convert from UTF-8 to UCS2-LE?... UTF-8
>> configure: WARNING: Sufficient support for iconv function was not found.
>>      Install libiconv from http://freshmeat.net/projects/libiconv/
>> for better charset compatibility!
>>
>> Looking at the code we're missing the "cp850" and "ibm850" codepages.
>>
>> I'm not sure how they are derived in the musl source though.
>>
>> Any help appreciated.
> In the immediate, I think your best course of action would be to see
> if you can just override these tests. It seems unlikely to me that you
> would really need conversion from these legacy codepages for normal
> usage of samba. (BTW I'm surprised nobody else has reported this
> before... does anybody else know why it hasn't come up..?)

That's easy enough.

> Adding cp850 and other DOS codepages should not be hard and should not
> take up much additional size in iconv, but it's also nontrivial to do
> without my tools to generate the tables, which are not published.
> Publishing them is something I should really get around to doing,
> since their absence affects the ability of others to modify the code
> in meaningful ways; I need to apologize for not doing so already.
>

O.k. that makes sense as I couldn't understand the format. :-)

Thanks,

Alan.


  reply	other threads:[~2014-02-25 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 21:44 Alan Hourihane
2014-02-25 22:25 ` Rich Felker
2014-02-25 22:31   ` Alan Hourihane [this message]
2014-02-25 22:39     ` Rich Felker
2014-02-26 11:58       ` Alan Hourihane

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=530D19D2.4020800@fairlite.co.uk \
    --to=alanh@fairlite.co.uk \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).