If libiconv in base for FreeBSD = 10.0 was supposed to replace the version in
ports but had a deficiency, is there any plan to port the ports version to base
for FreeBSD 10-stable or 11-head?
Tom
___
freebsd-ports@freebsd.org mailing list
On 22.03.2014 9:06, Kevin Oberman wrote:
On Fri, Mar 21, 2014 at 9:27 AM, Andrey Chernov a...@freebsd.org
mailto:a...@freebsd.org wrote:
On 21.03.2014 20 tel:21.03.2014%2020:15, Kevin Oberman wrote:
The FreeBSD iconv support is fully posix compliant
Not so fully. Translation
For me, I built libc WITHOUT iconv by setting
WITHOUT_ICONV=yes
in /etc/src.conf
than... make buildworld;make installworld.
and than rebuild all packages that depends on it (about 200)
now all the packages, ports are all working again
I will wait for FreeBSD11, that perhaps have a full
Am Thu, 20 Mar 2014 21:07:05 -0400
schrieb Adam McDougall mcdou...@egr.msu.edu:
In short, if you installed 10.0-RELEASE, don't pay any attention to
libiconv unless you are having specific problems. Do not try to fight
ports from using libiconv from ports, they are using that version for
a
On Thu, Mar 20, 2014 at 8:00 AM, Johan Hendriks joh.hendr...@gmail.comwrote:
Dr. Peter Voigt schreef:
I am running a fresh installation of 10.0-RELEASE since its
publication at the end of January this year. I have installed many
ports since then and all dependencies are OK.
Yesterday I
On 21.03.2014 20:15, Kevin Oberman wrote:
The FreeBSD iconv support is fully posix compliant
Not so fully. Translation to ASCII is completely broken. Toggling POSIX
translate flag is impossible (always on).
--
http://ache.vniz.net/
___
On Fri, Mar 21, 2014 at 9:27 AM, Andrey Chernov a...@freebsd.org wrote:
On 21.03.2014 20:15, Kevin Oberman wrote:
The FreeBSD iconv support is fully posix compliant
Not so fully. Translation to ASCII is completely broken. Toggling POSIX
translate flag is impossible (always on).
My error.
I am running a fresh installation of 10.0-RELEASE since its
publication at the end of January this year. I have installed many
ports since then and all dependencies are OK.
Yesterday I have stumbled across several posts in the forum making me
aware of a major change in handling port
Dr. Peter Voigt schreef:
I am running a fresh installation of 10.0-RELEASE since its
publication at the end of January this year. I have installed many
ports since then and all dependencies are OK.
Yesterday I have stumbled across several posts in the forum making me
aware of a major change in
Johan Hendriks joh.hendr...@gmail.com writes:
As far as I know, there is some libiconv functionality missing in the
base libiconv implementation. That is the reason some ports installed
converters/libiconv from ports.
From reading the mailing lists and skimming the PRs, it appears
Am Thu, 20 Mar 2014 12:20:43 -0400
schrieb Robert Huff roberth...@rcn.com:
Johan Hendriks joh.hendr...@gmail.com writes:
As far as I know, there is some libiconv functionality missing in
the base libiconv implementation. That is the reason some ports
installed converters/libiconv from
On 03/20/2014 14:54, Dr. Peter Voigt wrote:
Thanks on feedback to all.
Meanwhile I've read a lot about iconv and to be honest, things are
becoming even less clear. I am having not enough experience with FreeBSD
to completely judge the situation. But obviously replacement of the
ports
12 matches
Mail list logo
