Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc -I/usr/src/packages/BUILD/bash-4.2
-L/usr/src/packages/BUILD/bash-4.2/../readline-6.2
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYP
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/\
loca
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
Hi Andreas and Chet,
@Andreas: this patch seams promising. I am unable to test it now, but I will
at the beginning of next week.
@Chet: according to the specification, the retrun value of lseek is -1 if
error, or new offset from the beginning of the file if success. In my case,
the problem i
On 3/6/12 7:22 AM, wer...@suse.de wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i586
> OS: linux-gnu
> Compiler: gcc -I/usr/src/packages/BUILD/bash-4.2
> -L/usr/src/packages/BUILD/bash-4.2/../readline-6.2
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOST
On 03/06/2012 05:26 PM, Chet Ramey wrote:
> On 3/6/12 7:22 AM, wer...@suse.de wrote:
>> Configuration Information [Automatically generated, do not change]:
>> Machine: i586
>> OS: linux-gnu
>> Compiler: gcc -I/usr/src/packages/BUILD/bash-4.2
>> -L/usr/src/packages/BUILD/bash-4.2/../readline-6.2
>>
On 3/6/12 7:37 PM, Eric Blake wrote:
>> Thanks for the report. Unfortunately, the way different versions of Unix
>> name the `struct timespec' members of struct stat varies, and so the patch
>> is only valid on Linux, Solaris, and Cygwin. I will come up with some
>> autoconf-based way to do it.
You really should stop using this function. It is just plain wrong, and
is not predictable.
It may enocde BIG5 and SJIS but is is more by accident that intent.
If you want to do something like this then do it properly.
basically all of the multibyte system have to have a detection method
for mu