similar to: [patch] R-1.9.0: compile error without nl_langinfo(CODESET) (PR#6789)

Displaying 20 results from an estimated 1000 matches similar to: "[patch] R-1.9.0: compile error without nl_langinfo(CODESET) (PR#6789)"

2001 Sep 30
3
UTF-8 stuff
Here's a propsed heavy-duty solution for your UTF-8 problems. I'm including a patch in this message, but I'll put the new files on my web site at http://rano.org/tmp/xiph_files.tar.gz I've tested this by running vorbiscomment with and without -DHAVE_ICONV=1 in vorbis-tools/share/Makefile. It seems to work. Changed files: acinclude.m4: Add a test for nl_langinfo(CODESET). This
2018 Aug 20
2
Call for testing: OpenSSH 7.8
Hi, Michael Felt wrote on Mon, Aug 20, 2018 at 11:28:26AM +0200: > On 20/08/2018 10:33, Michael Felt wrote: >> On 17/08/2018 17:15, Ingo Schwarze wrote: >>> Darren Tucker wrote on Fri, Aug 17, 2018 at 07:16:03AM -0700: >>>> On 13 August 2018 at 15:06, Val Baranov <val.baranov at duke.edu> wrote: >>>>> test_utf8: ........................
2005 Sep 27
2
vorbiscomment, ogg123 charset bug - ticket #685
Hi I've a bug in vorbis-tools's libutf8 - some share/*.[ch] files don't include config.h; as a result, utf8.c:convert_set_charset doesn't try charset = nl_langinfo(CODESET) which would correctly return UTF-8, because HAVE_LANGINFO_CODESET isn't defined (it's defined in config.h, but config.h is not included). So, the bugfix is simple - just include config.h everywhere
2018 Feb 28
0
[PATCH v3 1/2] common: extract UTF-8 conversion function
libxml2-utils.c local_string_to_utf8() function could easily be reused in other places. This commit extracts it with a new parameter to allow giving the encoding of the input string and publishes it in guestfs-utils.h as guestfs_int_string_to_utf8() --- common/utils/guestfs-utils.h | 11 +++++++ common/utils/libxml2-utils.c | 69 +------------------------------------------- common/utils/utils.c
2017 Mar 31
2
testsuite error on Solaris 2.6 [Re: Announce: OpenSSH 7.5 released]
On 27/03/17 17:06, Tom G. Christensen wrote: > On 20/03/17 14:31, Damien Miller wrote: >> OpenSSH 7.5 has just been released. It will be available from the >> mirrors listed at http://www.openssh.com/ shortly. >> > > I'm seeing an error in the testsuite on Solaris 2.6: > test_utf8: ........................ > regress/unittests/utf8/tests.c:48 test #25
2018 Aug 20
6
Call for testing: OpenSSH 7.8
Hi, Michael Felt wrote on Mon, Aug 20, 2018 at 05:00:17PM +0200: > ./nl_langinfo > setlocale -> "C" > nl_langinfo -> "ISO8859-1" Thanks, that is helpful. So i think i was wrong and Damien was right. This means that OpenSSH returns truncated messages when non-ASCII bytes occur in them, even when the user requests LC_CTYPE=POSIX. That's not good. While
2018 Feb 15
0
[PATCH] Introduce a wrapper around xmlParseURI.
We only use xmlParseURI to parse our own "homebrew" URIs, for example the ones used by guestfish --add or virt-v2v. Unfortunately xmlParseURI cannot handle URIs with spaces or other non-RFC-compliant characters so simple commands like these fail: $ guestfish -a 'ssh://example.com/virtual machine.img' guestfish: --add: could not parse URI 'ssh://example.com/virtual
2023 Jan 31
1
Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '<ff>' if an environment variable contains \xFF
Can we use the "bytes" encoding for such environment variables invalid in the current locale? The following patch preserves CE_NATIVE for strings valid in the current UTF-8 or multibyte locale (or non-multibyte strings) but sets CE_BYTES for those that are invalid: Index: src/main/sysutils.c =================================================================== --- src/main/sysutils.c
2018 Nov 02
0
[PATCH REPOST] Introduce a wrapper around xmlParseURI.
We only use xmlParseURI to parse our own "homebrew" URIs, for example the ones used by guestfish --add or virt-v2v. Unfortunately xmlParseURI cannot handle URIs with spaces or other non-RFC-compliant characters so simple commands like these fail: $ guestfish -a 'ssh://example.com/virtual machine.img' guestfish: --add: could not parse URI 'ssh://example.com/virtual
2023 Jan 31
1
Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '<ff>' if an environment variable contains \xFF
On 1/31/23 09:48, Ivan Krylov wrote: > Can we use the "bytes" encoding for such environment variables invalid > in the current locale? The following patch preserves CE_NATIVE for > strings valid in the current UTF-8 or multibyte locale (or > non-multibyte strings) but sets CE_BYTES for those that are invalid: > > Index: src/main/sysutils.c >
2010 Jul 21
0
Samba install on AIX
ibm68p0:/home/b08chm/m4/m4-1.4.14] # oslevel -s 6100-04-02-1007 [ibm68p0:/home/b08chm/m4/m4-1.4.14] # $ make make all-recursive Making all in . Target "all-am" is up to date. Making all in examples Target "all" is up to date. Making all in lib rm -f alloca.h-t alloca.h && { echo '/* DO NOT EDIT! GENERATED AUTOMATICALLY! */'; cat
2005 Nov 11
1
undefined symbol in grDevices.so
Hello I'm trying to use rpy with latest R (2.2.0), but unfortunately it seems there is some kind of undefined symbol in grDevices.so (utf8locale) Within python, this message appears: >>> import rpy Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library '/usr/local/lib/R/library/grDevices/libs/grDevices.so':
2008 May 10
1
Failed to create rounding.h!
On an i686 with glibc 2.5 installed I'm not able to compile rsync 3.0.2 and later. rsync 3.0.0 was no problem, this compiled. Also on an x86_64 with glibc 2.7 installed rsync compiled. Here is a script of the failing comilation: Script started on Sat May 10 07:33:39 2008 teddy@mail /usr/src/rsync-HEAD-20080508-0612GMT $ mkdir build teddy@mail /usr/src/rsync-HEAD-20080508-0612GMT $ cd build
2007 Apr 04
4
3ware cards and new firmware in 9.4.1 codeset
I just saw the following in the release notes for the new firmware for the later 3ware cards; Improved CIFS performance The firmware has been tuned to greatly increase performance with CIFS (Common Internet File System) protocol. However, this has resulted in performance with the Linux ext3 file system that is slower than earlier releases. We recommend that you use other Linux file systems, such
2023 Jan 31
2
Sys.getenv(): Error in substring(x, m + 1L) : invalid multibyte string at '<ff>' if an environment variable contains \xFF
>>>>> Tomas Kalibera >>>>> on Tue, 31 Jan 2023 10:53:21 +0100 writes: > On 1/31/23 09:48, Ivan Krylov wrote: >> Can we use the "bytes" encoding for such environment variables invalid >> in the current locale? The following patch preserves CE_NATIVE for >> strings valid in the current UTF-8 or multibyte locale (or
2009 Nov 13
2
xend:default won''t start due to /usr/bin/kstat not locating autosplit.ix
Short:     Which package do I need to install to get "auto/I18N/Langinfo/autosplit.ix"? Long: The problem I have was discussed almost a year ago (see this thread), but the resolution was not complete... I''m using Mark Johnson''s slim.py script (package list below), against repo=http://pkg.opensolaris.org/dev, followed by `pkg install xvm-gui` and `svcadm enable
2018 Aug 20
2
Call for testing: OpenSSH 7.8
On 17/08/2018 17:15, Ingo Schwarze wrote: > Hi Darren, > > Darren Tucker wrote on Fri, Aug 17, 2018 at 07:16:03AM -0700: >> On 13 August 2018 at 15:06, Val Baranov <val.baranov at duke.edu> wrote: >>> test_utf8: ........................ >>> regress/unittests/utf8/tests.c:48 test #25 "c_esc" >>> ASSERT_INT_EQ(len, wantlen) failed:
2005 Jul 19
0
build of REventLoop package crashes with 2.1 due tosyntax error in Defn.h (PR#8017)
Full_Name: Richard Boyce Version: 2.1.-1 OS: Debian testing/unstable Submission from: (NULL) (128.95.123.29) While building a custom package using a modified version of Duncan's REventLoop with R version 2.1 (Debian package r-base, r-base-dev) and R source from apt-get source 2.1.1 I get the following error: $ R CMD build vjREventLoop * checking for file
2018 Feb 28
2
[PATCH v3 0/2] inspect: basic UTF-8 encoding for rpm
Diff to v2: * inlined local_string_to_utf8 Cédric Bosdonnat (2): common: extract UTF-8 conversion function inspector: rpm summary and description may not be utf-8 common/utils/guestfs-utils.h | 11 +++++ common/utils/libxml2-utils.c | 69 +-------------------------- common/utils/utils.c | 64 +++++++++++++++++++++++++
2006 Nov 05
1
Definity Asterisk Caller ID Issue
You should run the 4ESS protocol ("a" on the Definity command "change DS1 board#) as the Definity may not send Display Name for the NI-2 protocol (settings "b" or "d") Remember to make the Asterisk zapata settings consistent with the Definity. On the Definity trunk group form Page 1, change "Codeset to send Display" to "0 (zero)", also make