Re: ANSI C header files
Hi Marco. In my case I'm trying to install the 'grib_api' package from source (grib_api-1.9.9.tar.gz) found at http://www.ecmwf.int/products/data/software/download/grib_api.html After unpacking the tar-ball you're supposed to run 'configure' before installing but 'configure' hangs on "checking for ANSI C header files..." Regards, Kare The output looks like this: $ ./configure --prefix=/user/kare/software/ecmwf/lib 1.9.9 configuring grib_api 1.9.9 checking whether build environment is sane... yes checking for a BSD-compatible install... /usr/bin/install -c checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for xlc_r... no checking for xlc... no checking for gcc... gcc checking for C compiler default output file name... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... .exe checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for ranlib... ranlib checking for bison... bison -y checking for flex... flex checking lex output file root... lex.yy checking lex library... -lfl checking whether yytext is a pointer... yes checking for pgf90... no checking for pgf77... no checking for xlf... no checking for gfortran... gfortran checking whether we are using the GNU Fortran 77 compiler... yes checking whether gfortran accepts -g... yes checking for pgf90... no checking for xlf90... no checking for gfortran... gfortran checking whether we are using the GNU Fortran compiler... yes checking whether gfortran accepts -g... yes checking if Fortran 90 compiler capitalizes .mod filenames... yes checking if double and float are ieee big endian... no checking if double and float are ieee little endian... yes checking if Big Endian... no checking if inline in C... yes checking if bus error on unaligned pointers... no checking for posix_memalign... yes checking for _LARGEFILE_SOURCE value needed for large files... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking for jas_stream_memopen in -ljasper... yes checking for opj_image_create in -lopenjpeg... no checking for rm... rm checking for ar... ar checking whether gcc supports -pedantic -Wall... yes checking for pow in -lm... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for ANSI C header files... On ma., 2011-10-03 at 15:18 +0200, Marco Atzeri wrote: > On 10/3/2011 2:47 PM, Kåre Edvardsen wrote: > > Hi all! > > > > When installing software from source (./configure > > --prfix=/some/install/dir), the installation always hangs on: > > > > "checking for ANSI C header files..." > > > > Does anyone know if this is this a Windows or cygwin related problem? > > > > Cheers, > > Kåre > > > > How can we guess what are you trying to do without any info ? > Which software ? > > Regards > Marco > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ANSI C header files
Hi Kare, 2011/10/4 Kåre Edvardsen > Hi Marco. > > In my case I'm trying to install the 'grib_api' package from source > (grib_api-1.9.9.tar.gz) found at > http://www.ecmwf.int/products/data/software/download/grib_api.html > > After unpacking the tar-ball you're supposed to run 'configure' before > installing but 'configure' hangs on "checking for ANSI C header > files..." > > Regards, > Kare > > The output looks like this: > > $ ./configure --prefix=/user/kare/software/ecmwf/lib > 1.9.9 > configuring grib_api 1.9.9 > checking whether build environment is sane... yes > checking for a BSD-compatible install... /usr/bin/install -c > checking for a thread-safe mkdir -p... /usr/bin/mkdir -p (snip) > checking for library containing opendir... none required > checking for ANSI C header files... > > > > On ma., 2011-10-03 at 15:18 +0200, Marco Atzeri wrote: Please do not top-post: http://cygwin.com/acronyms/#TOFU Kill configure and take a look at the end of config.log configure logs each check and what it actually does. Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION
Kris Thielemans-2 wrote: > > Hi > > I'm running (up-to-date) Cygwin 1.7.9-1 on Windows7 sp1 64-bit. > > I recently am getting lots of errors like this > > bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION > > The messages do not happen all the time (for example, from bash (in minty) > I > do a few times ls. After about 4, I get 1-2 of these messages). They seem > to > mention only bash or sh. Here's an example of the stackdump > > > Exception: STATUS_ACCESS_VIOLATION at eip=6102048B > eax=00F70598 ebx=612454AC ecx=74C00F81 edx=003451F8 esi= > edi=0028F9F4 > ebp=61020C00 esp=0028C7C4 program=C:\cygwin\bin\bash.exe, pid 6236, thread > main > cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B > Stack trace: > Frame Function Args > End of stack trace > > This seems to happen with pretty much all Cygwin programs (I've tried > rsync, > ls, cat, vi, gcc). The strange thing is of course that the exception > mentioned is always in bash or sh, but that the actual program is just > running fine. (Just as a sanity check I set PS1=\$, but still the same). > > Up to recently, everything was fine on my system. It might have started > after I did a rebaseall but I am unfortunately not sure. > > What can I do to debug this? > > Thanks > > Kris > > > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > STATUS_ACCESS_VIOLATION at eip=6102048B I have debugged that, see http://old.nabble.com/STATUS_ACCESS_VIOLATION-to32557806.html. I do not know the direct cause. The post above contains a modification to tamper the problem. Without anything else, cat /proc/*/maps | egrep '^[01]' | egrep -v cygdrive | egrep -v .exe$ might reveal troubled dlls. Does it help to rebase them manually ? Please, if you need again help with workarround or solution, ask a new question to the folks on this forum. -- View this message in context: http://old.nabble.com/bash-2112-exception%3A%3Ahandle%3A-Exception%3A-STATUS_ACCESS_VIOLATION-tp32566047p32587500.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: admin privileges when logging in by ssh?
On Sep 12 10:24, Andrew Schulman wrote: > > When a user with administrative privileges logs in to sshd, it seems that > > the user is only granted > > standard user privileges for that session. Is there a way around that? > > How can I get the admin > > privileges for that session? > > Winding this up: > > Password authentication to sshd is all that's needed to be granted the > account's admin privileges on > login. I was mistaken about UAC: unlike at the console, when you log in by > ssh, the account's > admin privileges are granted at login, without needing any further > authentication to UAC. I'm quite puzzeled since password authentication should not be needed. This should work with pubkey as well. Please see http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview for a discussion how setuid works in Cygwin. In all cases, password auth and passwordless auth, you should get a full admin token. In case of password auth and in the passwordless methods 2 and 3, the OS returns a restricted token under UAC, but that token has a reference to the full admin token attached. Cygwin fetches this token and uses that when switching the user context. In the default passwordless method 1, Cygwin creates a token from scratch, which also has full admin rights. However, this token has a couple of problems as described in http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1 Probably that's what you stumble over. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ANSI C header files
On 10/4/2011 10:11 AM, Csaba Raduly wrote: Hi Kare, 2011/10/4 Kåre Edvardsen Hi Marco. In my case I'm trying to install the 'grib_api' package from source (grib_api-1.9.9.tar.gz) found at http://www.ecmwf.int/products/data/software/download/grib_api.html After unpacking the tar-ball you're supposed to run 'configure' before installing but 'configure' hangs on "checking for ANSI C header files..." Regards, Kare The output looks like this: $ ./configure --prefix=/user/kare/software/ecmwf/lib 1.9.9 configuring grib_api 1.9.9 checking whether build environment is sane... yes checking for a BSD-compatible install... /usr/bin/install -c checking for a thread-safe mkdir -p... /usr/bin/mkdir -p (snip) checking for library containing opendir... none required checking for ANSI C header files... On ma., 2011-10-03 at 15:18 +0200, Marco Atzeri wrote: Please do not top-post: http://cygwin.com/acronyms/#TOFU Kill configure and take a look at the end of config.log configure logs each check and what it actually does. Csaba Kare, in addition to the TOFU advise, running configure of grib_api-1.9.9_libtool.tar.gz on my XP-SP3 gave no problem. "Configuration completed." The ANSI C test is a basic one configure:6808: checking for ANSI C header files configure:6828: gcc -c -g -O2 conftest.c >&5 configure:6828: $? = 0 configure:6901: gcc -o conftest.exe -g -O2 conftest.c >&5 configure:6901: $? = 0 configure:6901: ./conftest.exe configure:6901: $? = 0 configure:6912: result: yes so a BLODA interference is possible http://cygwin.com/faq/faq.using.html#faq.using.bloda see also http://cygwin.com/problems.html Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ANSI C header files
On Tue, Oct 4, 2011 at 12:13 PM, Marco Atzeri wrote: (snip) > Kare, > in addition to the TOFU advise, > > running configure of grib_api-1.9.9_libtool.tar.gz > on my XP-SP3 gave no problem. > > "Configuration completed." > > The ANSI C test is a basic one > > configure:6808: checking for ANSI C header files > configure:6828: gcc -c -g -O2 conftest.c >&5 > configure:6828: $? = 0 > configure:6901: gcc -o conftest.exe -g -O2 conftest.c >&5 > configure:6901: $? = 0 > configure:6901: ./conftest.exe > configure:6901: $? = 0 > configure:6912: result: yes I reproduced the hang on my Cygwin CYGWIN_NT-6.0 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin and gcc version 4.5.3 This appears to be the critical spot (line 6820-6828) if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | $EGREP "memchr" >/dev/null 2>&1; then : else ac_cv_header_stdc=no fi It tries to run the preprocessor and pipe its output into egrep. Unfortunately, the EGREP variable appears to be empty, so the end result is similar to: gcc -E conftest.c | memchr Trying the above from the bash prompt (in both mintty and classic Cygwin prompt) results in an (unkillable from Cygwin) cc1.exe which is perpetually waiting for output: $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 4484 14484 4752 con 539771 Oct 3 /usr/bin/XWin 7848 17848 7848? 539771 14:03:11 /usr/bin/mintty 646878486468 74601 539771 14:03:11 /usr/bin/bash 6692 16692 6692? 539771 10:12:37 /usr/bin/mintty 460066924600 71563 539771 10:12:37 /usr/bin/ssh 627264686272 63561 539771 13:08:43 /usr/bin/gcc-4 O749262726272 68561 539771 13:08:43 /usr/lib/gcc/i686-pc-cygwin/4.5.3/cc1 7404646874045241 539771 13:08:46 /usr/bin/ps So, the workaround is to replace $EGREP with egrep in configure; then configure runs successfully. This seems to be some peculiarity of Cygwin's current GCC 4.5.3; neither GCC 3.4.4 in Cygwin 1.7 nor GCC 4.3.4 in Cygwin 1.7 nor GCC 4.3.2 in Cygwin 1.5 exhibit this hang. Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ANSI C header files
On 10/4/2011 1:24 PM, Csaba Raduly wrote: On Tue, Oct 4, 2011 at 12:13 PM, Marco Atzeri wrote: (snip) Kare, in addition to the TOFU advise, running configure of grib_api-1.9.9_libtool.tar.gz on my XP-SP3 gave no problem. "Configuration completed." The ANSI C test is a basic one configure:6808: checking for ANSI C header files configure:6828: gcc -c -g -O2 conftest.c>&5 configure:6828: $? = 0 configure:6901: gcc -o conftest.exe -g -O2 conftest.c>&5 configure:6901: $? = 0 configure:6901: ./conftest.exe configure:6901: $? = 0 configure:6912: result: yes I reproduced the hang on my Cygwin CYGWIN_NT-6.0 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin and gcc version 4.5.3 This appears to be the critical spot (line 6820-6828) if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | $EGREP "memchr">/dev/null 2>&1; then : else ac_cv_header_stdc=no fi It tries to run the preprocessor and pipe its output into egrep. Unfortunately, the EGREP variable appears to be empty, so the end result is similar to: gcc -E conftest.c | memchr Trying the above from the bash prompt (in both mintty and classic Cygwin prompt) results in an (unkillable from Cygwin) cc1.exe which is perpetually waiting for output: $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 4484 14484 4752 con 539771 Oct 3 /usr/bin/XWin 7848 17848 7848? 539771 14:03:11 /usr/bin/mintty 646878486468 74601 539771 14:03:11 /usr/bin/bash 6692 16692 6692? 539771 10:12:37 /usr/bin/mintty 460066924600 71563 539771 10:12:37 /usr/bin/ssh 627264686272 63561 539771 13:08:43 /usr/bin/gcc-4 O749262726272 68561 539771 13:08:43 /usr/lib/gcc/i686-pc-cygwin/4.5.3/cc1 7404646874045241 539771 13:08:46 /usr/bin/ps So, the workaround is to replace $EGREP with egrep in configure; then configure runs successfully. This seems to be some peculiarity of Cygwin's current GCC 4.5.3; neither GCC 3.4.4 in Cygwin 1.7 nor GCC 4.3.4 in Cygwin 1.7 nor GCC 4.3.2 in Cygwin 1.5 exhibit this hang. Csaba Hi Csaba, the configure looks for grep/egrep/fgrep configure:3610: checking for grep that handles long lines and -e configure:3668: result: /usr/bin/grep configure:3673: checking for egrep configure:3735: result: /usr/bin/grep -E configure:3740: checking for fgrep configure:3802: result: /usr/bin/grep -F and set them config.status:GREP='/usr/bin/grep' config.status:EGREP='/usr/bin/grep -E' config.status:FGREP='/usr/bin/grep -F' same compiler $ cygcheck -c -d gcc4 Cygwin Package Information Package Version gcc4 4.5.3-2 but I am running the last cygwin snapshot $ uname -srv CYGWIN_NT-5.1 1.7.10s(0.251/5/3) 20110829 15:53:50 Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin started speaking German today
On Sep 13 09:45, Eric Blake wrote:
> On 09/09/2011 08:59 AM, Corinna Vinschen wrote:
> >On Sep 9 13:33, Andy Koppe wrote:
> >>The 'C.UTF-8' default locale is not a bug, it was a deliberate design
> >>decision.
> >
> >Exactly. And it has been discussed a lot on the cygwin-apps mailing
> >list.
> >
> >And above all, there *is* an official way for the user to align the
> >Cygwin locale with the Windows locale, see the -s and -u options
> >of the locale(1) command:
> >
> > http://cygwin.com/cygwin-ug-net/using-utils.html#locale
>
> On 09/09/2011 09:09 AM, Corinna Vinschen wrote:
> >> OK, then the following four facilities are needed in Cygwin.
> >>
> >> 1) We need the name of the locale which is in effect when the user has
> >> not specified environment variables.
> >
> > In Fedora, for instance, the fallback is what is set as system default
> > in /etc/sysconfig/i18n.
> >
> > In Cygwin the fallback is the system default set in
> /etc/profile.d/lang.sh
> > or /etc/profile.d/lang.csh.
> >
> > Why should libintl use anything else on Cygwin, but not on Linux?
> >
>
> Given this, I think the bug is in cygwin for having base files
> /etc/profile.d/lang.{sh,csh} which hardcode LANG to C.UTF-8 instead
> of using locale -s -u to default LANG to the preferred Windows
> settings.
Bug? Didn't we choose C.UTF-8 after a long discussion? Are the points
raised in this discussion invalid or outdated now? Why? I don't object
against using `locale -sU' in lang.sh/lang.csh, but we should not do
this without a discussion of the pros and cons.
> Libintl should NOT be second-guessing an explicit setting
> of LANG,
ACK.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: pressing ENTER scrambles scrolled MS-DOS-console
On Sep 26 14:18, Paul Maier wrote: > Hi, > > scrolling up the console output to review the console history, then pressing > Enter scrambles the console. That's a long standing behaviour of the Cygwin console emulation. I guess it can be fixed, but somebody will have to do it. In the meantime, try mintty as terminal. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin started speaking German today
On 10/4/2011 8:28 AM, Corinna Vinschen wrote:
> On Sep 13 09:45, Eric Blake wrote:
>> Given this, I think the bug is in cygwin for having base files
>> /etc/profile.d/lang.{sh,csh} which hardcode LANG to C.UTF-8 instead
>> of using locale -s -u to default LANG to the preferred Windows
>> settings.
>
> Bug? Didn't we choose C.UTF-8 after a long discussion? Are the points
> raised in this discussion invalid or outdated now? Why? I don't object
> against using `locale -sU' in lang.sh/lang.csh, but we should not do
> this without a discussion of the pros and cons.
IIRC, that discussion occurred before the 'locale' application (was
written|got smarter). Sure, I think C.UTF-8 should be the "default
default" but the arguments in favor of respecting the users' own Windows
i18n settings make sense.
However, one issue is that windows basically will always have SOME
setting -- even if just "English". Which would cause locale to report
'en_US' or something. So you'd never actually SEE the "default default"
of C.UTF-8 take effect. Also, would locale append '.UTF-8' (or would
lang.{sh,csh} do so?).
Maybe we should start a new thread on this topic, listing the pros and
cons as Corinna suggested. Who wants to summarize the "con" side of the
argument?
--
Chuck
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ANSI C header files
On Tue, Oct 4, 2011 at 12:13 PM, Marco Atzeri wrote: (snip) > Kare, > in addition to the TOFU advise, > > running configure of grib_api-1.9.9_libtool.tar.gz > on my XP-SP3 gave no problem. > > "Configuration completed." > > The ANSI C test is a basic one > > configure:6808: checking for ANSI C header files > configure:6828: gcc -c -g -O2 conftest.c >&5 > configure:6828: $? = 0 > configure:6901: gcc -o conftest.exe -g -O2 conftest.c >&5 > configure:6901: $? = 0 > configure:6901: ./conftest.exe > configure:6901: $? = 0 > configure:6912: result: yes > > I reproduced the hang on my Cygwin CYGWIN_NT-6.0 1.7.9(0.237/5/3) > 2011-03-29 10:10 i686 Cygwin > and gcc version 4.5.3 > > This appears to be the critical spot (line 6820-6828) > > if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | > $EGREP "memchr" >/dev/null 2>&1; then > : > else > ac_cv_header_stdc=no > fi > > It tries to run the preprocessor and pipe its output into egrep. > Unfortunately, the EGREP variable appears to be empty, so the end > result is similar to: > > gcc -E conftest.c | memchr > > Trying the above from the bash prompt (in both mintty and classic > Cygwin prompt) results in an (unkillable from Cygwin) cc1.exe which is > perpetually waiting for output: > > $ ps > PIDPPIDPGID WINPID TTY UIDSTIME COMMAND > 4484 14484 4752 con 539771 Oct 3 /usr/bin/XWin > 7848 17848 7848? 539771 14:03:11 /usr/bin/mintty > 646878486468 74601 539771 14:03:11 /usr/bin/bash > 6692 16692 6692? 539771 10:12:37 /usr/bin/mintty > 460066924600 71563 539771 10:12:37 /usr/bin/ssh > 627264686272 63561 539771 13:08:43 /usr/bin/gcc-4 > O749262726272 68561 539771 13:08:43 > /usr/lib/gcc/i686-pc-cygwin/4.5.3/cc1 > 7404646874045241 539771 13:08:46 /usr/bin/ps > > > So, the workaround is to replace $EGREP with egrep in configure; then > configure runs successfully. > > This seems to be some peculiarity of Cygwin's current GCC 4.5.3; > neither GCC 3.4.4 in Cygwin 1.7 nor GCC 4.3.4 in Cygwin 1.7 nor GCC > 4.3.2 in Cygwin 1.5 exhibit this hang. > > Csaba Csaba & Marco. Marco: Your try on the XP-SP3 gave no problem. My try on Win 7 Pro hangs, but as Csaba points out: This seems to be some peculiarity of Cygwin's current GCC 4.5.3 Csaba: Replacing $EGREP with egrep in configure did make the difference! Thanx to both of you for excellent help. Regards, Kare -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.9 Missing SIGPIPE?
Peter Rosin skrev 2011-09-28 17:26: > Hi! > > When I use bash to build pipelines, they sometimes don't finish but > instead some process remains running. Example: > > $ tail -f -n 1 log.txt | grep . | head -n 2 > > Almost instantly I get the expected two lines of output, but no prompt > back. I have to use ctrl-c. If I don't ctrl-c I can run pstree in > another terminal and see this: > > $ pstree > ?─┬─mintty───bash───tail > └─mintty───bash───pstree This example is a poor one, as tail simply waits for a new line, when it gets a new line it forwards it to the pipe and promptly receives a SIGPIPE as grep is not there anymore. I'll get back when I have distilled a better STC. If I can... Cheers, Peter -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.9 Missing SIGPIPE?
On 10/4/2011 3:53 PM, Peter Rosin wrote: Peter Rosin skrev 2011-09-28 17:26: Hi! When I use bash to build pipelines, they sometimes don't finish but instead some process remains running. Example: $ tail -f -n 1 log.txt | grep . | head -n 2 Almost instantly I get the expected two lines of output, but no prompt back. I have to use ctrl-c. If I don't ctrl-c I can run pstree in another terminal and see this: $ pstree ?─┬─mintty───bash───tail └─mintty───bash───pstree This example is a poor one, as tail simply waits for a new line, when it gets a new line it forwards it to the pipe and promptly receives a SIGPIPE as grep is not there anymore. I'll get back when I have distilled a better STC. If I can... Cheers, Peter Hi Peter, are you referring on something like SIGHUP on PTY closure ? http://cygwin.com/ml/cygwin/2011-07/msg00295.html http://pubs.opengroup.org/onlinepubs/9699919799/functions/close.html Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.9 Missing SIGPIPE?
On Tue, Oct 04, 2011 at 04:00:13PM +0200, Marco Atzeri wrote: >On 10/4/2011 3:53 PM, Peter Rosin wrote: >> Peter Rosin skrev 2011-09-28 17:26: >>> Hi! >>> >>> When I use bash to build pipelines, they sometimes don't finish but >>> instead some process remains running. Example: >>> >>> $ tail -f -n 1 log.txt | grep . | head -n 2 >>> >>> Almost instantly I get the expected two lines of output, but no prompt >>> back. I have to use ctrl-c. If I don't ctrl-c I can run pstree in >>> another terminal and see this: >>> >>> $ pstree >>> ??mintty?bash?tail >>>??mintty?bash?pstree >> >> This example is a poor one, as tail simply waits for a new line, when it >> gets a new line it forwards it to the pipe and promptly receives a >> SIGPIPE as grep is not there anymore. >> >> I'll get back when I have distilled a better STC. If I can... > >Hi Peter, >are you referring on something like SIGHUP on PTY closure ? > >http://cygwin.com/ml/cygwin/2011-07/msg00295.html >http://pubs.opengroup.org/onlinepubs/9699919799/functions/close.html Note that this thread contains your assertion that something isn't happening correctly but it isn't clear that your analysis is correct. But, no, SIGPIPE != SIGHUP and the above example clearly shows a completely different scenario than what is described in the above thread. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin started speaking German today
On Oct 4 08:45, Charles Wilson wrote:
> On 10/4/2011 8:28 AM, Corinna Vinschen wrote:
> > On Sep 13 09:45, Eric Blake wrote:
> >> Given this, I think the bug is in cygwin for having base files
> >> /etc/profile.d/lang.{sh,csh} which hardcode LANG to C.UTF-8 instead
> >> of using locale -s -u to default LANG to the preferred Windows
> >> settings.
> >
> > Bug? Didn't we choose C.UTF-8 after a long discussion? Are the points
> > raised in this discussion invalid or outdated now? Why? I don't object
> > against using `locale -sU' in lang.sh/lang.csh, but we should not do
> > this without a discussion of the pros and cons.
>
> IIRC, that discussion occurred before the 'locale' application (was
> written|got smarter). Sure, I think C.UTF-8 should be the "default
> default" but the arguments in favor of respecting the users' own Windows
> i18n settings make sense.
Does it? Even if I'm running a german OS, I absolutely hate to see
german diagnostic output from gcc, and I absolutely hate certain
programs using non-ASCII chars in output. (In)famous examples are
Unicode quoting chars rather than ' or ", or using the Unicode hyphen
character rather than -. But that's just me.
> However, one issue is that windows basically will always have SOME
> setting -- even if just "English". Which would cause locale to report
> 'en_US' or something. So you'd never actually SEE the "default default"
> of C.UTF-8 take effect. Also, would locale append '.UTF-8' (or would
> lang.{sh,csh} do so?).
That's what the -U option is for. See `locale --help'.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.9 Missing SIGPIPE?
On 10/4/2011 4:09 PM, Christopher Faylor wrote: On Tue, Oct 04, 2011 at 04:00:13PM +0200, Marco Atzeri wrote: On 10/4/2011 3:53 PM, Peter Rosin wrote: Peter Rosin skrev 2011-09-28 17:26: Hi! When I use bash to build pipelines, they sometimes don't finish but instead some process remains running. Example: $ tail -f -n 1 log.txt | grep . | head -n 2 Almost instantly I get the expected two lines of output, but no prompt back. I have to use ctrl-c. If I don't ctrl-c I can run pstree in another terminal and see this: $ pstree ??mintty?bash?tail ??mintty?bash?pstree This example is a poor one, as tail simply waits for a new line, when it gets a new line it forwards it to the pipe and promptly receives a SIGPIPE as grep is not there anymore. I'll get back when I have distilled a better STC. If I can... Hi Peter, are you referring on something like SIGHUP on PTY closure ? http://cygwin.com/ml/cygwin/2011-07/msg00295.html http://pubs.opengroup.org/onlinepubs/9699919799/functions/close.html Note that this thread contains your assertion that something isn't happening correctly but it isn't clear that your analysis is correct. But, no, SIGPIPE != SIGHUP and the above example clearly shows a completely different scenario than what is described in the above thread. cgf Hi Cgf, I know that SIGPIPE != SIGHUP, but Peter mentioned that the example is not really representative of the PIPE problem he found, so eventually he catched the same problem I saw on mc. Of course, it could be a different one. Referring to the SIGHUP thread This portion of the standard, if I am not wrong, it is not currently implemented in cygwin: "If fildes refers to the master side of a pseudo-terminal, and this is the last close, a SIGHUP signal shall be sent to the controlling process, if any, for which the slave side of the pseudo-terminal is the controlling terminal. It is unspecified whether closing the master side of the pseudo-terminal flushes all queued input and output." The workaround I implemented in mc was to send the SIGHUP to the subshell, before mc exit, instead on relying on cygwin to do it. Am I misundestanding the standard ? Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Writing to Windows Share issues fixed in cygwin1-20110829.dll.bz2
On Sep 16 11:17, Keith Christian wrote: > I was wrong. > > Only some improvement using the cygwin1-20110829.dll.bz2 snapshot. > Problems still exist when trying to check in a file with RCS on this > Windows share. > > Annotated test example below. Apologies for not being brief. > > Any ideas appreciated. However, progress has been made with the 0829 > snapshot, at least I can create files on this share.. > [...] > # 11 - Comments: Check testfile.1 into RCS - first indication of > problems. Unable to use the "testfile.1" name with a ",v" appended to > it: > > Fri Sep 16 10:31:35 (kchristian@laptop-pc) > /cygdrive/z/foo/bar/baz>ci -l -m"Attempted check in using 20110829 > Cygwin snapshot" -t-"Testing new cygwin snapshot to see if it fixes > Windows Share writing difficulties" ./testfile.1 > ./RCS/testfile.1,v <-- ./testfile.1 > initial revision: 1.1 > ci: ./RCS/testfile.1,v: Permission denied > ci: saved in ./RCS/_0qrsNBd That's weird. The fact that you can create and write the _0qrsNBd file shows that the write permission issue is fixed. It seems that renaming the file to testfile.1,v fails, but it's not clear why this should happen. What kind of share is that (/usr/lib/csih/getVolInfo /cygdrive/z)? Does manual renaming the _0qrsNBd file work? Does deleteing the _0qrsNBd file work? Can you reproduce this situation from scratch and call the ci command under strace, like this strace -o ci.trace ci -l -mfoo ./testfile.1 and send the strace output here? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: error while running shell in emacs
On 10/4/2011 2:56 AM, Markus Hoenicka wrote: Ken Brown was heard to say: On 10/2/2011 5:56 PM, Ken Brown wrote: On 10/2/2011 5:35 PM, Ken Brown wrote: On 9/30/2011 3:04 PM, Ken Brown wrote: On 9/30/2011 10:27 AM, Markus Hoenicka wrote: Hi, after moving to a new position I have set up a fresh Cygwin installation: CYGWIN_NT-5.1 sbhc123 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin I use some Emacs extensions which execute external programs using (call-process). This used to work on my previous setup, but it fails on my current box. The following command run in Emacs reproduces what seems to be the problem: (call-process "bash" nil '(t t) nil "-ic" "ls -al") bash: Kann die Prozessgruppe des Terminals nicht setzen (-1).: Inappropriate ioctl for device bash: Keine Job Steuerung in dieser Shell. As you can see, my Cygwin also started speaking German, but I didn't get round to fix that yet. The messages loosely translate to: "cannot set terminal process group" and "no job control in this shell". Is this an incorrect setup of either Cygwin or Emacs, or is this indeed a problem that crept into Cygwin recently? I can reproduce this problem. It reminds me of a problem that I reported in http://cygwin.com/ml/cygwin/2011-06/msg00174.html , but that started with the 2011-05-05 snapshot and was fixed in the 2011-06-16 snapshot. The problem you're reporting exists in Cygwin 1.7.9 and persists in the latest snapshot, but with different symptoms: Instead of printing error messages, emacs hangs and has to be killed. If one of the Cygwin developers wants to look at this, here are the steps to reproduce it: 1. Start emacs. 2. Type b [This should put you in the *scratch* buffer.] 3. Type (or copy and paste) the following text into the *scratch* buffer: (call-process "bash" nil '(t t) nil "-ic" "ls -al") 4. With the cursor positioned immediately after the closing parenthesis, type FWIW, the change in behavior (i.e., emacs hanging instead of giving an error message) starts with the 2006-06-13 snapshot. And it may be Ignore the statement that it starts with the 2006-06-13 snapshot. I made a mistake and didn't test enough snapshots. I'll have to continue bisecting. All I know at the moment is that there's an error message in the 2011-05-10 snapshot and that the "hang" occurs in the 2011-06-13 snapshot. There are still a lot of snapshots in between that need testing. Sorry for the noise. I've finished testing snapshots. Up through the 2011-05-20 snapshot, I get the error messages reported by the OP: bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell Starting with the 2011-05-28 snapshot, I instead get the message "Aborted". Starting with the 2011-06-01 snapshot, I get the "hanging" behavior that I reported previously (with a stopped bash process). There was a similar pattern in the problem I reported in http://cygwin.com/ml/cygwin/2011-06/msg00174.html Ken Do you have any idea which Cygwin DLL version introduced the problem? I have never used snapshots, but as I can't access my previous box anymore I can't really tell which version it ran. No, 1.7.9 is the earliest version I've tested. I'm inclined to wait and see if cgf or Corinna says it would be useful for us to test earlier versions. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: admin privileges when logging in by ssh?
> On Sep 12 10:24, Andrew Schulman wrote: > > > When a user with administrative privileges logs in to sshd, it seems that > > > the user is only granted > > > standard user privileges for that session. Is there a way around that? > > > How can I get the admin > > > privileges for that session? > > > > Winding this up: > > > > Password authentication to sshd is all that's needed to be granted the > > account's admin privileges on > > login. I was mistaken about UAC: unlike at the console, when you log in > > by ssh, the account's > > admin privileges are granted at login, without needing any further > > authentication to UAC. > > I'm quite puzzeled since password authentication should not be needed. > This should work with pubkey as well. Please see > http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview for > a discussion how setuid works in Cygwin. > > In all cases, password auth and passwordless auth, you should get a full > admin token. In case of password auth and in the passwordless methods > 2 and 3, the OS returns a restricted token under UAC, but that token > has a reference to the full admin token attached. Cygwin fetches this > token and uses that when switching the user context. In the default > passwordless method 1, Cygwin creates a token from scratch, which also > has full admin rights. However, this token has a couple of problems as > described in http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1 > Probably that's what you stumble over. Thanks for writing up that documentation of user context switching (I assume it was you who wrote it). It's complex. So IIUC, sshd by default uses method 1, creating a token from scratch. So when a user logs in with pubkey authentication, they won't have a logon session, which means their SID name may be misidentified by native Windows apps; and they won't have access to password-protected network shares. But they should still have all of the privileges normally granted to their account. I'm not able to test it right now, but what I observed before was that when a user with the SeBackupPrivilege and SeBackupPrivilege privileges logged in by password authentication, it could use those privileges (with rsync); but when it logged in by pubkey authentication, it couldn't. So I agree that this is puzzling since it doesn't seem to square with the description above. This is on Windows 7 Home Premium. I'll test this again when I can, to be sure what I observed is correct. If you can suggest any diagnostic tools to help identify the available privileges, that would be helpful. I'll also look into implementing methods 2 or 3, so I can do away with the password authentication. Andrew. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.9 Missing SIGPIPE?
On Tue, Oct 04, 2011 at 04:33:33PM +0200, Marco Atzeri wrote: >On 10/4/2011 4:09 PM, Christopher Faylor wrote: >> On Tue, Oct 04, 2011 at 04:00:13PM +0200, Marco Atzeri wrote: >>> On 10/4/2011 3:53 PM, Peter Rosin wrote: Peter Rosin skrev 2011-09-28 17:26: > Hi! > > When I use bash to build pipelines, they sometimes don't finish but > instead some process remains running. Example: > > $ tail -f -n 1 log.txt | grep . | head -n 2 > > Almost instantly I get the expected two lines of output, but no prompt > back. I have to use ctrl-c. If I don't ctrl-c I can run pstree in > another terminal and see this: > > $ pstree > ??mintty?bash?tail > ??mintty?bash?pstree This example is a poor one, as tail simply waits for a new line, when it gets a new line it forwards it to the pipe and promptly receives a SIGPIPE as grep is not there anymore. I'll get back when I have distilled a better STC. If I can... >>> >>> Hi Peter, >>> are you referring on something like SIGHUP on PTY closure ? >>> >>> http://cygwin.com/ml/cygwin/2011-07/msg00295.html >>> http://pubs.opengroup.org/onlinepubs/9699919799/functions/close.html >> >> Note that this thread contains your assertion that something isn't >> happening correctly but it isn't clear that your analysis is correct. >> >> But, no, SIGPIPE != SIGHUP and the above example clearly shows a >> completely different scenario than what is described in the above >> thread. >> >> cgf > >Hi Cgf, >I know that SIGPIPE != SIGHUP, but Peter mentioned that the example >is not really representative of the PIPE problem he found, so eventually >he catched the same problem I saw on mc. >Of course, it could be a different one. > >Referring to the SIGHUP thread >This portion of the standard, if I am not wrong, >it is not currently implemented in cygwin: > >"If fildes refers to the master side of a pseudo-terminal, and this is >the last close, a SIGHUP signal shall be sent to the controlling >process, if any, for which the slave side of the pseudo-terminal is the >controlling terminal. It is unspecified whether closing the master side >of the pseudo-terminal flushes all queued input and output." As I mentioned in the thread, that is supposed to be implemented in Cygwin. I could never see a case where it wasn't sent. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: admin privileges when logging in by ssh?
On Oct 4 11:59, Andrew Schulman wrote:
> > On Sep 12 10:24, Andrew Schulman wrote:
> > > > When a user with administrative privileges logs in to sshd, it seems
> > > > that the user is only granted
> > > > standard user privileges for that session. Is there a way around that?
> > > > How can I get the admin
> > > > privileges for that session?
> > >
> > > Winding this up:
> > >
> > > Password authentication to sshd is all that's needed to be granted the
> > > account's admin privileges on
> > > login. I was mistaken about UAC: unlike at the console, when you log in
> > > by ssh, the account's
> > > admin privileges are granted at login, without needing any further
> > > authentication to UAC.
> >
> > I'm quite puzzeled since password authentication should not be needed.
> > This should work with pubkey as well. Please see
> > http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview for
> > a discussion how setuid works in Cygwin.
> >
> > In all cases, password auth and passwordless auth, you should get a full
> > admin token. In case of password auth and in the passwordless methods
> > 2 and 3, the OS returns a restricted token under UAC, but that token
> > has a reference to the full admin token attached. Cygwin fetches this
> > token and uses that when switching the user context. In the default
> > passwordless method 1, Cygwin creates a token from scratch, which also
> > has full admin rights. However, this token has a couple of problems as
> > described in http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1
> > Probably that's what you stumble over.
>
> Thanks for writing up that documentation of user context switching (I
> assume it was you who wrote it). It's complex.
Sorry, but the Windows authentication stuff is complex.
> So IIUC, sshd by default uses method 1, creating a token from scratch. So
Not sshd in the first place, but the underlying set(e)uid system call.
> when a user logs in with pubkey authentication, they won't have a logon
> session, which means their SID name may be misidentified by native Windows
> apps; and they won't have access to password-protected network shares. But
> they should still have all of the privileges normally granted to their
> account.
Right. And in contrast to the normal user token, the token hand-crafted
by Cygwin has all privileges enabled by default. But it suffers from
the fact that there's no login session attached to it. Don't ask. This
part of the authentication mechanism I don't understand and afaics it's
not documented at all.
> I'm not able to test it right now, but what I observed before was that when
> a user with the SeBackupPrivilege and SeBackupPrivilege privileges logged
> in by password authentication, it could use those privileges (with rsync);
> but when it logged in by pubkey authentication, it couldn't. So I agree
> that this is puzzling since it doesn't seem to square with the description
> above. This is on Windows 7 Home Premium.
The OS shouldn't matter.
> I'll test this again when I can, to be sure what I observed is correct. If
> you can suggest any diagnostic tools to help identify the available
> privileges, that would be helpful.
Does Windows 7 Home Premium come with a native whoami? I'm only
running Ultimate, which has this tool:
$ /cygdrive/c/Windows/System32/whoami /all
With method 1 you will see a wrong user name showing up, even though
the user SID is correct.
If you don't have a native whoami, I hacked some tool once which I
use all the time to do basically the same as the Windows whoami.
I attached the ugly source code, build with
$ g++ -o gettokinfo gettokinfo.cc
and run from the session you want to check like this
$ ./gettokinfo
if you don't want to see the privileges, or like this
$ ./gettokinfo x
if you want to see them.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
#include
#include
#define _WIN32_WINNT 0x0600
#include
int
error (const char *funcname)
{
fprintf (stderr, "%s: %lu\n", funcname, GetLastError());
return 1;
}
char *
convert_sid_to_string_sid (const PSID psid, char *sid_str)
{
char t[32];
DWORD i;
if (!psid)
return NULL;
strcpy (sid_str, "S-1-");
sprintf(t, "%u", GetSidIdentifierAuthority (psid)->Value[5]);
strcat (sid_str, t);
for (i = 0; i < *GetSidSubAuthorityCount (psid); ++i)
{
sprintf(t, "-%lu", *GetSidSubAuthority (psid, i));
strcat (sid_str, t);
}
return sid_str;
}
HANDLE tok;
char buf[4096];
DWORD size;
PVOID
gti (TOKEN_INFORMATION_CLASS type)
{
if (GetTokenInformation (tok, type, buf, 4096, &size))
return (PVOID) buf;
return NULL;
}
PVOID
hgti (HANDLE token, TOKEN_INFORMATION_CLASS type)
{
if (GetTokenInformation (token, type, buf, 4096, &size))
return (PVOID) buf;
return NULL;
}
void
print_acl (PACL acl)
{
printf ("\n");
if (! acl)
printf ("empty
Re: cygwin started speaking German today
Corinna Vinschen schreef, Op 4-10-2011 16:29: Does it? Even if I'm running a german OS, I absolutely hate to see german diagnostic output from gcc, and I absolutely hate certain programs using non-ASCII chars in output. (In)famous examples are Unicode quoting chars rather than ' or ", or using the Unicode hyphen character rather than -. But that's just me. You got used to ASCII, like all the old-timers... ;) export LANG=C is your solution. By the way, I noticed that with the default locale C.UTF-8 the nl_langinfo(CODESET) C function returns wrongly "ISO-8859-1", while if I set LANG to nl_NL.UTF-8 nl_langinfo(CODESET) returns correctly "UTF-8". The locale command returns LC_ CTYPE="C.UTF-8" and LC_CTYPE="nl_NL.UTF-8". -- Erwin -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin started speaking German today
On Oct 4 20:03, Erwin Waterlander wrote:
> Corinna Vinschen schreef, Op 4-10-2011 16:29:
> >Does it? Even if I'm running a german OS, I absolutely hate to see
> >german diagnostic output from gcc, and I absolutely hate certain
> >programs using non-ASCII chars in output. (In)famous examples are
> >Unicode quoting chars rather than ' or ", or using the Unicode
> >hyphen character rather than -. But that's just me.
>
> You got used to ASCII, like all the old-timers... ;)
> export LANG=C is your solution.
>
> By the way, I noticed that with the default locale C.UTF-8 the
> nl_langinfo(CODESET) C function returns wrongly
> "ISO-8859-1",
Not for me:
$ cat > setl.c <
#include
#include
int main(int argc, char **argv)
{
char *loc;
if (argc > 1)
loc = setlocale (LC_ALL, argv[1]);
else
loc = setlocale (LC_CTYPE, NULL);
printf ("locale: %s charset: %s\n", loc, nl_langinfo (CODESET));
return 0;
}
EOF
$ gcc -o setl setl.c
$ ./setl
locale: C charset: ANSI_X3.4-1968
$ ./setl C
locale: C charset: ANSI_X3.4-1968
$ ./setl C.utf8
locale: C.utf8 charset: UTF-8
$ ./setl C.UTF-8
locale: C.UTF-8 charset: UTF-8
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ANSI C header files
On 04/10/2011 9:05 AM, Kåre Edvardsen wrote: On Tue, Oct 4, 2011 at 12:13 PM, Marco Atzeri wrote: (snip) Kare, in addition to the TOFU advise, running configure of grib_api-1.9.9_libtool.tar.gz on my XP-SP3 gave no problem. "Configuration completed." The ANSI C test is a basic one configure:6808: checking for ANSI C header files configure:6828: gcc -c -g -O2 conftest.c>&5 configure:6828: $? = 0 configure:6901: gcc -o conftest.exe -g -O2 conftest.c>&5 configure:6901: $? = 0 configure:6901: ./conftest.exe configure:6901: $? = 0 configure:6912: result: yes I reproduced the hang on my Cygwin CYGWIN_NT-6.0 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin and gcc version 4.5.3 This appears to be the critical spot (line 6820-6828) if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | $EGREP "memchr">/dev/null 2>&1; then : else ac_cv_header_stdc=no fi It tries to run the preprocessor and pipe its output into egrep. Unfortunately, the EGREP variable appears to be empty, so the end result is similar to: gcc -E conftest.c | memchr Trying the above from the bash prompt (in both mintty and classic Cygwin prompt) results in an (unkillable from Cygwin) cc1.exe which is perpetually waiting for output: $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 4484 14484 4752 con 539771 Oct 3 /usr/bin/XWin 7848 17848 7848? 539771 14:03:11 /usr/bin/mintty 646878486468 74601 539771 14:03:11 /usr/bin/bash 6692 16692 6692? 539771 10:12:37 /usr/bin/mintty 460066924600 71563 539771 10:12:37 /usr/bin/ssh 627264686272 63561 539771 13:08:43 /usr/bin/gcc-4 O749262726272 68561 539771 13:08:43 /usr/lib/gcc/i686-pc-cygwin/4.5.3/cc1 7404646874045241 539771 13:08:46 /usr/bin/ps So, the workaround is to replace $EGREP with egrep in configure; then configure runs successfully. This seems to be some peculiarity of Cygwin's current GCC 4.5.3; neither GCC 3.4.4 in Cygwin 1.7 nor GCC 4.3.4 in Cygwin 1.7 nor GCC 4.3.2 in Cygwin 1.5 exhibit this hang. Csaba Csaba& Marco. Marco: Your try on the XP-SP3 gave no problem. My try on Win 7 Pro hangs, but as Csaba points out: This seems to be some peculiarity of Cygwin's current GCC 4.5.3 Csaba: Replacing $EGREP with egrep in configure did make the difference! Thanx to both of you for excellent help. It wouldn't surprise me at all if the real problem were an earlier fork failure that caused $EGREP to come up blank. Why gcc would then hang on the resulting broken pipeline is a different question, tho... Ryan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Bug in remote gui app execution via ssh
Hi Larry I would appreciate if you can tell if there is any plan to fix this? Regards Arun From: Elr, Arun Sent: Thursday, September 29, 2011 6:24 PM Hi Is there any update on this feature? I downgraded to 5.6p1, still it did not work. I heavily depended on this feature. I tried in XP, Vista and Windows 7. Is there any plan to fix this in upcoming release? Thanks Arun On 4/26/2011 1:52 PM, Harmon Nine wrote: The bug is as follows: A remote system R has Cygwin sshd running from version 5.8p1-1 of openssh. The daemon is running as a service, configured using the directions at http://chinese-watercolor.com/LRP/printsrv/cygwin-sshd.html. Further, the service is running under the "Local System account", and in its properties as a service, "Allow service to interact with desktop" has been checked. A couple things to note here: 1. We don't support other people's recipes for configuring any Cygwin package. Generally when someone reports a problem after using an external source for configuration help, this list suggests looking to the authors of the help for support. 2. Interacting with the desktop through a service is really only supported for XP and older systems. Since most of the other details you report also suggest that you're using XP, I'll surmise you are, though it would be best if you followed the problem reporting guidelines found here - http://cygwin.com/problems.html - just so we don't have to make these kind of guesses. You might try downgrading to 5.6p1 if you have not done so already. -- Larry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: pressing ENTER scrambles scrolled MS-DOS-console
Corinna Vinschen-2 wrote:
>
> On Sep 26 14:18, Paul Maier wrote:
>> Hi,
>>
>> scrolling up the console output to review the console history, then
>> pressing
>> Enter scrambles the console.
>
> That's a long standing behaviour of the Cygwin console emulation.
> I guess it can be fixed, but somebody will have to do it. In the
> meantime, try mintty as terminal.
>
>
> Corinna
>
> --
> Corinna Vinschen Please, send mails regarding Cygwin to
> Cygwin Project Co-Leader cygwin AT cygwin DOT com
> Red Hat
>
>
The problem is as below.
However it needs some thinking, checking and testing, since I have no idea
what that line was needed for.
diff --git i/fhandler_console.cc w/fhandler_console.cc
index 74b5cbd..f29426d 100644
--- i/fhandler_console.cc
+++ w/fhandler_console.cc
@@ -1089,7 +1127,27 @@ fhandler_console::cursor_set (bool rel_to_top, int x,
int y)
dev_state->fillin_info (get_output_handle ());
if (y > dev_state->info.winBottom)
-y = dev_state->info.winBottom;
+y = y;
+// certainly not if doing CR: y = dev_state->info.winBottom;
+// (What purpose did that serve?)
+// There is number of places that assume the following be noop with
respect to cursor's position:
+// cursor_get( &x, &y)
+// cursor_set( x, y)
+// For any of them the assignment that I removed is unacceptable.
+
+// Test case 1: while sleep 0.2; do echo -ne "\r$x"; x=x$x; done
+// Now it works correctly when the user attempts to
scroll the window.
+// Test case 2: sleep 2{scroll up}
+// Now it does not scramble the console even if PS1
(effectively) starts with \n as usual.
+
+
+// There is another problem, not fully manifested in this place:
+// Nothing should depend on the window how it is currently scrolled by
the user.
+// If there is any scrolling sub-window, it should be managed without
reference to winBottom/Top.
+// If we have to place cursor, it should not depend on winBottom/Top.
+// For example srTop / srBottom cannot be computed relative to
winBottom/Top.
+
else if (y < 0)
y = 0;
else if (rel_to_top)
JK
--
View this message in context:
http://old.nabble.com/pressing-ENTER-scrambles-scrolled-MS-DOS-console-tp32539946p32593677.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: error while running shell in emacs
On 9/30/2011 10:27 AM, Markus Hoenicka wrote: CYGWIN_NT-5.1 sbhc123 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin I use some Emacs extensions which execute external programs using (call-process). This used to work on my previous setup, but it fails on my current box. The following command run in Emacs reproduces what seems to be the problem: (call-process "bash" nil '(t t) nil "-ic" "ls -al") bash: Kann die Prozessgruppe des Terminals nicht setzen (-1).: Inappropriate ioctl for device bash: Keine Job Steuerung in dieser Shell. Markus, Why are you calling bash with the -i option in this context? Your first `nil' causes bash's input to come from /dev/null. Does it make sense to have an interactive shell with input coming from /dev/null? If you remove -i and just run (call-process "bash" nil '(t t) nil "-c" "ls -al") , it works fine with both cygwin 1.7.9 and the latest snapshot. Maybe there's still a Cygwin bug here; I tested your original command in Linux, and it worked. But omitting -i might at least be a workaround for you. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: pressing ENTER scrambles scrolled MS-DOS-console
On Tue, Oct 04, 2011 at 06:18:33PM -0700, jan.kolar wrote: > > >Corinna Vinschen-2 wrote: >> >> On Sep 26 14:18, Paul Maier wrote: >>> Hi, >>> >>> scrolling up the console output to review the console history, then >>> pressing >>> Enter scrambles the console. >> >> That's a long standing behaviour of the Cygwin console emulation. >> I guess it can be fixed, but somebody will have to do it. In the >> meantime, try mintty as terminal. >> >> >> Corinna >> >> -- >> Corinna Vinschen Please, send mails regarding Cygwin to >> Cygwin Project Co-Leader cygwin AT cygwin DOT com >> Red Hat >> >> > >The problem is as below. >However it needs some thinking, checking and testing, since I have no idea >what that line was needed for. > >diff --git i/fhandler_console.cc w/fhandler_console.cc >index 74b5cbd..f29426d 100644 >--- i/fhandler_console.cc >+++ w/fhandler_console.cc >@@ -1089,7 +1127,27 @@ fhandler_console::cursor_set (bool rel_to_top, int x, >int y) > > dev_state->fillin_info (get_output_handle ()); > if (y > dev_state->info.winBottom) >-y = dev_state->info.winBottom; >+y = y; Yeah. Yeah. Nice. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: error while running shell in emacs
On 10/4/2011 10:11 PM, Ken Brown wrote: On 9/30/2011 10:27 AM, Markus Hoenicka wrote: CYGWIN_NT-5.1 sbhc123 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin I use some Emacs extensions which execute external programs using (call-process). This used to work on my previous setup, but it fails on my current box. The following command run in Emacs reproduces what seems to be the problem: (call-process "bash" nil '(t t) nil "-ic" "ls -al") bash: Kann die Prozessgruppe des Terminals nicht setzen (-1).: Inappropriate ioctl for device bash: Keine Job Steuerung in dieser Shell. Markus, Why are you calling bash with the -i option in this context? Your first `nil' causes bash's input to come from /dev/null. Does it make sense to have an interactive shell with input coming from /dev/null? If you remove -i and just run (call-process "bash" nil '(t t) nil "-c" "ls -al") , it works fine with both cygwin 1.7.9 and the latest snapshot. Maybe there's still a Cygwin bug here; I tested your original command in Linux, and it worked. But omitting -i might at least be a workaround for you. Replacing -i by -l also works: (call-process "bash" nil '(t t) nil "-lc" "ls -al") -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: docbook-xsl{,-ns}-1.76.1-1
The following packages have been updated for the Cygwin distribution: *** docbook-xsl-1.76.1-1 *** docbook-xsl-ns-1.76.1-1 This package provides the XSL stylesheets for the DocBook XML schemas. This release is an update to the latest upstream version. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: boost-1.46.1-1
The following packages have been updated in the Cygwin distribution: *** libboost1.46.1-1.46.1-1 *** libboost_python1.46.1-1.46.1-1 *** libboost-devel-1.46.1-1 Boost provides free peer-reviewed portable C++ source libraries which are intended to work well with the C++ Standard Library. This release has been built with GCC 4.5 and fixes issues previously reported to the Cygwin lists. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: audiofile-0.3.1-1
The following package has been updated for the Cygwin distribution: *** audiofile-0.3.1-1 *** libaudiofile0-0.3.1-1 *** libaudiofile-devel-0.3.1-1 The Audio File Library provides a uniform programming interface for processing of audio data to and from audio files of many common formats (currently AIFF, AIFF-C, WAVE, NeXT/Sun .snd/.au, IRCAM, AVR, Amiga IFF/8SVX, and NIST SPHERE). This is an update to the latest upstream release. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: e2fsprogs-1.41.14-1
The following packages have been updated for the Cygwin distribution: *** e2fsprogs-1.41.14-1 *** libcom_err2-1.41.14-1 *** libcom_err-devel-1.41.14-1 *** libe2p2-1.41.14-1 *** libe2p-devel-1.41.14-1 *** libext2fs2-1.41.14-1 *** libext2fs-devel-1.41.14-1 *** libss2-1.41.14-1 *** libss-devel-1.41.14-1 e2fsprogs provide utilities and libraries for working with ext2/3/4 filesystems. This is an update to the latest upstream release. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: dbus-1.4.16-1
The following packages have been updated for the Cygwin distribution: *** dbus-1.4.16-1 *** libdbus1_3-1.4.16-1 *** libdbus1-devel-1.4.16-1 D-BUS is a message bus system, a simple way for applications to talk to one another. It supplies both a system daemon (for events such as 'new hardware device added' or 'printer queue changed') and a per-user-login-session daemon (for general IPC needs among user applications). This is an update to the latest upstream release. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: gtypist-2.8.5-1
The following packages have been updated in the Cygwin distribution: *** gtypist-2.8.5-1 GNU Typist is a console-mode typing tutor with several lessons for different keyboards and languages. This is an update to the latest upstream version and is built against ncursesw. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libexif-0.6.20-1
The following packages have been updated in the Cygwin distribution: *** libexif12-0.6.20-1 *** libexif-devel-0.6.20-1 libexif is a C library for reading and writing EXIF metadata from and to image files. This is an update to the latest upstream release, and includes a fix for CVE-2009-3895. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: flexdll-0.26-1
The following package has been updated for the Cygwin distribution: *** flexdll-0.26-1 FlexDLL is an implementation of the dlopen() APIs which creates DLLs whose symbols can be resolved at runtime. It is used by OCaml for dynamic module support. This is an update to the latest upstream release, and includes a patch to handle the -g flag by passing it to gcc. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libproxy-0.4.6-1
The following packages have been updated for the Cygwin distribution: *** libproxy-0.4.6-1 *** libproxy1-0.4.6-1 *** libproxy-devel-0.4.6-1 *** perl-Net-Libproxy-0.4.6-1 *** python-libproxy-0.4.6-1 *** vala-libproxy1.0-0.4.6-1 Libproxy is a library for simplifying and centralizing proxy configuration management. This release adds Perl and Vala bindings. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libssh2-1.2.7-1
The following packages have been updated for the Cygwin distribution: *** libssh2_1-1.2.7-1 *** libssh2-devel-1.2.7-1 libssh2 is a library implementing the SSH2 protocol. This is an update to a more recent upstream version. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libxml2-2.7.8-2
The following packages have been updated for the Cygwin distribution: *** libxml2-2.7.8-2 *** libxml2-devel-2.7.8-2 *** libxml2-doc-2.7.8-2 *** python-libxml2-2.7.8-2 Libxml2 is the XML C library developed for GNOME but widely used outside thereof as well. This is an update to the latest upstream release and includes a patch for CVE-2010-4494. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: perl-Tk-804.029-2
The following package has been updated for the Cygwin distribution: *** perl-Tk-804.029-2 perl-Tk provides an X11 GUI toolkit for Perl programs. This release was rebuilt for the latest libjpeg and libpng libraries. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: netpbm-10.54.4-1
The following package has been updated for the Cygwin distribution: *** netpbm-10.54.4-1 *** libnetpbm10-10.54.4-1 *** libnetpbm-devel-10.54.4-1 Netpbm is a suite of image conversion and manipulation tools, supporting a wide range of formats. This is an update from the upstream Advanced branch, and has been built with GCC 4.5 against jpeg-8. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: python-numpy-1.5.1-1
The following package has been updated for the Cygwin distribution: *** python-numpy-1.5.1-1 The NumPy module contains a powerful N-dimensional array object, sophisticated (broadcasting) functions, tools for integrating C/C++ and Fortran code, and useful linear algebra, Fourier transform, and random number capabilities. It derives from the old Numeric code base and can be used as a replacement for Numeric. It also adds the features introduced by numarray and can be used to replace numarray. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: pcre-8.13-1
The following packages have been updated for the Cygwin distribution: *** pcre-8.13-1 *** libpcre0-8.13-1 *** libpcre-devel-8.13-1 *** libpcrecpp0-8.13-1 *** libpcrecpp-devel-8.13-1 The PCRE library implements regular expression pattern matching using the same syntax and semantics as Perl. This is an update to the latest upstream version, built with GCC 4.5. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
