Doxygen: update request
The version of doxygen included in Cygwin is quite old. Could the doxygen maintainer please consider updating this package soon, thanks. Max.
Re: Doxygen: update request
On Fri, 25 Mar 2005, Max Bowsher wrote: The version of doxygen included in Cygwin is quite old. Could the doxygen maintainer please consider updating this package soon, thanks. Hans Horn offered[*] to maintain a new version of doxygen. Let's give it another week or so, and if Ryunosuke doesn't respond, we'll consider doxygen up for grabs. The decision is ultimately up to the project co-leaders, though. CGF or Corinna? Igor P.S. Corinna, your reply to the below message never got to cygwin-apps. [*] http://cygwin.com/ml/cygwin/2005-03/msg00870.html -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
Re: Do we still have an rxvt maintainer?
Christopher Faylor wrote: ... I don't know if there are any other issues that need to be addressed with rxvt ... There are a few issues that I had already pointed out to Steve O recently: * A new port should be based on the newer rxvt-unicode project. Actually, I have been able to compile the newest rxvt-unicode on cygwin, but unfortunately, it does not work in Unicode mode. I guess the reason is that it strongly (and dogmatically) depends on the locale mechanism for character encoding support. So in order to enable rxvt with Unicode, some sort of locale emulation functionality (like for the non-X mode, or maybe in connection with it, see below) would probably have to be added. * The stand-alone mode (without X windows) is a very strong advantage of the current port of rxvt. It would probably have to be adapted as Steve wrote to me: I don't know how much more of the X library has to be emulated due to unicode, or how much bit-rot has occurred since I last looked at it. * For the stand-alone (non-X) mode, it would be nice to have Windows look-and-feel support. With this option, foreground and background colors should be taken from registry entries /HKEY_CURRENT_USER/Control Panel/Colors/WindowText and /HKEY_CURRENT_USER/Control Panel/Colors/Window, respectively. Unfortunately, for the font setting, this is not as straight-forward as there is no such thing like a default Windows monowidth font and size setting. Considering the effort and problems to be expected, it might be worth considering to add the stand-alone features to xterm rather than to rxvt-unicode. This might turn out easier and rxvt might not be needed anymore then. Kind regards, Thomas Wolff
Re: Do we still have an rxvt maintainer?
On Sat, Mar 26, 2005 at 12:29:58AM +0100, Thomas Wolff wrote: Christopher Faylor wrote: ... I don't know if there are any other issues that need to be addressed with rxvt ... There are a few issues that I had already pointed out to Steve O recently: Steve has just released a new version of rxvt so my concerns have been met. cgf
Re: Doxygen: update request
Max Bowsher wrote: The version of doxygen included in Cygwin is quite old. Could the doxygen maintainer please consider updating this package soon, thanks. FYI, the current doxygen package still uses the old /usr/doc directory. Whoever ends up updating this package should use /usr/share/doc. Brian
Re: gygwin/x keyboard
Silvio A. Vitiello wrote: Although I have a brazilian keyboard and it seems to be properly configurated as you can see in the XWin.log file, I can't get characters like / and the question mark to appear in any of the keys. I've check my local installation and everything with the keyboard configuration seems to be ok. But I'm not sure if the correct key is reported. Please try $ setxkbmap br -model abnt2 $ xev press the key in the event window and report the keypress event. Something like KeyPress event, serial 26, synthetic NO, window 0x242, root 0x65, subw 0x243, time 72994276, (62,62), root:(295,542), state 0x0, keycode 38 (keysym 0x61, a), same_screen YES, XLookupString gives 1 bytes: (61) a XmbLookupString gives 1 bytes: (61) a XFilterEvent returns: False (this is for key a since I don't have the special key on my keyboard) So far XWin expects the keycode to be 211. Maybe this is wrong. bye ago NP: NCOR - An Dunklen Tagen (T.S.M.'s Cracker Beat) -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Fwd: GLXUnsupportedPrivateRequest error with Xwin_gl.exe
Hi Alexander. I made a little progress on this error with the help of the application's authors. By changing the application's method for rendering offscreen buffers from SGIX (hardware acceleration) to GLX (no hardware acceleration) I can avoid the error. Although SGIX works on my Nvidia card with Linux, it does not work for many people, including apparently all ATI users. Information on this application setting is here: http://playerstage.sourceforge.net/doc/Gazebo-manual-0.5-html/gazebo_opengl.html So the problem may be in many X servers besides just Cygwin/X. However, Gazebo now dies immediately after with the cryptic message Bad System Call: $ gazebo.exe example.world *** Gazebo 0.5.1 *** using display [127.0.0.1:0.0] rendering: [GLX offscreen] direct [no] RGBA [8 8 8 8] depth [16] Bad system call The X server's messages during this time are: glWinCreateContext:677: glWinCreateContext glWinCreateContext:696: glWinCreateContext done glWinDestroyContext:411: glWinDestroyContext (ctx 0x0) Can you tell from this whether the problem is in the application or in the rendering? Dave
Re: Cygwin Dlls
Ravi Prasad wrote: I am using cygwin for tinyos. I installed Tinyos1.1.0 in directory C:\tinyos\ and later upgraded to 1.1.7. I have installed arm-gcc from http://www.gnuarm.com/bu-2.15_gcc-3.4.3-c-c++-java_nl-1.12.0_gi-6.1.exe to the directory C:\tinyos\cygwin\arm-gcc\GNUARM Now the problem starts: 1. When I tried to compile a C program by arm-elf-gcc it gave error The procedure entry point__argz_count could not be located in the dynamic linked library cygwin1.dll 2. I replaced C:\tinyos\cygwin\bin\cygwin1.dll by C:\tinyos\cygwin\arm-gcc\GNUARM\bin\cygwin1.dll and also deleted C:\tinyos\cygwin\arm-gcc\GNUARM\bin\cygwin1.dll . Now the program compiled if I compiled it from the directory C:\tinyos\cygwin\arm-gcc\GNUARM\bin. From other directory it gave error The procedure entry point libconv_set_relocation_prefix could not be located in the dynamic linked library cygiconv-2.dll. **At this point the uisp command to uplaod a program started hanging indefinetly. 3. Finally I moved all dll in C:\tinyos\cygwin\arm-gcc\GNUARM\bin\ to C:\tinyos\cygwin\bin\. Now I can compile from any place but uisp still hangs. Can any one please suggest the exact way of using dlls so that I can use the arm-gcc as like avr-gcc in tinyos All of this is off-topic for this list. Cygwin only has the resources to support the Cygwin distribution you get when you use the official setup.exe from cygwin.com. Many third parties package Cygwin in many different ways (often very poorly) and there is no way for this list to be able to support any of them. The error that you're getting (The procedure entry point could not be found...) in indicative of an .exe that was compiled/linked against a version of that DLL that is newer than the version that's being found. It usually happens when you have two copies of the same DLL, one a very much older revision than the other. If the old one is found first in the search order, it will be used first and it will not have the symbols that the .exe requires. Whenever you get that message, find all copies of the named DLL and delete all but the most recent version (you may have to use some tools to find out what version the DLL is.) Then make sure that version is found for all .exes that need it -- usually by putting it in the path. But again... if you didn't install it with setup.exe from cygwin.com, you should be asking elsewhere, such as the place that made whatever distribution you're using. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt problem: Prompt doesn't look very nice
Brian Dessent wrote: Mikael wrote: Thanks Michael. I am using the CVS-version (dated early febraury) of Emacs. I removed the lines I added to my .bashrc and added what you showed to my .emacs. Now my bash shell inside emacs looks nice (and in color), but it's not perfect. Here it is: ]0;c:/cygwin/home/mikael/coding/Win32/show_styles/src [EMAIL PROTECTED] c:/cygwin/home/mikael/coding/Win32/show_styles/src $ The first line doesn't look so good and it's basically repeating what's in the second line (the path). The first line above of PS1 is an escape sequence that tells the terminal to change the window title to the given string. Emacs apparently does not support that escape sequence, so you'll have to modify your prompt. The Cygwin default is PS1='\[\033]0;[EMAIL PROTECTED] \[\033[33m\w\033[0m\]\n$ ' The part that sets the window title is \033]0;\w\007, so you would want PS1='[EMAIL PROTECTED] \[\033[33m\w\033[0m\]\n$ ' Note that '\[' and '\]' are pseudo-escape sequences that tell bash that the enclosed characters represent an escape sequence that the terminal will interpret and not print. They are used so that bash will know to not include those characters in calculating the cursor position. If you want to change the colors, the number N in \033[Nm is what to modify. See google or http://www.dee.ufcg.edu.br/~rrbrandt/tools/ansi.html for more details. Brian Very nice Brian! Now it looks great! Thanks alot everyone for helping me out...now my list of outstanding issues, related or semi-related, to Cygwin got shorter! / M -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Running Cygwin on Windows 2003 Server via remote desktop
Hi, we installed cygwin (version 1.5.13-1) on a Windows Server 2003 (Windows .NET Server Ver 5.2 Build 3790). Locally on the machine everything is running fine. When I remote connect from a Windows XP machine (runnige XP Professional SP2) via Windows Remote Desktop and I start up a bash shell I get the following error message: 6 [main] bash 2644 fork_parent: child 2684 died waiting for longjmp before initialization bash: fork: Bad file descriptor bash-2.05b$ Any help appreciated. Kind regards, Lode cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: autossh-1.3-1
A new version of the autossh package is available in the Cygwin distribution. Changes in version 1.3-1: * New upstream release: - You can now use a remote echo server, instead of a loop of port forwardings, to monitor the ssh connection. See the man page for details. - Several bug fixes. Andrew E. Schulman *** To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt problem: Prompt doesn't look very nice
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Brian Dessent on 3/25/2005 1:00 AM: The first line above of PS1 is an escape sequence that tells the terminal to change the window title to the given string. Emacs apparently does not support that escape sequence, so you'll have to modify your prompt. The Cygwin default is PS1='\[\033]0;[EMAIL PROTECTED] \[\033[33m\w\033[0m\]\n$ ' And this is an evil default in /etc/profile, because it does not correctly delineate printing vs non-printing characters, and hence messes up bash in computing prompt width. Can we please get base-files updated, to actually use \[ and \] only around non-printing characters? Also, bash supports \e for \033, and \a for \007, and uses \$ to print $ for normal users vs # for root (man bash, search for PROMPTING for other cool escape sequences). I would prefer the cygwin default for bash to be: PS1='\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' See google or http://www.dee.ufcg.edu.br/~rrbrandt/tools/ansi.html for more details. That page only covered ANSI sequences, or \e[ It did not cover xterm sequences, or \e]... See http://networking.ringofsaturn.com/Unix/Bash-prompts.php for details on setting the xterm title and icon using \e]0;...\a, \e]1;...\a, and \e]2;...\a. This page also recommends examining $TERM before setting PS1 to use \e]..., since it those escapes work when TERM is cygwin or xterm, but don't work when it is emacs or vt100. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCRBm984KuGfSFAYARAud7AJ9bgnHlTxmLgKIyXq/PRLHZuV89kQCgp3Ro fs9h4RYoIRUes1Ks054C1HE= =ETk0 -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt problem: Prompt doesn't look very nice
Eric Blake wrote: According to Brian Dessent on 3/25/2005 1:00 AM: The first line above of PS1 is an escape sequence that tells the terminal to change the window title to the given string. Emacs apparently does not support that escape sequence, so you'll have to modify your prompt. The Cygwin default is PS1='\[\033]0;[EMAIL PROTECTED] \[\033[33m\w\033[0m\]\n$ ' And this is an evil default in /etc/profile, because it does not correctly delineate printing vs non-printing characters, and hence messes up bash in computing prompt width. Can we please get base-files updated, to actually use \[ and \] only around non-printing characters? Also, bash supports \e for \033, and \a for \007, and uses \$ to print $ for normal users vs # for root (man bash, search for PROMPTING for other cool escape sequences). I would prefer the cygwin default for bash to be: PS1='\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' Well, I'm hoping I can find the time to propose a bash update this weekend to the official packages. I finally found a reference to a nice recipe for building a package, as the Cygwin package web page is a little overwhelming. But via the FAQ, there's a pointer to a very concise posting by Charles Wilson on how to do it, and I'm going to try and get to this weekend. If it is under control of the bash package, then I will add this in. But it may not be. See google or http://www.dee.ufcg.edu.br/~rrbrandt/tools/ansi.html for more details. That page only covered ANSI sequences, or \e[ It did not cover xterm sequences, or \e]... See http://networking.ringofsaturn.com/Unix/Bash-prompts.php for details on setting the xterm title and icon using \e]0;...\a, \e]1;...\a, and \e]2;...\a. This page also recommends examining $TERM before setting PS1 to use \e]..., since it those escapes work when TERM is cygwin or xterm, but don't work when it is emacs or vt100. Someone either posted here, or I found a link to, a nice .bashrc. In it, there was: # Setup color variables BLACK=\[\033[0;30m\] DGRAY=\[\033[1;30m\] RED=\[\033[0;31m\] LRED=\[\033[1;31m\] GREEN=\[\033[0;32m\] LGREEN=\[\033[1;32m\] BROWN=\[\033[0;33m\] YELLOW=\[\033[1;33m\] BLUE=\[\033[0;34m\] LBLUE=\[\033[1;34m\] PURPLE=\[\033[0;35m\] LPURPLE=\[\033[1;35m\] CYAN=\[\033[0;36m\] LCYAN=\[\033[1;36m\] LGRAY=\[\033[0;37m\] WHITE=\[\033[1;37m\] NEUTRAL=\[\033[0m\] export BLACK DGRAY RED LRED GREEN LGREEN BROWN YELLOW BLUE export LBLUE PURPLE LPURPLE CYAN LCYAN LGRAY WHITE NEUTRAL which is kinda nice. So that means my PS1 is: export PS1=*** [EMAIL PROTECTED] *** $YELLOW\w$NEUTRAL ***\n\r$NEUTRAL There's a bunch of nice .bashrc examples, as a quick Google scan found. -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Amazing Developments http://www.buddydog.org I feel like a fugitive from the law of averages. - William H. Mauldin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Postgres 7.2
there id the option of just downloading the srcs from www.postgresql.org for 7.2.X and building them yourself. reid -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: recv and errno during a connection reset/closed by peer
On Thu, 24 Mar 2005, Brian Dessent wrote: Peter Stephens wrote: When in non-blocking mode I thought I would be able to get a return from recv of '-1' and then check errno, but it never seems to be anything but '11', or EAGAIN. This seems to be true whether I MSG_PEEK or not. I have included my code below. The intention is that for recv returns greater than zero, there is a message and I should process it and get ready for the next one. For recv returns of '0' I should do nothing and for recv returns of '-1' I should handle per errno. Seems easy enough, but no matter what I have tried I can only get a recv return of EAGAIN. ... rcv_length = recv(threadarg-new_fd,NULL,NULL,MSG_PEEK); Try passing a buffer and length to recv(). The Cygwin code does not attempt to do anything with the socket if buf = NULL and len = 0. (You can look at it yourself, file winsup/cygwin/net.cc, functions cygwin_recv() and cygwin_recvfrom().) How would you ever expect recv() to return 0 when you don't give it a buffer to put the data into? AIUI, recv with MSG_PEEK is supposed to return the length of the waiting data without putting anything in the buffer. The POSIX standard doesn't say anything about the behavior of recv() when buf=NULL so what you're trying to do must be some nonstandard quirk of other systems' libc. The SUSv6 page on recv also doesn't mention the possibility of the buffer being NULL. I'd suggest to the OP to pass in a dummy 1-character buffer to recv() with MSG_PEEK, e.g., char c; ... rcv_length = recv(threadarg-new_fd,c,1,MSG_PEEK); HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt problem: Prompt doesn't look very nice
On Fri, 25 Mar 2005, Jonathan Arnold wrote: Eric Blake wrote: And this is an evil default in /etc/profile, [snip] I would prefer the cygwin default for bash to be: PS1='\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' Well, I'm hoping I can find the time to propose a bash update this weekend to the official packages. ... If it is under control of the bash package, then I will add this in. But it may not be. [snip] /etc/profile is a user-controlled. The default /etc/profile is in /etc/defaults/etc/profile, and, as cygcheck -f /etc/defaults/etc/profile shows, this is distributed as part of the base-files package. cygcheck -l base-files should list all of the files in base-files. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt problem: Prompt doesn't look very nice [FAQ alert]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jonathan Arnold on 3/25/2005 7:16 AM: I would prefer the cygwin default for bash to be: PS1='\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' Well, I'm hoping I can find the time to propose a bash update this weekend to the official packages. I finally found a reference to a nice recipe for building a package, as the Cygwin package web page is a little overwhelming. But via the FAQ, there's a pointer to a very concise posting by Charles Wilson on how to do it, and I'm going to try and get to this weekend. If it is under control of the bash package, then I will add this in. But it may not be. Nope, /etc/profile is under the control of base-files, not bash, so you don't have to worry about it when trying to package bash. And the people on cygwin-apps will help you with suggestions if you need them for packaging bash (thanks for volunteering by the way) - I still remember the learning curve to get diffstat prepared as the first package I maintain. Also, check out the generic build script, it automates several of the steps in Chuck's email as listed in the FAQ (can we get FAQ 88 updated to add a link to the latest version of the GBS?). It is covered in more detail near the end of http://cygwin.com/setup.html. Bash is particularly annoying to build, since Chet Ramey does not publish new tarballs with the 16 official patches against 3.0 already applied, and since he does not make his development repository public. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCRCFS84KuGfSFAYARAoLRAKDNKl+PB06e46Wd7DVZHh0YTLhiOQCgu/zj 5+5FhCAVjNxpydG43hMNnmY= =JXVO -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
base-files patch
Considering the recent thread on rxvt and PS1, I propose the following patches to /etc/default/etc/profile. In addition to fixing the default PS1 for bash to correctly delineate non-printing characters, it fixes the following additional bugs: When using case, you do not need to quote a command substitution; this is particularly important since `` is non-portable, just use case `` instead. Sorting is not necessarily strictly alphanumeric in other locales (not that cygwin has good locale support, but still...). Also, `info coreutils dircolors' recently changed to recommend eval `dircolors ...`, due to the security hole mentioned in http://lists.gnu.org/archive/html/bug-coreutils/2004-12/msg00058.html. -- Eric Blake base-files.diff Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: base-files patch
On Fri, Mar 25, 2005 at 04:37:26PM +, Eric Blake wrote: Considering the recent thread on rxvt and PS1, I propose the following patches to /etc/default/etc/profile. In addition to fixing the default PS1 for bash to correctly delineate non-printing characters, it fixes the following additional bugs: When using case, you do not need to quote a command substitution; this is particularly important since `` is non-portable, just use case `` instead. Sorting is not necessarily strictly alphanumeric in other locales (not that cygwin has good locale support, but still...). Also, `info coreutils dircolors' recently changed to recommend eval `dircolors ...`, due to the security hole mentioned in http://lists.gnu.org/archive/html/bug-coreutils/2004-12/msg00058.html. I'm not sure I understand the removal of `` for portability in the same patch which changes A=foo export A to export A=foo I've never seen a shell that didn't understand `` but I have seen shells which didn't understand export A=foo. Personally, I wish we wouldn't play any prompt games in the system profiles. I'd rather just either just have the standard prompt that the shell uses or my own customized version rather than assuming that we all know what the cygwin users want for a prompt. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: base-files patch
On Fri, Mar 25, 2005 at 04:37:26PM +, Eric Blake wrote: I'm not sure I understand the removal of `` for portability in the same patch which changes A=foo export A to export A=foo Yes, export A=foo is nonportable (/bin/sh, which is ash, does not like it, even though POSIX requires it), but since that line is inside the case that is doing shell-specific settings of PS1, it is guaranteed to only be executed by bash, which handles it. By the way, is there a newer version of ash that is more POSIX-compliant? The current version is more than a year old. I've never seen a shell that didn't understand `` but I have seen shells which didn't understand export A=foo. It is not `` alone, but `` that has problems. Some shells require the nested to be escaped with \, others don't, since some shells treat ` as an error, and others can't parse `\\`. But since case does not do word splitting or filename expansion on its argument, and since `` is a quoting pattern and therefore forms the argument to case, (even if inside the `` contains spaces, or the command output has spaces), case `echo $0` is portable while case `echo $0` and case `echo \$0\` are not. See the autoconf manual for more details. Personally, I wish we wouldn't play any prompt games in the system profiles. I'd rather just either just have the standard prompt that the shell uses or my own customized version rather than assuming that we all know what the cygwin users want for a prompt. True enough - how about having /etc/default/etc/profile always set PS1=$ , then have /etc/profile/etc/skel/.bash_profile (and friends) set the colorized version that cygwin users have always had as their default. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: base-files patch
On Fri, Mar 25, 2005 at 05:14:49PM +, Eric Blake wrote: On Fri, Mar 25, 2005 at 04:37:26PM +, Eric Blake wrote: I'm not sure I understand the removal of `` for portability in the same patch which changes A=foo export A to export A=foo Yes, export A=foo is nonportable (/bin/sh, which is ash, does not like it, even though POSIX requires it), but since that line is inside the case that is doing shell-specific settings of PS1, it is guaranteed to only be executed by bash, which handles it. By the way, is there a newer version of ash that is more POSIX-compliant? The current version is more than a year old. ash is not supposed to be POSIX compliant. Personally, I wish we wouldn't play any prompt games in the system profiles. I'd rather just either just have the standard prompt that the shell uses or my own customized version rather than assuming that we all know what the cygwin users want for a prompt. True enough - how about having /etc/default/etc/profile always set PS1=$ , then have /etc/profile/etc/skel/.bash_profile (and friends) set the colorized version that cygwin users have always had as their default. That sounds closer to right to me, but I'd be happy with the stuff in /etc/profile not playing any games with the prompt. In fact, why should /etc/default/etc/profile set the prompt to anything? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
test -f occasionally fails on sym links (keychain related)
Hi All... While doing some testing with keychain and the snapshots while getting ready to release a keychain service package (still working on it)...I noticed the following Sometimes doing a [ -f foo ]; will show a false true while the symlink is being created. You can see this by opening two bash shells and executing while :; do echo $$ foo.lnk; rm foo.lnk; done in the first one and while :; do if [ -f foo ]; then echo here; else echo there; fi; done in the second one. Thanks, ...Karl -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: test -f occasionally fails on sym links (keychain related)
Hi All... Cut and paste error...I wanted to say execute while :; do rm foo; ln -s $$ foo; done in the first one. The line I used was part of furhter debugging work. From: Karl M Subject: test -f occasionally fails on sym links (keychain related) Date: Fri, 25 Mar 2005 09:37:30 -0800 Hi All... While doing some testing with keychain and the snapshots while getting ready to release a keychain service package (still working on it)...I noticed the following Sometimes doing a [ -f foo ]; will show a false true while the symlink is being created. You can see this by opening two bash shells and executing while :; do echo $$ foo.lnk; rm foo.lnk; done in the first one and while :; do if [ -f foo ]; then echo here; else echo there; fi; done in the second one. Thanks, ...Karl -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: base-files patch
On Fri, 25 Mar 2005, Eric Blake wrote (snipped): In addition to fixing the default PS1 for bash to correctly delineate non-printing characters, One thing that bash does is *deliberately* compute the line break one character *before* the edge of the screen. You can see what happens when it is fooled into thinking the prompt is 1 character shorter than it actually is (e.g., export PS1='$\[ \]' and type a long command). it fixes the following additional bugs: When using case, you do not need to quote a command substitution; this is particularly important since `` is non-portable, just use case `` instead. Most shells understand `` (particularly, all official shells on Cygwin, which is what's important). In fact, in this particular case, it's probably better to use `` instead of ``, IMO. Sorting is not necessarily strictly alphanumeric in other locales (not that cygwin has good locale support, but still...). Good point. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
No /dev/parport0
Hi, I´m trying the whole time to get my /dev directory work. There is no /dev/parport0, so I tried to install one with mknod /dev/parport0 c 99 0 but it doesn´t help. I need it for programming my ATmega16 microcontroller with uisp. I always get /dev/parport0: No such device or address Failed to open ppdev. Please help me. greetings -- Handyrechnung zu hoch? Tipp: SMS und MMS mit GMX Seien Sie so frei: Alle Infos unter http://www.gmx.net/de/go/freesms -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: base-files patch
On Fri, 25 Mar 2005, Eric Blake wrote (snipped): Most shells understand `` (particularly, all official shells on Cygwin, which is what's important). True enough, and I concede that POSIX requires it to work. In fact, in this particular case, it's probably better to use `` instead of ``, IMO. No, `echo $0|tr ...` does the wrong thing if $0 is two spaces/sh (it passes just one space to tr, instead of two), while `echo $0|tr ...` works correctly. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: base-files patch
On Fri, 25 Mar 2005, Eric Blake wrote: In fact, in this particular case, it's probably better to use `` instead of ``, IMO. No, `echo $0|tr ...` does the wrong thing if $0 is two spaces/sh (it passes just one space to tr, instead of two), while `echo $0|tr ...` works correctly. In *this particular* case, the value will be compared with a constant set of space-free values, so the number of spaces doesn't matter -- it still won't match any values from that set... :-) In general you're correct -- quoting is a way of preserving spaces, among other things. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: base-files patch
On Fri, 25 Mar 2005, Eric Blake wrote: No, `echo $0|tr ...` does the wrong thing if $0 is two spaces/sh (it passes just one space to tr, instead of two), while `echo $0|tr ...` works correctly. In *this particular* case, the value will be compared with a constant set of space-free values, so the number of spaces doesn't matter -- it still won't match any values from that set... :-) In general you're correct -- quoting is a way of preserving spaces, among other things. True enough. And that points out another bug - echo $0 may fail if $0 starts with -, it should be echo -- $0. Isn't portable shell programming fun? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
package for netstat?
Pardon if this is mis-posted. I'm a long-time cygwin user and fan, but not very good at usenet. Which package do I get to get 'netstat'? I found this (slightly silly) thread: http://sourceware.org/ml/cygwin/2004-06/msg00959.html titled yes -- netstat (was Re: is there any command to see all the current tcp socket?), so it sounds like Cygwin does have netstat, but a search from this page: http://cygwin.com/packages found 0 matches, and a quick scan of the package names found no likely suspects. What am I doing wrong? much thanks, Jonathan This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: package for netstat?
At 04:31 PM 3/25/2005, you wrote: Pardon if this is mis-posted. I'm a long-time cygwin user and fan, but not very good at usenet. Which package do I get to get 'netstat'? I found this (slightly silly) thread: http://sourceware.org/ml/cygwin/2004-06/msg00959.html titled yes -- netstat (was Re: is there any command to see all the current tcp socket?), so it sounds like Cygwin does have netstat, but a search from this page: http://cygwin.com/packages found 0 matches, and a quick scan of the package names found no likely suspects. What am I doing wrong? Ignoring Windows? I typed which netstat at my bash prompt just now and was greeted with /WINDOWS/system32/netstat. YMMV, depending on the version of Windows you're running and your mount points. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: package for netstat?
At 04:31 PM 3/25/2005, you wrote: Pardon if this is mis-posted. I'm a long-time cygwin user and fan, but not very good at usenet. Which package do I get to get 'netstat'? I found this (slightly silly) thread: http://sourceware.org/ml/cygwin/2004-06/msg00959.html titled yes -- netstat (was Re: is there any command to see all the current tcp socket?), so it sounds like Cygwin does have netstat, but a search from this page: http://cygwin.com/packages found 0 matches, and a quick scan of the package names found no likely suspects. What am I doing wrong? Ignoring Windows? I typed which netstat at my bash prompt just now and was greeted with /WINDOWS/system32/netstat. YMMV, depending on the version of Windows you're running and your mount points. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 Actually, yes, I do tend to ignore windows when possible. It keeps me happy. ;- I've got the system32/netstat in my path currently, too. I guess I was working off some bad past experiences with Windows 'find' vs. GNU 'find' - I use GNU if it's available. But if other cygwinners use Win netstat, I'll use it too. Thanks. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: recv and errno during a connection reset/closed by peer
I boiled this down to nothing(see below). I must be missing something
basic. I tried the suggestions made so far and it never gets to:
printf( ERRNO %i\n, errno);
I would expect that on a disconnect (I use putty in telnet or raw mode) it
would return -1 whether it is doing MSG_PEEK or an actual retrieval. No
luck.
#include errno.h
#include stdio.h
#include unistd.h
#include sys/socket.h
#include netinet/in.h
#include arpa/inet.h
int main(int argc, char **argv)
{
int lfd=-1, afd=-1, temp=0;
char buf[20];
lfd = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);
if (-1 == lfd)
printf(Error at socket(): %i\n, errno);
// joris' suggestion
#if 1
temp = 1;
setsockopt(lfd, SOL_SOCKET, SO_KEEPALIVE,(char *)temp, sizeof(temp)) ;
#endif
sockaddr_in svc;
svc.sin_family = AF_INET;
svc.sin_addr.s_addr = inet_addr(192.168.1.245);
svc.sin_port = htons(27015);
if (-1 == bind(lfd, (struct sockaddr *) svc, sizeof(svc)))
printf(bind() failed.\n);
if (-1 == listen(lfd, 1 ))
printf(Error listening on socket.\n);
printf(Waiting for client to connect...\n);
while( -1 == afd ){
afd = accept( lfd, NULL, NULL );
}
printf(Client connected.\n);
int ret_val = 0;
do{
ret_val = recv(afd, buf, 20, MSG_PEEK);
if(0 ret_val)
printf( ERRNO %i\n, errno);
else if(ret_val 0){
ret_val = recv(afd, buf, 20, 0);
buf[ret_val]='\0';
printf((%i) %s, ret_val, buf);
}
usleep(250);
}while(ret_val=0);
return 0;
}
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Errors in #include files when compiling a Legacy C++ Application
Hi! Our legacy C++ application was written on SGI IRIX using older compiler features. Last year, we ported it to SuSe Linux (both 8.2 and 9.1). We have had a few challenges, but nothing big. Recently, I have been asked to get the application to run on MS-Windows, with very little time. I looked around, and have found 2 possible solutions Cygwin and VmWare. I installed Cygwin yesterday with no errors. I moved my source onto the MS-Windows PC, and tried to compile. At first, several include files could not be found (we had similar problems in the Linux port). I found the files, and changed my makefile. Then, there were a lot of errors, but they were in the include files. I started to look inside the include files, but it was confusing. I am including the beginning of the source file that won't compile, a file with the error messages, my makefile, and an included sub make file (make.source). The makefile uses an environment variable (OSTYPE) that is set by SuSe to linux. I have manually set this variable before calling make. I am confused, because the two flavors of SuSe use g++ 3.2 and 3.3.4, and there wasn't a big problem going from 3.2 to 3.3.4. Since Cygwin uses g++ 3.3.3, I would think that the code that works on 3.3.4 (SuSe 9.1) would be a no brainer. I think there must be something simple that I have done wrong. I have looked at your FAQ, and made several searches on the mailing lists, and have not found this problem, so I hope you don't mind helping me. If there is any other info that would help in diagnosing the problem, please let me know. (Is there a way to send you a list of packages that I installed, perhaps something is missing or I installed conflicting items). I will monitor the mailing list for replies. Thanks! Brian K. Whatcott Senior Software and Systems Engineer Millennium Engineering Integration (719) 264-4310, FAX (719) 264-4318 (719) 331-5100 (Cell) [EMAIL PROTECTED] BMC2_Delete_Msg.cc Description: Binary data $ make mv: cannot stat `A_Linux/libshared.a': No such file or directory mv: cannot stat `A_Linux/*.d': No such file or directory mv: cannot stat `A_Linux/*.o': No such file or directory make: [get] Error 1 (ignored) g++ -fpermissive -w -g -I../lib -I/usr/X11R6/include -I../shared -I/usr/include/machine -DOS_IS_LINUX -c BMC2_Delete_Msg.cc In file included from /usr/include/c++/3.3.3/cwchar:51, from /usr/include/c++/3.3.3/bits/fpos.h:45, from /usr/include/c++/3.3.3/iosfwd:49, from /usr/include/c++/3.3.3/ios:44, from /usr/include/c++/3.3.3/ostream:45, from /usr/include/c++/3.3.3/iostream:45, from /usr/include/c++/3.3.3/backward/iostream.h:32, from /usr/include/c++/3.3.3/backward/iomanip.h:32, from BMC2_Delete_Msg.cc:35: /usr/include/c++/3.3.3/ctime:68: error: `tm' not declared /usr/include/c++/3.3.3/ctime:70: error: `clock' not declared /usr/include/c++/3.3.3/ctime:71: error: `difftime' not declared /usr/include/c++/3.3.3/ctime:72: error: `mktime' not declared /usr/include/c++/3.3.3/ctime:73: error: `time' not declared /usr/include/c++/3.3.3/ctime:74: error: `asctime' not declared /usr/include/c++/3.3.3/ctime:75: error: `ctime' not declared /usr/include/c++/3.3.3/ctime:76: error: `gmtime' not declared /usr/include/c++/3.3.3/ctime:77: error: `localtime' not declared /usr/include/c++/3.3.3/ctime:78: error: `strftime' not declared In file included from /usr/include/c++/3.3.3/bits/stl_algobase.h:67, from /usr/include/c++/3.3.3/memory:54, from /usr/include/c++/3.3.3/string:48, from /usr/include/c++/3.3.3/bits/locale_classes.h:47, from /usr/include/c++/3.3.3/bits/ios_base.h:47, from /usr/include/c++/3.3.3/ios:49, from /usr/include/c++/3.3.3/ostream:45, from /usr/include/c++/3.3.3/iostream:45, from /usr/include/c++/3.3.3/backward/iostream.h:32, from /usr/include/c++/3.3.3/backward/iomanip.h:32, from BMC2_Delete_Msg.cc:35: /usr/include/c++/3.3.3/cstdlib:86: error: `div_t' not declared /usr/include/c++/3.3.3/cstdlib:87: error: `ldiv_t' not declared /usr/include/c++/3.3.3/cstdlib:89: error: `abort' not declared /usr/include/c++/3.3.3/cstdlib:90: error: `abs' not declared /usr/include/c++/3.3.3/cstdlib:91: error: `atexit' not declared /usr/include/c++/3.3.3/cstdlib:92: error: `atof' not declared /usr/include/c++/3.3.3/cstdlib:93: error: `atoi' not declared /usr/include/c++/3.3.3/cstdlib:94: error: `atol' not declared /usr/include/c++/3.3.3/cstdlib:95: error: `bsearch' not declared /usr/include/c++/3.3.3/cstdlib:96: error: `calloc' not declared /usr/include/c++/3.3.3/cstdlib:97: error: `div' not declared /usr/include/c++/3.3.3/cstdlib:98: error: `exit' not declared /usr/include/c++/3.3.3/cstdlib:99: error: `free' not declared /usr/include/c++/3.3.3/cstdlib:100:
cygwin1.dll
cygwin-1.5.13-1 give me cygwin1.dll plz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Errors in #include files when compiling a Legacy C++ Application
At 03:19 PM 3/25/2005, Brian K. Whatcott wrote: I am confused, because the two flavors of SuSe use g++ 3.2 and 3.3.4, and there wasn't a big problem going from 3.2 to 3.3.4. Since Cygwin uses g++ 3.3.3, I would think that the code that works on 3.3.4 (SuSe 9.1) would be a no brainer. I think there must be something simple that I have done wrong. I have looked at your FAQ, and made several searches on the mailing lists, and have not found this problem, so I hope you don't mind helping me. If there is any other info that would help in diagnosing the problem, please let me know. (Is there a way to send you a list of packages that I installed, perhaps something is missing or I installed conflicting items). Yes, the FAQ should tell you about running cygcheck, and how the list prefers to see the results. It does look like your build is not finding the standard C headers. Did you install gcc as well as g++ ? Tim Prince -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin1.dll
Âèòàëèé Ñòàñþê wrote: cygwin-1.5.13-1 give me cygwin1.dll plz This list only supports installations of Cygwin done with the setup.exe installer from cygwin.com. If you used that you'd have cygwin1.dll already, so it's likely that you're using someone else's packaged binaries. Ask them. If you just want the DLL it's available from any of the cygwin mirrors in the cygwin package, or in snapshot form on cygwin.com. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rxvt problem: Prompt doesn't look very nice [FAQ alert]
On Fri, 25 Mar 2005 07:33:54 -0700, Eric Blake wrote: Also, check out the generic build script, it automates several of the steps in Chuck's email as listed in the FAQ (can we get FAQ 88 updated to add a link to the latest version of the GBS?). It is covered in more detail near the end of http://cygwin.com/setup.html. Updated. http://www.cygwin.com/faq/faq_3.html#SEC88 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Using ssmtp to send email as a different user (-f doesn't seem to be working)
thomas revell wrote: Apologies if I'm missing something really obvious here, but I can't seem to get ssmtp to use the -f option, to change the address to send from. My situation is like this: From a glance at the code without any real testing, it looks like it changes the From: header correctly, but doesn't give the right MAIL FROM: in the smtp communication. Try downloading the source, changing the line in ssmtp.c smtp_write(sock, MAIL FROM:%s, uad); to smtp_write(sock, MAIL FROM:%s, from); and see if that does the trick. Note that this isn't really a Cygwin issue, you should probably submit further questions upstream at http://packages.debian.org/testing/mail/ssmtp Someday I'll try to update the Cygwin package, by the way; but I've been very busy, so if anyone else is keen to maintain ssmtp, they are welcome to it. Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Errors in #include files when compiling a Legacy C++ Application
Tim, I did install the gcc C compiler. What switches need to be set with cygcheck? I'll run it and forward the results. Brian K. Whatcott Senior Software and Systems Engineer Millennium Engineering Integration (719) 264-4310, FAX (719) 264-4318 (719) 331-5100 (Cell) [EMAIL PROTECTED] -Original Message- From: Tim Prince [mailto:[EMAIL PROTECTED] Sent: Friday, March 25, 2005 6:34 PM To: Brian K. Whatcott; cygwin@cygwin.com Subject: Re: Errors in #include files when compiling a Legacy C++ Application At 03:19 PM 3/25/2005, Brian K. Whatcott wrote: I am confused, because the two flavors of SuSe use g++ 3.2 and 3.3.4, and there wasn't a big problem going from 3.2 to 3.3.4. Since Cygwin uses g++ 3.3.3, I would think that the code that works on 3.3.4 (SuSe 9.1) would be a no brainer. I think there must be something simple that I have done wrong. I have looked at your FAQ, and made several searches on the mailing lists, and have not found this problem, so I hope you don't mind helping me. If there is any other info that would help in diagnosing the problem, please let me know. (Is there a way to send you a list of packages that I installed, perhaps something is missing or I installed conflicting items). Yes, the FAQ should tell you about running cygcheck, and how the list prefers to see the results. It does look like your build is not finding the standard C headers. Did you install gcc as well as g++ ? Tim Prince -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Updated: autossh-1.3-1
A new version of the autossh package is available in the Cygwin distribution. Changes in version 1.3-1: * New upstream release: - You can now use a remote echo server, instead of a loop of port forwardings, to monitor the ssh connection. See the man page for details. - Several bug fixes. Andrew E. Schulman *** To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
