env var or mount option for multibyte<->unicode filenames conversion

Hi. Currently, the code page for internal convertion of file names to unicode depends on programs's locale. I want to keep UTF-8 as current locale, but use CP1251 for this conversion. Is it possible? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.c

Re: i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11?

On 8/18/2011 13:44, Frédéric Bron wrote: > Using cygwin 1.7.9(0.237/5/3) 2011-03-29 10:10. > > The following program: > > #include > int main() { > > std::cout<<__MINGW32_MAJOR_VERSION<<'.'<<__MINGW32_MINOR_VERSION<<'\n'; > return 0; > } > > outputs: > - 3.18 when built with i6

Re: env var or mount option for multibyte<->unicode filenames conversion

On Aug 18 14:19, Ilya Basin wrote: > Hi. Currently, the code page for internal convertion of file names to > unicode depends on programs's locale. > I want to keep UTF-8 as current locale, but use CP1251 for this > conversion. Is it possible? Maybe if you describe your problem slightly more detail

Gawk error under Cygwin

Hi all, I encounter a strange behavior of gawk under cygwin: Using awk -f somescript.awk works fine except NaN handling which is switched on by --posix but awk --posix -f somescript.awk produces an error awk somescript.awk:29: Fatal: Funktion 'systime' ist nicht definiert. (systime not d

Re: Gawk error under Cygwin

On Aug 18 15:00, DEWI - N. Zacharias wrote: > > Hi all, > > I encounter a strange behavior of gawk under cygwin: > > Using > awk -f somescript.awk > > works fine except NaN handling which is switched on by --posix but > > awk --posix -f somescript.awk > > produces an error > > awk somesc

AW: [bulk] - Re: Gawk error under Cygwin

Hi Corrina, > Von: Corinna Vinschen > Gesendet: Donnerstag, 18. August 2011 15:21 > Betreff: [bulk] - Re: Gawk error under Cygwin > > On Aug 18 15:00, DEWI - N. Zacharias wrote: > > > > Hi all, > > > > I encounter a strange behavior of gawk under cygwin: > > > > Using > > awk -f somescript.awk

Re: i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11?

> Just bump it up and see if there are any issues, the mingw-w64 toolchain > uses its own header set and the numbers don't always reflect mingw.org > releases, since the macros in there are mainly for compatibility. > > You want to check instead for __MINGW64_VERSION_MAJOR on mingw-w64. neither __

Re: i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11?

On 8/18/2011 21:56, Frédéric Bron wrote: >> Just bump it up and see if there are any issues, the mingw-w64 toolchain >> uses its own header set and the numbers don't always reflect mingw.org >> releases, since the macros in there are mainly for compatibility. >> >> You want to check instead for __M

Re: v*printf functions not available with g++ -std=c++0x

On Aug 17 11:04, Ryan Johnson wrote: > Hi all, > > I'm using the experimental gcc-4.5 package and hit a strange error: > c++0x mode suppresses the definition of the v*printf() family of > functions in stdio.h in c++0x mode. The offending code seems to be: > > #if !defined(__STRICT_ANSI__) || (__S

i686-w64-mingw32-gcc & ntifs.h

Hi, I cannot #include because /usr/i686-w64-mingw32/sys-root/mingw/include/ddk/ntifs.h contains #include and actually lives in ddk, i.e., it should be #include after I aplly these two patches: --- c:/gnu/cygwin/usr/i686-w64-mingw32/sys-root/mingw/include/ddk/ntddk.h.old 2011-08-10 09:06:18.0

Re: i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11?

On Thu, 2011-08-18 at 07:44 +0200, Frédéric Bron wrote: > Using cygwin 1.7.9(0.237/5/3) 2011-03-29 10:10. > > The following program: > > #include > int main() { > > std::cout<<__MINGW32_MAJOR_VERSION<<'.'<<__MINGW32_MINOR_VERSION<<'\n'; > return 0; > } > > outputs: > - 3.18 whe

Re: i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11?

On Thu, 2011-08-18 at 07:44 +0200, Frédéric Bron wrote: > Using cygwin 1.7.9(0.237/5/3) 2011-03-29 10:10. > > The following program: > > #include > int main() { > > std::cout<<__MINGW32_MAJOR_VERSION<<'.'<<__MINGW32_MINOR_VERSION<<'\n'; > return 0; > } > > outputs: > - 3.18 whe

Re: [ANNOUNCEMENT] Updated: binutils-2.21.53-1

On Fri, 2011-08-05 at 13:35 +0200, Denis Excoffier wrote: > Hello, > > On Sun, Jul 31, 2011 at 02:22:51PM -0400, Christopher Faylor wrote: > >> I've made a new version of binutils available for installation. This is > >> a refresh against the current CVS. > > Compared to the previous one (binuti

Re: [ANNOUNCEMENT] Updated: binutils-2.21.53-1

On 8/18/2011 1:37 PM, Yaakov (Cygwin/X) wrote: > Could you please respin binutils with the missing headers and libraries? Since libbfd & friends are no longer default-installed by the src/ build machinery when building binutils or gcc, I wonder if it would be a good idea to "spin off" libbfd as a

Re: i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11?

> If you are using a mingw* compiler, then you're not "using" Boost on > Cygwin. I am. Up to now, I have a dual cygwin installation 1.5/1.7 because I was unable to use boost nor wxwidgets with 1.7. I recently decided to make another effort to build boost with 1.7 because I feel that it will be dif

Re: [ANNOUNCEMENT] Updated: binutils-2.21.53-1

On Thu, Aug 18, 2011 at 12:37:56PM -0500, Yaakov (Cygwin/X) wrote: >On Fri, 2011-08-05 at 13:35 +0200, Denis Excoffier wrote: >> Hello, >> >> On Sun, Jul 31, 2011 at 02:22:51PM -0400, Christopher Faylor wrote: >> >> I've made a new version of binutils available for installation. This is >> >> a r

Re: i686-w64-mingw32-gcc & ntifs.h

On 8/18/2011 23:44, Sam Steingold wrote: > Hi, > I cannot > #include > because /usr/i686-w64-mingw32/sys-root/mingw/include/ddk/ntifs.h contains > #include > and actually lives in ddk, i.e., it should be > #include > after I aplly these two patches: > --- c:/gnu/cygwin/usr/i686-w64-mingw32/sys-

Re: i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11?

On 8/19/2011 03:10, Frédéric Bron wrote: >> If you are using a mingw* compiler, then you're not "using" Boost on >> Cygwin. > > I am. Up to now, I have a dual cygwin installation 1.5/1.7 because I > was unable to use boost nor wxwidgets with 1.7. > I recently decided to make another effort to buil

Re: i686-w64-mingw32-gcc & ntifs.h

> * JonY [2011-08-19 06:39:03 +0800]: > > You are supposed to use -I to add the ddk path to gcc. how? I mean, -Iddk does not work because I do not have ddk directory in my build directory. how do I ask i686-w64-mingw32-gcc to print /usr/i686-w64-mingw32/sys-root/mingw/include/ ?? thanks! -- Sam

Contributing license information?

Soon, I will have prepared a list of the location of every license file in every Cygwin package. My motivation is to make it easy for people to find the license information, if they need it. (Preparing this information has required a lot of work on my part, so I would be happy if something co

Issue with inserting '@' at the command prompt.

Samuel Thibault, le Thu 14 Jul 2011 14:42:14 +0200, a écrit : > Lars Bjørndal, le Thu 14 Jul 2011 12:56:21 +0200, a écrit : > > BRLTTY has a cut & paste facility. It sometimes doesn't paste all > > characters inside cygwin. Pasting an att sign into a shell prompt, the > > terminal beeps, and no cha

Re: Issue with inserting '@' at the command prompt.

Samuel Thibault, le Fri 19 Aug 2011 04:37:40 +0200, a écrit : > - the user presses '@' on his braille keyboard (ascii 0x40). I forgot to mention: everything goes fine at the cmd, cygwin and mingw shell when the pressed key is e.g. 'a', i.e. which does not need altgr. Samuel -- Problem reports: