Re: Updated: lilypond-2.4.2-1
On Dec 16 06:55, Bertalan Fodor wrote: http://www.inf.bme.hu/~berti/lilypond/release/lilypond/setup.hint http://www.inf.bme.hu/~berti/lilypond/release/lilypond/lilypond-2.4.2-1.tar.bz2 http://www.inf.bme.hu/~berti/lilypond/release/lilypond/lilypond-2.4.2-1-src.tar.bz2 http://www.inf.bme.hu/~berti/lilypond/release/lilypond/lilypond-doc/setup.hint http://www.inf.bme.hu/~berti/lilypond/release/lilypond/lilypond-doc/lilypond-doc-2.4.2-1.tar.bz2 Uploaded. I've removed 2.2.2 and kept 2.2.5. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: directx-headers
On Thu, Dec 09, 2004 at 03:29:28PM +0100, Peter Ekberg wrote: Background: I miss DirectX header files. Slightly patched headers from the Wine project works fine for me, so I submitted those some time ago. However, they were rejected due to licensing issues (Wine is LGPL, w32api is Public Domain). I then asked nicely if the Wine developers would be so kind as to release the headers under a less restirictive license. Not surprisingly, I didn't receive responses from all contributors so that was a dead end. I sent your query to mingw-dvlpr. Here was the response: On Thu, Dec 09, 2004 at 08:17:03PM -0500, Earnie Boyd wrote: From Christopher Faylor: Is there really no hope of getting these into w32api? Uhm, directx lives already in w32api. See w32api/include/directx and w32api/lib/directx. Patches to those should be submitted to http://sourceforge.net/tracker/?group_id=2435atid=302435. So, a cygwin package would be inappropriate. cgf
RE: directx-headers
cgf wrote: On Thu, Dec 09, 2004 at 03:29:28PM +0100, Peter Ekberg wrote: Background: I miss DirectX header files. Slightly patched headers from the Wine project works fine for me, so I submitted those some time ago. However, they were rejected due to licensing issues (Wine is LGPL, w32api is Public Domain). I then asked nicely if the Wine developers would be so kind as to release the headers under a less restirictive license. Not surprisingly, I didn't receive responses from all contributors so that was a dead end. I sent your query to mingw-dvlpr. Here was the response: On Thu, Dec 09, 2004 at 08:17:03PM -0500, Earnie Boyd wrote: From Christopher Faylor: Is there really no hope of getting these into w32api? Uhm, directx lives already in w32api. See w32api/include/directx and w32api/lib/directx. Patches to those should be submitted to http://sourceforge.net/tracker/?group_id=2435atid=302435. Tried that, no go. These files are, as stated, LGPL. They did therefore not fit the bill. Looking through w32api/include/directx reveals that the files provided by my package are nowhere in sight. Also, I see no future in further discussions of these headers with the MinGW folks, they will simply not accept them into w32api if they are LGPL. So, a cygwin package would be inappropriate. Yes, I realize that there will be a clash if this package is added to the cygwin dist and if w32api in the future includes some version of ddraw.h etc. But there seems to be no work in the latter direction... Some evidence of this inactivity can be found in this note in the w32api TODO: Low priority RASAPI MAPI directx (what about existing ports?) Nothing is happening, low priority, patches not accepted and a suggestion from someone (I think it was Danny Smith) that perhaps a new package was needed led me to create just that, a new package. And to propose it for inclusion. I need working DirectX headers in Cygwin so that I can propose a libggi package for inclusion. But if you don't want the headers, you'll get no DirectX backend in libggi, if/when libggi is added to Cygwin. That is a pity since the DirectX backend is working like a charm on Cygwin. Would the package be less controversial if the headers were installed somewhere else? I can then point to them with the ggi configure scripts. But that would be sad, since ggi would then not work out of the box, as is the case if these headers are in the right place. Another option is to include package local copies of them in the (future) ggi package, but that seems very unsatisfactory as well. This approach also poses the same problem for ggi as it does for w32api, as ggi then must be relicensed under LGPL, which is something I want to avoid. Is there some way to get DirectX headers into Cygwin without adding them to the w32api package? Or should I just stop trying and go away? Cheers, Peter
Re: setup.exe sucks
You do have to have something early on that bootstraps what you need, like setup.exe does now, but it could always install the cygwin first before it does anything. Yes, once we had yum, we could almost have the unattended install working. Of course, you couldn't use yum to install python or cygwin, as it stands right now. So this idea just came to me and seems brilliant right now, but may not be: what about making setup.exe do nothing except install a bootstrap Cygwin including python and rpm database. After that yum or apt-rpm or connectiva's thing would to the rest. I see the advantages being: throw out the most confusing parts of setup, but keep around a lot of bootstrap work. There would not need to be any changes to the basic Cygwin install instructions (the Use setup.exe mantra). The existing problems with using Unix-based tools on Windows like replacing files would remain, though.
Problems with ssh and X
First, please accept my apologies for send my message to the wrong list. Thanks to Igor for suggesting the FAQ list. I have now tried: ssh -Y -l username remotemachine I now get the error message: connect 212.159.18.214 port 6000 Connection refused. (the IP address is the static IP address provided by my ISP) There is still nothing in the log of my Netgear NG834G firewall or the ZoneAlarm log. I shutdown Zone alarm and the same thing happened. Any thoughts or suggestions would be gratefully received. Many thanks, Chris. Dr Christian Hicks Senior Lecturer, Director of Postgraduate Training, School of Mechanical Systems Engineering, Stephenson Building, University of Newcastle upon Tyne, NE1 7RU. Phone: +44 191 222 6238 Mobile 0796 398 9449 Fax: + 44 191 222 8600 Homepage: http://www.staff.ncl.ac.uk/chris.hicks
Re: Problems with ssh and X
On Thu, 16 Dec 2004, Dr Christian Hicks wrote: First, please accept my apologies for send my message to the wrong list. Thanks to Igor for suggesting the FAQ list. I have now tried: ssh -Y -l username remotemachine I now get the error message: connect 212.159.18.214 port 6000 Connection refused. (the IP address is the static IP address provided by my ISP) There is still nothing in the log of my Netgear NG834G firewall or the ZoneAlarm log. I shutdown Zone alarm and the same thing happened. Which unix you're connecting too? Gentoo does set the DISPLAY variable to the remote ip and breaks X11 Forwarding. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
default font size
Hello, the default font size within the xterm, that comes up on the default installation of Cygwin is tiny. I would generally prefer a larger size. How do I increase the font size? (there is no XF86Config file any more). - Josef
Re: default font size
On Thu, 16 Dec 2004, Josef Dalcolmo wrote: Hello, the default font size within the xterm, that comes up on the default installation of Cygwin is tiny. I would generally prefer a larger size. How do I increase the font size? (there is no XF86Config file any more). The default font size for xterm is normally the alias fixed. That can be set by a resource value (see the manpage). The available fonts can be listed with xlsfonts. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
Re: default font size
On Thu, 16 Dec 2004, Josef Dalcolmo wrote: Hello, the default font size within the xterm, that comes up on the default installation of Cygwin is tiny. I would generally prefer a larger size. How do I increase the font size? (there is no XF86Config file any more). select another font xterm -fn 7x13 or xterm -fn 12x24 fontnames can be listed with xlsfonts or xterm -fa Courier -fs 12 fontnames can be listed with fs-list adding -dpi 100 to the XWin commandline may help too (and installing the xorg-x11-f100 package) bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Problems with ssh and X
Hi Christian, If I recall my past life properly, -Y (X11ForwardingTrusted) does not enable -X (X11Forwarding)... Try this instead: ssh -X -Y -l username remotemachine Also, when you get bored of using command-line options, read 'man ssh_config' G'day, JST On Thu, Dec 16, 2004 at 09:49:49AM +, Dr Christian Hicks wrote: First, please accept my apologies for send my message to the wrong list. Thanks to Igor for suggesting the FAQ list. I have now tried: ssh -Y -l username remotemachine I now get the error message: connect 212.159.18.214 port 6000 Connection refused. (the IP address is the static IP address provided by my ISP) There is still nothing in the log of my Netgear NG834G firewall or the ZoneAlarm log. I shutdown Zone alarm and the same thing happened. Any thoughts or suggestions would be gratefully received. Many thanks, Chris. Dr Christian Hicks Senior Lecturer, Director of Postgraduate Training, School of Mechanical Systems Engineering, Stephenson Building, University of Newcastle upon Tyne, NE1 7RU. Phone: +44 191 222 6238 Mobile 0796 398 9449 Fax: + 44 191 222 8600 Homepage: http://www.staff.ncl.ac.uk/chris.hicks
Re: cygwin
On Thu, Dec 16, 2004 at 10:26:29AM -0500, Andrew Schulman wrote: please add me to mailing list.. I am having nothing but problems with this The ability to add yourself to the mailing list is well-tested. You can think of it as an entrance examination if you want. No one is going to do this for you. As an additional exam, we should add the ability to write an intelligent subject line. A subject of cygwin or cygwin problem on a post to any cygwin-related mailing list should result in instant ejection from the list. Good point. I do reject some subjects like that in the main cygwin list but I hadn't done so here. I have now, though. However, if people think that's too harsh, I'll remove that restriction. I always wonder if people who post subjects like that also go into the bank, hand their checks to the teller and say Bank!. Or if they go to the auto shop to get their car fixed and open the discussion by pointing and saying Car! cgf
Re: cygwin, and comment on rejection
Christopher Faylor [EMAIL PROTECTED] writes: Good point. I do reject some subjects like that in the main cygwin list but I hadn't done so here. I have now, though. However, if people think that's too harsh, I'll remove that restriction. A person's inability to articulate their problem should not deprive them of help. Yes, I feel this is too harsh. Sarir A kindly tongue is the lodestone of the hearts of men.
Re: cygwin
please add me to mailing list.. I am having nothing but problems with this The ability to add yourself to the mailing list is well-tested. You can think of it as an entrance examination if you want. No one is going to do this for you. As an additional exam, we should add the ability to write an intelligent subject line. A subject of cygwin or cygwin problem on a post to any cygwin-related mailing list should result in instant ejection from the list. Good point. I do reject some subjects like that in the main cygwin list but I hadn't done so here. I have now, though. However, if people think that's too harsh, I'll remove that restriction. No, I wasn't serious about ejecting subscribers, or even individual postings. Just making my little point. -- To reply by email, replace deadspam.com by alumni.utexas.net
Re: cygwin, and comment on rejection
On Thu, Dec 16, 2004 at 09:36:37AM -0700, Sarir Khamsi wrote: Christopher Faylor [EMAIL PROTECTED] writes: Good point. I do reject some subjects like that in the main cygwin list but I hadn't done so here. I have now, though. However, if people think that's too harsh, I'll remove that restriction. A person's inability to articulate their problem should not deprive them of help. Yes, I feel this is too harsh. I thought I'd get that response but it sort of misses the point, IMO. This doesn't stop people cold. It just prevents their first attempt sending email to the mailing list from being a clueless one. This is exactly what the suggestions at http://cygwin.com/problems.html were intended to stop. cgf
Problems with ssh and X
The remote machine is running SunOs 5.7 on a sparc SUNW,Ultra-4. Best regards, Chris. Dr Christian Hicks Senior Lecturer, Director of Postgraduate Training, School of Mechanical Systems Engineering, Stephenson Building, University of Newcastle upon Tyne, NE1 7RU. Phone: +44 191 222 6238 Mobile 0796 398 9449 Fax: + 44 191 222 8600 Homepage: http://www.staff.ncl.ac.uk/chris.hicks
Re: Problems with ssh and X
On Thu, 16 Dec 2004, Dr Christian Hicks wrote: The remote machine is running SunOs 5.7 on a sparc SUNW,Ultra-4. When doing X11Forwarding the DISPLAY variable should point to localhost:10.0 (or higher numbers) or is unset if X11Forwarding does not work. In your case it is set to remotehost:0.0 which is wrong. Find the place where the DISPLAY variable is set and prevent it. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: cygwin
On Wed, Dec 15, 2004 at 10:09:32PM -0700, MP wrote: please add me to mailing list.. I am having nothing but problems with this The ability to add yourself to the mailing list is well-tested. You can think of it as an entrance examination if you want. No one is going to do this for you.
Re: cygwin
please add me to mailing list.. I am having nothing but problems with this The ability to add yourself to the mailing list is well-tested. You can think of it as an entrance examination if you want. No one is going to do this for you. As an additional exam, we should add the ability to write an intelligent subject line. A subject of cygwin or cygwin problem on a post to any cygwin-related mailing list should result in instant ejection from the list. -- To reply by email, replace deadspam.com by alumni.utexas.net
Re: cygwin, and comment on rejection
On Thu, Dec 16, 2004 at 12:06:18PM -0500, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 09:36:37AM -0700, Sarir Khamsi wrote: Christopher Faylor [EMAIL PROTECTED] writes: Good point. I do reject some subjects like that in the main cygwin list but I hadn't done so here. I have now, though. However, if people think that's too harsh, I'll remove that restriction. A person's inability to articulate their problem should not deprive them of help. Yes, I feel this is too harsh. I thought I'd get that response but it sort of misses the point, IMO. This doesn't stop people cold. It just prevents their first attempt sending email to the mailing list from being a clueless one. This is exactly what the suggestions at http://cygwin.com/problems.html were intended to stop. But, regardless, I asked for feedback and the first two responses were don't do it so I've removed this. cgf
Problems with ssh and X
Problem sorted. Thanks Jean-Sebastien. Chris. Dr Christian Hicks Senior Lecturer, Director of Postgraduate Training, School of Mechanical Systems Engineering, Stephenson Building, University of Newcastle upon Tyne, NE1 7RU. Phone: +44 191 222 6238 Mobile 0796 398 9449 Fax: + 44 191 222 8600 Homepage: http://www.staff.ncl.ac.uk/chris.hicks
src/winsup/cygwin ChangeLog fhandler_console.cc
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2004-12-16 13:19:09 Modified files: winsup/cygwin : ChangeLog fhandler_console.cc Log message: * fhandler_console.cc (get_win32_attr): Avoid inappropriate intensity interchanging that used to render reverse output unreadable when non-reversed text is bright. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.2619r2=1.2620 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_console.cc.diff?cvsroot=srcr1=1.133r2=1.134
Re: [Patch] bug # 514 (cygwin console handling) - update
On Dec 14 06:02, Thomas Wolff wrote: This is an update of my trivial patch that fixes http://sourceware.org/bugzilla/show_bug.cgi?id=514 I guess the patch is pretty much ok and I'm inclined to let it pass under the trivial patch rule... iff you change it so that the #ifdef goes away. Which alternative seems more appropriate resp. which one results in the more readable output? It's the one we should choose (since any choice will result in complains anyway). OK, I kept the alternative that was selected by #ifdef before. It's the more consistent one anyway. And please shorten the ChangeLog entry to about one sentence. OK. Well done, just the layout of the ChangeLog needed some reworking (the whole entry should be tabbified). Thanks for the patch, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: Patch to allow trailing dots on managed mounts
On Thu, Dec 16, 2004 at 09:55:48AM -0500, Pierre A. Humblet wrote: Here is an untested patch. I hope Mark can test it (on managed and unmanaged mounts, including basenames consisting entirely of dots and spaces) and possibly make adjustments, without having to file the paperwork. Pierre * path.cc (path_conv::check): Do not strip trailing dots and spaces. * fhandler.cc (fhandler_base::open): Strip trailing dots and spaces. Is it correct to assume that only fhandler_base::open cares about trailing dots? cgf
Re: Patch to allow trailing dots on managed mounts
On Thu, Dec 16, 2004 at 07:59:05AM -0700, Mark Paulus wrote: Other than the way I proposed, I'm not sure how to fix this, since the issue seems to be that conv_to_win32_path() needs to get the trailing dot in it's input argument, and check() is stripping it out. The only way I can see to fix this behaviour is to leave the trailing dots in the string. Maybe conv_to_win32_path needs to deal/strip with the trailing dots, depending upon whether it's a managed filesystem or not? Yes, *of course* there either has to be special accommodations for managed mounts or you have to show that your change will not affect normal cygwin operation for non-managed mounts. Your patch just essentially nuked most of cygwin's handling of trailing dots. Unless you can prove that the previous code was misguided in the general case of non-managed mounts, doing this is obviously the wrong solution. cgf
Re: Patch to allow trailing dots on managed mounts
On Dec 16 10:00, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 09:55:48AM -0500, Pierre A. Humblet wrote: Here is an untested patch. I hope Mark can test it (on managed and unmanaged mounts, including basenames consisting entirely of dots and spaces) and possibly make adjustments, without having to file the paperwork. Pierre * path.cc (path_conv::check): Do not strip trailing dots and spaces. * fhandler.cc (fhandler_base::open): Strip trailing dots and spaces. Is it correct to assume that only fhandler_base::open cares about trailing dots? So far, yes. But somehow moving this code into open() looks a bit like a step backwards to me. The general direction is to do more stuff using NT functions, isn't it? So in the long run we would get the same problem in other code paths as well. Since the mount code is called from path_conv anyway, wouldn't it be better to pass the information managed mount or not up to path_conv? Actually, the information should be don't mangle pathnames further or some such. This would allow a new mount point type along the lines of NTFS/Posix, which would allow to use unchanged pathnames in mounted NTFS directories. This would not only affect trailing dots and spaces, also aux.c comes to mind. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: Patch to allow trailing dots on managed mounts
On Dec 16 10:57, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 04:53:39PM +0100, Corinna Vinschen wrote: Since the mount code is called from path_conv anyway, wouldn't it be better to pass the information managed mount or not up to path_conv? How about just doing the pathname munging in `conv_to_win32_path' if/when it's needed? Erm... I'm not quite sure, but didn't the remove trailing dots and spaces code start there and has been moved to path_conv by Pierre to circumvent some problem? I recall only very vaguely right now. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: Patch to allow trailing dots on managed mounts
On Thu, Dec 16, 2004 at 05:03:22PM +0100, Corinna Vinschen wrote: On Dec 16 10:57, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 04:53:39PM +0100, Corinna Vinschen wrote: Since the mount code is called from path_conv anyway, wouldn't it be better to pass the information managed mount or not up to path_conv? How about just doing the pathname munging in `conv_to_win32_path' if/when it's needed? Erm... I'm not quite sure, but didn't the remove trailing dots and spaces code start there and has been moved to path_conv by Pierre to circumvent some problem? I recall only very vaguely right now. One problem that it would circumvent is that currently, if you do this: ls /bin.. You'll get a listing of the bin directory. If you move the code to conv_to_win32_path that may not be as easy to get right. cgf
Re: Patch to allow trailing dots on managed mounts
On Thu, Dec 16, 2004 at 09:23:56AM -0700, Mark Paulus wrote: Which is why I did what I did. If you look, my patch allows for checking to see if . was entered as an argument, and throws the exception if it was. THEN, if that is not the case, it passes the FULL name to conv_to_win32_path to allow for proper demangling rules. What you did was clear. It was only a two line change, after all. Unfortunately, you seemed to assume that all the work that cygwin went through to figure out that trailing dot stuff was just useless and that the rest of cygwin will work just fine with files containing trailing dots regardless of whether the file is managed or not. That is not the case. The point of the section of code that you patched was not just to throw the exception it was to strip off the trailing dots. cgf
Another attempt to patch path.cc for trailing dots
* path.cc (path_conv::check): retain trailing dots and spaces * path.cc (mount_item::build_win32): strip trailing dots and spaces for unmanaged filesystems path.cc.patch Description: Binary data
Re: [Patch] cygcheck: eprintf + display_error: Do /something/.
Op Thu, 16 Dec 2004 21:02:05 -0500 schreef Christopher Faylor
in [EMAIL PROTECTED]:
: On Fri, Dec 17, 2004 at 02:04:40AM +0100, Buzz wrote:
: Here is another attempt at making eprintf a usable/used function in
: cygcheck. It this time just flushes stdout and stderr before/after
: output on stderr, when both (stdout and stderr) are ttys.
[...]
: I'm still not sure what you're hoping to accomplish with this. I haven't
: seen any problems with flushing in cygcheck and I wouldn't expect any
: since the flushing should be automatic if stdout is a tty.
I seem to be making a mess here... The point is to have the error-messages
appear at about the appropriate point in the output, not bunched together
near the beginning or end. Here is another attempt. This time, do the
flushing when both are ttys or neither are.
(If you know of a simple test to find out if the two are identical,
that would be preferable. No test at all is also an option...)
ChangeLog-entry:
2004-12-17 Bas van Gompel [EMAIL PROTECTED]
* cygcheck.cc (eprintf): Flush stdout before, and stderr after output,
when stdout and stderr both refer to tty's, or both don't.
(display_error): Use eprintf.
--- src/winsup/utils/cygcheck.cc18 Nov 2004 05:20:23 - 1.64
+++ src/winsup/utils/cygcheck.cc17 Dec 2004 02:45:43 -
@@ -9,6 +9,7 @@
details. */
#include stdio.h
+#include unistd.h
#include stdlib.h
#include string.h
#include sys/time.h
@@ -102,9 +103,16 @@ void
eprintf (const char *format, ...)
{
va_list ap;
+
+ if (isatty (fileno (stdout)) == isatty (fileno (stderr)))
+fflush (stdout);
+
va_start (ap, format);
vfprintf (stderr, format, ap);
va_end (ap);
+
+ if (isatty (fileno (stdout)) == isatty (fileno (stderr)))
+fflush (stderr);
}
/*
@@ -114,10 +122,10 @@ static int
display_error (const char *name, bool show_error = true, bool print_failed =
true)
{
if (show_error)
-fprintf (stderr, cygcheck: %s%s: %lu\n, name,
+eprintf (cygcheck: %s%s: %lu\n, name,
print_failed ? failed : , GetLastError ());
else
-fprintf (stderr, cygcheck: %s%s\n, name,
+eprintf (cygcheck: %s%s\n, name,
print_failed ? failed : );
return 1;
}
L8r,
Buzz.
--
) | | ---/ ---/ Yes, this | This message consists of true | I do not
-- | | // really is | and false bits entirely.| mail for
) | | //a 72 by 4 +---+ any1 but
-- \--| /--- /--- .sigfile. | |perl -pe s.u(z)\1.as.| me. 4^re
Re: [Patch] cygcheck: eprintf + display_error: Do /something/.
On Fri, Dec 17, 2004 at 03:51:47AM +0100, Bas van Gompel wrote: Op Thu, 16 Dec 2004 21:02:05 -0500 schreef Christopher Faylor in [EMAIL PROTECTED]: : On Fri, Dec 17, 2004 at 02:04:40AM +0100, Buzz wrote: : Here is another attempt at making eprintf a usable/used function in : cygcheck. It this time just flushes stdout and stderr before/after : output on stderr, when both (stdout and stderr) are ttys. [...] : I'm still not sure what you're hoping to accomplish with this. I haven't : seen any problems with flushing in cygcheck and I wouldn't expect any : since the flushing should be automatic if stdout is a tty. I seem to be making a mess here... The point is to have the error-messages appear at about the appropriate point in the output, not bunched together near the beginning or end. Here is another attempt. This time, do the flushing when both are ttys or neither are. I still don't see the point. There is no need to do explicit flushes if both stdout and stderr are ttys. In the case of stdout the flush should occur every time there's a newline. In the case of stderr, the flush should happen after every write. cgf
Re: Another attempt to patch path.cc for trailing dots
On Thu, Dec 16, 2004 at 04:48:52PM -0700, Mark Paulus wrote: * path.cc (path_conv::check): retain trailing dots and spaces * path.cc (mount_item::build_win32): strip trailing dots and spaces for unmanaged filesystems Thanks for the effort. You're working on some of the most complicated code in cygwin. However, I'd prefer not to add extra loops at this point, if I can help it, or add extra burden to the common case of non-managed mode for the the uncommon case of managed mode. I have things set up in my sandbox so that the tail information is passed to the appropriate routine which will recreate trailing dots if needed. I'm just running cygwin through the test suite to make sure I didn't make any egregious mistakes. cgf
Re: Patch to allow trailing dots on managed mounts
At 11:06 AM 12/16/2004 -0500, Christopher Faylor wrote:
On Thu, Dec 16, 2004 at 05:03:22PM +0100, Corinna Vinschen wrote:
On Dec 16 10:57, Christopher Faylor wrote:
On Thu, Dec 16, 2004 at 04:53:39PM +0100, Corinna Vinschen wrote:
Since the mount code is called from path_conv anyway, wouldn't it be
better to pass the information managed mount or not up to path_conv?
How about just doing the pathname munging in `conv_to_win32_path' if/when
it's needed?
Erm... I'm not quite sure, but didn't the remove trailing dots and spaces
code start there and has been moved to path_conv by Pierre to circumvent
some problem? I recall only very vaguely right now.
One problem that it would circumvent is that currently, if you do this:
ls /bin..
You'll get a listing of the bin directory. If you move the code to
conv_to_win32_path that may not be as easy to get right.
The initial trailing dots and space test was put in normalize_posix path,
not conv_to_win32_path. That was done to fix a side effect of
NtCreateFile, without considering all the many issues.
Putting it in conv_to_win32_path will forbid files ending in .lnk
or .exe but that are called without these suffixes.
This should not happen:
~: ln -s /etc 'abc . .'
~: ls abc*
ls: abc . .: No such file or directory
~: rm 'abc . ..lnk'
rm: remove `abc . ..lnk'? y
It's also called during each iteration of the check() loop, which is
unnecessary.
Putting it in mount_item::build_win32 (as Mark as just done) suffers
from the same problems, and misses a number of cases where it's needed.
The attached patch puts the test at the end of check(), and only if the
file doesn't start with //./
I can't test for the moment due to the state of my sandbox.
I believe that the tests for in normalize_{posix,win32}_path are now
irrelevant, but I'd like Corinna to confirm (she introduced the test
on 2003-10-25).
Due to those tests, suffixes consisting entirely of dots are still
disallowed.
Also, for my info, what is the unc\ in
!strncasematch (this-path + 4, unc\\, 4)))
around line 868? I have never seen that documented.
Pierre
* path.cc (path_conv::check): Check the output Win32 path for trailing
spaces and dots, not the input path.
Index: path.cc
===
RCS file: /cvs/src/src/winsup/cygwin/path.cc,v
retrieving revision 1.326
diff -u -p -r1.326 path.cc
--- path.cc 3 Dec 2004 02:00:37 - 1.326
+++ path.cc 17 Dec 2004 02:58:57 -
@@ -546,25 +546,12 @@ path_conv::check (const char *src, unsig
/* Detect if the user was looking for a directory. We have to strip
the
trailing slash initially while trying to add extensions but take it
into account during processing */
- if (tail path_copy + 1)
+ if (tail path_copy + 1 isslash (tail[-1]))
{
- if (isslash (tail[-1]))
- {
- need_directory = 1;
- tail--;
- }
- /* Remove trailing dots and spaces which are ignored by Win32
functions but
-not by native NT functions. */
- while (tail[-1] == '.' || tail[-1] == ' ')
- tail--;
- if (tail path_copy + 1 isslash (tail[-1]))
- {
- error = ENOENT;
- return;
- }
+ need_directory = 1;
+ *--tail = '\0';
}
path_end = tail;
- *tail = '\0';
/* Scan path_copy from right to left looking either for a symlink
or an actual existing file. If an existing file is found, just
@@ -835,6 +822,18 @@ out:
if (dev.devn == FH_FS)
{
+ if (strncmp (path, .\\, 4))
+{
+ /* Windows ignores trailing dots and spaces */
+ char *tail = strchr (path, '\0');
+ while (tail[-1] == ' ' || tail[-1] == '.')
+tail[-1] = '\0';
+ if (tail[-1] == '\\')
+{
+ error = ENOENT;
+ return;
+}
+}
if (fs.update (path))
{
debug_printf (this-path(%s), has_acls(%d), path, fs.has_acls ());
Re: Patch to allow trailing dots on managed mounts
On Thu, Dec 16, 2004 at 10:26:27PM -0500, Christopher Faylor wrote: I don't see how it could be correct for the slash checking code not to be in the loop. Won't this cause a problem if you've done Ah, nevermind. I see that your patch handles that. cgf
Re: [Patch] cygcheck: eprintf + display_error: Do /something/.
Op Thu, 16 Dec 2004 21:56:07 -0500 schreef Christopher Faylor
in [EMAIL PROTECTED]:
: On Fri, Dec 17, 2004 at 03:51:47AM +0100, Bas van Gompel wrote:
[...]
: I seem to be making a mess here... The point is to have the error-messages
: appear at about the appropriate point in the output, not bunched together
: near the beginning or end. Here is another attempt. This time, do the
: flushing when both are ttys or neither are.
:
: I still don't see the point. There is no need to do explicit flushes if
: both stdout and stderr are ttys. In the case of stdout the flush should
: occur every time there's a newline. In the case of stderr, the flush
: should happen after every write.
So, the test can exclude the case where both are ttys. (Did I say I was
making a mess?) Here is a sample of ``cygcheck -s -v -r cygcheck.out
21'', when some (network) drives can not be read:
...
zip 2.3-6
zlib1.2.2-1
zsh 4.2.0-2
Use -h to see help about each section
cygcheck: dump_sysinfo: GetVolumeInformation() failed: 5
cygcheck: dump_sysinfo: GetVolumeInformation() failed: 5
Another version of the ChangeLog-entry/patch:
2004-12-17 Bas van Gompel [EMAIL PROTECTED]
* cygcheck.cc (eprintf): Flush stdout before, and stderr after output,
when stdout and stderr both don't refer to ttys.
(display_error): Use eprintf.
--- src/winsup/utils/cygcheck.cc18 Nov 2004 05:20:23 - 1.64
+++ src/winsup/utils/cygcheck.cc17 Dec 2004 02:45:43 -
@@ -9,6 +9,7 @@
details. */
#include stdio.h
+#include unistd.h
#include stdlib.h
#include string.h
#include sys/time.h
@@ -102,9 +103,16 @@ void
eprintf (const char *format, ...)
{
va_list ap;
+
+ if (!isatty (fileno (stdout)) !isatty (fileno (stderr)))
+fflush (stdout);
+
va_start (ap, format);
vfprintf (stderr, format, ap);
va_end (ap);
+
+ if (!isatty (fileno (stdout)) !isatty (fileno (stderr)))
+fflush (stderr);
}
/*
@@ -114,10 +122,10 @@ static int
display_error (const char *name, bool show_error = true, bool print_failed =
true)
{
if (show_error)
-fprintf (stderr, cygcheck: %s%s: %lu\n, name,
+eprintf (cygcheck: %s%s: %lu\n, name,
print_failed ? failed : , GetLastError ());
else
-fprintf (stderr, cygcheck: %s%s\n, name,
+eprintf (cygcheck: %s%s\n, name,
print_failed ? failed : );
return 1;
}
L8r,
Buzz.
--
) | | ---/ ---/ Yes, this | This message consists of true | I do not
-- | | // really is | and false bits entirely.| mail for
) | | //a 72 by 4 +---+ any1 but
-- \--| /--- /--- .sigfile. | |perl -pe s.u(z)\1.as.| me. 4^re
Re: Patch to allow trailing dots on managed mounts
At 10:27 PM 12/16/2004 -0500, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 10:26:27PM -0500, Christopher Faylor wrote: I don't see how it could be correct for the slash checking code not to be in the loop. Won't this cause a problem if you've done Ah, nevermind. I see that your patch handles that. OK. The key point in my patch is that it's the output Win32 path that must be checked, not the input path. The reason we don't care about the input path is that check() only makes simple Windows calls. They handle the tails as they judge best (and that worked OK until NtCreateFile was introduced), we don't have to do anything special. We want to fix the output path (only for real disk files that are not escaped with //./) so that: 1) NtCreateFile mimics the Windows rules 2) the path hash is invariant to the path tail 3) chdir something/... is prevented Pierre
Re: Patch to allow trailing dots on managed mounts
On Thu, Dec 16, 2004 at 10:43:47PM -0500, Pierre A. Humblet wrote: At 10:27 PM 12/16/2004 -0500, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 10:26:27PM -0500, Christopher Faylor wrote: I don't see how it could be correct for the slash checking code not to be in the loop. Won't this cause a problem if you've done Ah, nevermind. I see that your patch handles that. OK. The key point in my patch is that it's the output Win32 path that must be checked, not the input path. How can that be? As I mentioned previously, if you don't perform the fixups prior to inspecting the mount table then ls /bin.. won't work. cgf
Re: [Patch] cygcheck: eprintf + display_error: Do /something/.
On Fri, Dec 17, 2004 at 04:33:10AM +0100, Bas van Gompel wrote: Op Thu, 16 Dec 2004 21:56:07 -0500 schreef Christopher Faylor in [EMAIL PROTECTED]: : On Fri, Dec 17, 2004 at 03:51:47AM +0100, Bas van Gompel wrote: [...] : I seem to be making a mess here... The point is to have the error-messages : appear at about the appropriate point in the output, not bunched together : near the beginning or end. Here is another attempt. This time, do the : flushing when both are ttys or neither are. : : I still don't see the point. There is no need to do explicit flushes if : both stdout and stderr are ttys. In the case of stdout the flush should : occur every time there's a newline. In the case of stderr, the flush : should happen after every write. So, the test can exclude the case where both are ttys. (Did I say I was making a mess?) Here is a sample of ``cygcheck -s -v -r cygcheck.out 21'', when some (network) drives can not be read: ... zip 2.3-6 zlib1.2.2-1 zsh 4.2.0-2 Use -h to see help about each section cygcheck: dump_sysinfo: GetVolumeInformation() failed: 5 cygcheck: dump_sysinfo: GetVolumeInformation() failed: 5 Another version of the ChangeLog-entry/patch: 2004-12-17 Bas van Gompel [EMAIL PROTECTED] * cygcheck.cc (eprintf): Flush stdout before, and stderr after output, when stdout and stderr both don't refer to ttys. (display_error): Use eprintf. Ok. I don't see any reason to check for ttyness, then. If this is an issue then lets just flush stdout prior to doing anything with stderr. Flushing stderr should always be a no-op. Or, we could just make stdout always unbuffered. cgf
Re: Patch to allow trailing dots on managed mounts
Here is an untested patch.
I hope Mark can test it (on managed and unmanaged mounts,
including basenames consisting entirely of dots and spaces)
and possibly make adjustments, without having to file the
paperwork.
Pierre
* path.cc (path_conv::check): Do not strip trailing dots and spaces.
* fhandler.cc (fhandler_base::open): Strip trailing dots and spaces.
Index: path.cc
===
RCS file: /cvs/src/src/winsup/cygwin/path.cc,v
retrieving revision 1.326
diff -u -p -r1.326 path.cc
--- path.cc 3 Dec 2004 02:00:37 - 1.326
+++ path.cc 16 Dec 2004 14:42:58 -
@@ -546,25 +546,12 @@ path_conv::check (const char *src, unsig
/* Detect if the user was looking for a directory. We have to strip the
trailing slash initially while trying to add extensions but take it
into account during processing */
- if (tail path_copy + 1)
+ if (tail path_copy + 1 isslash (tail[-1]))
{
- if (isslash (tail[-1]))
- {
- need_directory = 1;
- tail--;
- }
- /* Remove trailing dots and spaces which are ignored by Win32
functions but
-not by native NT functions. */
- while (tail[-1] == '.' || tail[-1] == ' ')
- tail--;
- if (tail path_copy + 1 isslash (tail[-1]))
- {
- error = ENOENT;
- return;
- }
+ need_directory = 1;
+ *--tail = '\0';
}
path_end = tail;
- *tail = '\0';
/* Scan path_copy from right to left looking either for a symlink
or an actual existing file. If an existing file is found, just
Index: fhandler.cc
===
RCS file: /cvs/src/src/winsup/cygwin/fhandler.cc,v
retrieving revision 1.207
diff -u -p -r1.207 fhandler.cc
--- fhandler.cc 20 Nov 2004 23:42:36 - 1.207
+++ fhandler.cc 16 Dec 2004 14:43:51 -
@@ -537,6 +537,17 @@ fhandler_base::open (int flags, mode_t m
UNICODE_STRING upath = {0, sizeof (wpath), wpath};
pc.get_nt_native_path (upath);
+ /* Remove trailing dots and spaces which are ignored by Win32 functions but
+ not by native NT functions. */
+ WCHAR *tail = upath.Buffer + upath.Length;
+ while (tail[-1] == '.' || tail[-1] == ' ')
+tail--;
+ if (tail[-1] == '\\')
+{
+ set_errno (ENOENT);
+ return 0;
+}
+
if (RtlIsDosDeviceName_U (upath.Buffer))
return fhandler_base::open_9x (flags, mode);
Re: Patch to allow trailing dots on managed mounts
On Thu, Dec 16, 2004 at 04:53:39PM +0100, Corinna Vinschen wrote: On Dec 16 10:00, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 09:55:48AM -0500, Pierre A. Humblet wrote: Here is an untested patch. I hope Mark can test it (on managed and unmanaged mounts, including basenames consisting entirely of dots and spaces) and possibly make adjustments, without having to file the paperwork. Pierre * path.cc (path_conv::check): Do not strip trailing dots and spaces. * fhandler.cc (fhandler_base::open): Strip trailing dots and spaces. Is it correct to assume that only fhandler_base::open cares about trailing dots? So far, yes. But somehow moving this code into open() looks a bit like a step backwards to me. The general direction is to do more stuff using NT functions, isn't it? So in the long run we would get the same problem in other code paths as well. That was my thought as well. Since the mount code is called from path_conv anyway, wouldn't it be better to pass the information managed mount or not up to path_conv? How about just doing the pathname munging in `conv_to_win32_path' if/when it's needed? cgf
Re: Patch to allow trailing dots on managed mounts
On Thu, Dec 16, 2004 at 11:06:07AM -0500, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 05:03:22PM +0100, Corinna Vinschen wrote: On Dec 16 10:57, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 04:53:39PM +0100, Corinna Vinschen wrote: Since the mount code is called from path_conv anyway, wouldn't it be better to pass the information managed mount or not up to path_conv? How about just doing the pathname munging in `conv_to_win32_path' if/when it's needed? Erm... I'm not quite sure, but didn't the remove trailing dots and spaces code start there and has been moved to path_conv by Pierre to circumvent some problem? I recall only very vaguely right now. One problem that it would circumvent is that currently, if you do this: ls /bin.. You'll get a listing of the bin directory. If you move the code to conv_to_win32_path that may not be as easy to get right. That's the problem with somehow getting the information back to path_conv::check, too, I think. It's a chicken/egg situation. You need to regularize the path name before looking through the mount table to find out if the file is controlled by a managed mount. cgf
Re: Patch to allow trailing dots on managed mounts
cgf wrote: Is it correct to assume that only fhandler_base::open cares about trailing dots? Good point. This bring back memories. The initial motivation was to fix problems introduced by the use of NtCreateFile http://www.cygwin.com/ml/cygwin/2004-04/msg01250.html and there were successive changes 2004-04-30 Corinna Vinschen [EMAIL PROTECTED] * path.cc (normalize_posix_path): Remove trailing dots and spaces. http://cygwin.com/ml/cygwin-patches/2004-q2/msg00053.html 2004-05-06 Pierre Humblet [EMAIL PROTECTED] * path.cc (path_conv::check): Strip trailing dots and spaces and return error if the final component had only dots and spaces. (normalize_posix_path): Revert 2004-04-30. However, as a side effect, checking the tail in :check also cleanly fixed longstanding dormant issues with the path hash and with chroot (at least). So checking the tail in fhandler_base::open() is too late. It should be done before exiting :check(), perhaps only in the case where the path refers to a disk file, preferably with little processing overhead. Although it wasn't done before 2004/04, we should also make sure (I have no free time for the moment) that nothing goes wrong inside :check() while we lookup symbolic links. Pierre
Re: Patch to allow trailing dots on managed mounts
On Thu, 16 Dec 2004 11:37:32 -0500, Christopher Faylor wrote: On Thu, Dec 16, 2004 at 09:23:56AM -0700, Mark Paulus wrote: Which is why I did what I did. If you look, my patch allows for checking to see if . was entered as an argument, and throws the exception if it was. THEN, if that is not the case, it passes the FULL name to conv_to_win32_path to allow for proper demangling rules. What you did was clear. It was only a two line change, after all. Unfortunately, you seemed to assume that all the work that cygwin went through to figure out that trailing dot stuff was just useless and that the rest of cygwin will work just fine with files containing trailing dots regardless of whether the file is managed or not. That is not the case. The point of the section of code that you patched was not just to throw the exception it was to strip off the trailing dots. Then I guess I'll have to wait for a fix to come down, since the amount of work to fix this will probably be more than I can put in without a waiver. cgf
Re: c++ code executes very slowly - sjlj EH to blame?
Larry Hall wrote: True but the way I read that conversation was that DWARF2 EH worked if callbacks weren't used or would work with callbacks so long as -fexceptions was used. Maybe I read that incorrectly though. That is correct. Maybe we can convince ReactOs to release a win32api built with -fexceptions and DW2 unwind tables. My goal is to build gcc/g++ that use Dwarf2 EH. A compiler with working EH will be able to run my test program without aborting. So far I have built several versions of gcc, all of which have the abort() EH, which is equivalent to having _no_ EH in practical terms. Maybe Danny Smith has some thoughts about this, since he has apparently been at least partially successful in getting DWARF2 EH to work on cygwin. Yes, I expect he'll chime in. ding-dong-lurker.wav FWIW, Dwarf2 unwind worked without any complaints (that I am aware of) from cygwin users in a GCC-3.2 (cygming special) release. One of the two DW2 bug reports by mngw users (stdcall vs fomit-frame-pointer vs -mno-accumulate-outgoing-args) has been fixed in GCC. The other (callbacks that throw exceptions from a foreign function) has not A 4.0 patch to enable DW2 unwind is at: http://gcc.gnu.org/ml/gcc-patches/2004-11/msg01989.html GCC is now in Stage 3 of development cycle (regression fixes only) I plan to submit a revised patch when 4.0 branches. So maybe 4.1 Another question for anyone at all: any ideas why sjlj is so crap-tastically slow on cygwin? I can't believe that sjlj EH has nearly such a huge hit on other targets. If sjlj it is the sole perpetrator of the slowdown, then it is doing a very very effective job of slowing things down. Depends. If you're app makes only limited use of exceptions, sjlj can be more efficient. However, since operator new can throw exceptions, the cost of sjlj can add up very quickly. I think the default use of the simple new-based allocator in gcc-3.4.x libstdc++ (rather than a more efficient pool allocator) also compounds the problem. I wouldn't blame everything on sjlj. C programs that do any file I/O are also crap-tastically slow on windows compared to glibc targets. Danny -- 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/
Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
For the last 6 hrs I have been fighting with latex2html and cygwin to get latex2html to work, but I give up. Has anyone got latex2html to work on cygwin? This is what I have 1. Latex cygwin FULL installation. $ uname -a CYGWIN_NT-5.1 me 1.5.12(0.116/4/2) 2004-11-10 08:34 i686 unknown unknown Cygwin cygwins install just fine, all working well. 2. Get the netpbm programs, installed no problem 3. downloaded latex2html: latex2html-2002-2-1.tar latest version of late2html. untar, In the latex2html directory there is a file called L2hos.pm , Edit this file by replacing $^O with 'unix' 4. added everything to path, and for latex2html did ./configure, make, make install all went with NO errors !! 5. But now everytime I try the late2html command on a .tex file, I get the error $ latex2html foo.tex Fatal (use l2hconf): l2hconf.pm did not return a true value at (eval 7) line 2. BEGIN failed--compilation aborted at (eval 7) line 2. I look at the file l2hconf.pm, and I see this as first 3 lines: #!/perl # LaTeX2HTML l2hconf.pm # $Id: l2hconf.pin,v 1.17 2002/06/15 22:46:36 RRM Exp $ Ok, so line 2 is commented out. so what is wrong? I changed the first line to #!/usr/local/perl but it did not make any difference. more information: $ which perl /usr/bin/perl $ perl --version This is perl, v5.8.5 built for cygwin-thread-multi-64int Why does it say '64int' there? my machine is 32 bit P4. I read on the net that latex2html might not work when using cygwin supplied perl, and I need to install windows perl, such as active Perl, and have that perl stub in cygwin tools, that calls windows perl.exe instead. may be I should try that? I'll supply more information if needed. thanks, Bill __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 -- 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: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
ops, typo: in the text below, instead of I changed the first line to #!/usr/local/perl I meant to write I changed the first line to #!/usr/bin/perl thanks, Bill --- bill BW [EMAIL PROTECTED] wrote: For the last 6 hrs I have been fighting with latex2html and cygwin to get latex2html to work, but I give up. Has anyone got latex2html to work on cygwin? This is what I have 1. Latex cygwin FULL installation. $ uname -a CYGWIN_NT-5.1 me 1.5.12(0.116/4/2) 2004-11-10 08:34 i686 unknown unknown Cygwin cygwins install just fine, all working well. 2. Get the netpbm programs, installed no problem 3. downloaded latex2html: latex2html-2002-2-1.tar latest version of late2html. untar, In the latex2html directory there is a file called L2hos.pm , Edit this file by replacing $^O with 'unix' 4. added everything to path, and for latex2html did ./configure, make, make install all went with NO errors !! 5. But now everytime I try the late2html command on a .tex file, I get the error $ latex2html foo.tex Fatal (use l2hconf): l2hconf.pm did not return a true value at (eval 7) line 2. BEGIN failed--compilation aborted at (eval 7) line 2. I look at the file l2hconf.pm, and I see this as first 3 lines: #!/perl # LaTeX2HTML l2hconf.pm # $Id: l2hconf.pin,v 1.17 2002/06/15 22:46:36 RRM Exp $ Ok, so line 2 is commented out. so what is wrong? I changed the first line to #!/usr/local/perl but it did not make any difference. more information: $ which perl /usr/bin/perl $ perl --version This is perl, v5.8.5 built for cygwin-thread-multi-64int Why does it say '64int' there? my machine is 32 bit P4. I read on the net that latex2html might not work when using cygwin supplied perl, and I need to install windows perl, such as active Perl, and have that perl stub in cygwin tools, that calls windows perl.exe instead. may be I should try that? I'll supply more information if needed. thanks, Bill __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 -- 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/ __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com -- 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: running .bat files from bash
-Original Message- From: cygwin-owner On Behalf Of Donal Murtagh Sent: 15 December 2004 20:10 I've noticed that if I want to run a .bat file in bash I have to cd to the directory it's in first in order for it to run properly For example, if I want to run c:\foo\bar.bat I have to use: cd /cygdrive/c/foo bar.bat if I try /cygdrive/c/foo/bar.bat it doesn't work properly. It seems that if I attempt the latter, the .bat file is launched, but doesn't work properly. The particular .bat file I'm running compiles a Java source tree, and when I try to launch it via /cygdrive/c/foo/bar.bat, the messages sent to standard output suggest it's working fine, but none of the .class files are created. Has anyone else come across this? Nope, but I have an experiment to suggest: what happens if you start up a DOS shell, and try running the batch file from a different directory to the one where it lives under DOS? If it still goes wrong, your batch file (or perhaps some makefile it invokes) has a bug; if it works, there's something cyg-weird going on. cheers, DaveK -- Can't think of a witty .sigline today -- 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: unison and cygwin on windows xp SP2
Dirk Leinenbach wrote: Hi folks, I have the problem that the native windows version of unison (2.9.1) on Windows XP SP2 together with cygwin (starting from DLL version 1.5.11) unison hangs after me entering the ssh password. This didn't happen with version 1.5.10 of the cygwin dll but this version cannot be installed with the cygwin installer, so I have to deal with the new version. I think that this unison problem is somehow related to the pipe code problem which was discussed on this mailing list in the first half of October, but I didn't see any results/solutions on this problem, too. The last message I found on this topic in the archive said something like 'we are looking for a solution...'. Now I was wondering if there was any progress in the meantime or if there are plans to develop a fix in the near future. Otherwise I would have to find a solution for unison without the cygwin ssh client. Thanks in advance, Your mileage should be greater if you use the cygwin build of unison, available through setup.exe. I've had much less problems after I switched. Cheers, Rob Dirk -- Dirk Leinenbach Computer Science Department Saarland University Germany Buildung 45, Room 318 Tel. +49 - 681 / 302 - 5557 Fax. +49 - 681 / 302 - 4290 -- 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: 1.5.12: mt sees incorrect maximum block size
On Dec 15 10:36, Brian Dessent wrote: Corinna Vinschen wrote: So, as you can see, the Windows NT tape functions doesn't allow me to set the block size to more than 64K, too. That's the same functionality used inside of Cygwin. I have no idea how to workaround that. I also didn't find anything useful on the Web so far. I'd *love* to get that solved, but I don't know how. I'm going to ask someone who's writing tape drivers for Windows, perhaps he has a clue. Other than that, I'm open to any useful hint from the community. A little googling found the following, but I don't have a tape drive so I cannot test it... http://www.complanguages.com/Reading_128K_Blocks_off_a_DLT_via_Adaptec_AHA2940AU-7710081-5505-a.html Thanks Brian, that was very interesting. I tried it with my Adaptec U160 but unfortunately nothing changed. I had a quick look into winTar, but, alas, that's a proprietary application. If there's actually some problem with the SCSI adapter, then winTar apparently knows how to get around it. I don't know much about the SCSI low level interface... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: Python, USB and cygwin
At 11:41 PM 12/15/2004, you wrote: I have a couple of USB devices which are based upon FTDI chips. I am using the FTDI virtual serial port drivers. The devices appear to work properly except when attempting to communicate with them via cygwin python. Scripts which work o.k. with Windows python will not work properly with cygwin python. The point of failure depends upon the Windows version. Under Windows 98, the scripts fail to complete the opening of the virtual serial port,. The failure occurs in tcgetattr and an error '22, Invalid argument' is returned. I haven't followed this further into the bowels of python to work out what this means but tcgetattr() in cygwin 'C' does not fail. Under Windows 2000, the same python scripts go further but fail further down the track, early during the attempted transfer of data. The same python scripts have worked well in the past under cygwin when I use a real serial port. Are there known problems with cygwin python and USB virtual serial ports? If so, are there any solutions or work-arounds? There's nothing about your configuration that looks troublesome that I can see. If things work well with real serial ports and Cygwin but not with virtual serial ports, the problem may actually be with the virtual serial port drivers. But there's no way to really tell without investigating further. If there are others on this list using the chips you are with the same problems with those virtual serial port drivers, then they may have more information or be willing to track down this problem for you. If not, you may be stuck trying to figure out what's wrong on your own, more or less. Since the problem isn't obvious without the virtual serial port drivers, only those with them could track this further. :-( -- 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: Error with managed mount point.
On Wed, 15 Dec 2004 19:21:51 -0500, Larry Hall wrote: At 03:48 PM 12/15/2004, you wrote: Running strace pointed me to the proper place to look for the error. However, the proper fix is maybe more of a philosophy issue. No, they need to be removed. Windows behavior is to ignore one or more '.'s at the end of a file so we're stuck with that in normal Cygwin-working mode. I actually haven't delved into the inner workings of the managed mount option code but if there's going to be a place to hang onto and translate the trailing '.'s, it would be in this special case code. Without looking at more than just the patch lines, I'm guessing that the patch you made (submitted to the Cygwin patches list) to path_conv::check() are going to be in too generic of a spot to be the right thing to do for just managed mount mode, though I could be wrong. I'll try to find a minute tonight to comment further. I am going to have to disagree with you on this point. If you are going to have a truly managed filesystem, then it needs to handle all characters, and not arbitrarily remove/drop any characters. Consider the trivial tar file I've attached. Each README file will contain the directory heirarchy under which it can be found. The tar file was created on a SunOS box, but should be portable. Now, if you arbitrarily drop the trailing dots, you will wind up with less than half of the README files, which for a real application, could be a badness. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 tmpdir.tar Description: Unix tar archive -- 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: Patch to allow trailing dots on managed mounts
On Wed, 15 Dec 2004 21:32:47 -0500, Christopher Faylor wrote: On Wed, Dec 15, 2004 at 04:04:13PM -0700, Mark Paulus wrote: This patch is as trivial as I could get to allow trailing dots to be used on a managed file system. Unfortunately, my company will not sign the waiver, so I cannot sign up for any significant changes to the cygwin sources. So, hopefully, this patch is small enough to squeek under the limit, or it can be a starting point for discussions on how to fix the original problem. * path.cc (path_conv::check): retain trailing dots and spaces for managed mounts. Er, this patch apparently just leaves the trailing dots in the converted path, bypassing the loop which attempts to remove them. That's not the way to do this. Sorry. I am bypassing the loop which attemps to remove them, because for a managed filesystem, I think they need to remain. Consider the following snippets from my strace.out: 40 2418062 [main] tar 1600 normalize_posix_path: /tmp1/usr/share/sgml/Netscape_Comm._Corp. = normalize_posix_path ./usr/share/sgml/Netscape_Comm._Corp.) 40 2418102 [main] tar 1600 mount_info::conv_to_win32_path: conv_to_win32_path (/tmp1/usr/share/sgml/Netscape_Comm._Corp) 43 2418145 [main] tar 1600 set_flags: flags: binary (0x2) 47 2418192 [main] tar 1600 mount_info::conv_to_win32_path: src_path /tmp1/usr/share/sgml/Netscape_Comm._Corp, dst c:\cygmanaged\usr\share\sgml\% 4Eetscape_%43omm._%43orp, flags 0x80A, rc 0 In the above, conv_to_win32_path removes the trailing dot, which creates a directory without the trailing dot. now, further down the strace: 265 2419810 [main] tar 1600 normalize_posix_path: src ./usr/share/sgml/Netscape_Comm._Corp./dtd 41 2419851 [main] tar 1600 cwdstuff::get: posix /tmp1 38 2419889 [main] tar 1600 cwdstuff::get: (/tmp1) = cwdstuff::get (0x22EA50,260, 1, 0), errno 0 38 2419927 [main] tar 1600 normalize_posix_path: /tmp1/usr/share/sgml/Netscape_Comm._Corp./dtd = normalize_posix_path (./usr/share/sgml/Netscape_Comm._Corp./dtd) 39 2419966 [main] tar 1600 mount_info::conv_to_win32_path: conv_to_win32_path (/tmp1/usr/share/sgml/Netscape_Comm._Corp./dtd) 42 2420008 [main] tar 1600 set_flags: flags: binary (0x2) 47 2420055 [main] tar 1600 mount_info::conv_to_win32_path: src_path /tmp1/usr/share/sgml/Netscape_Comm._Corp./dtd, dst c:\cygmanaged\usr\share \sgml\%4Eetscape_%43omm._%43orp%2E\dtd, flags 0x80A, rc 0 Here, tar is going to look for a directory that cygwin clearly thinks should have a dot at the end (the %2E), and it's going to fail because it's not going to find it, since the directory was created above without the %2E. Other than the way I proposed, I'm not sure how to fix this, since the issue seems to be that conv_to_win32_path() needs to get the trailing dot in it's input argument, and check() is stripping it out. The only way I can see to fix this behaviour is to leave the trailing dots in the string. Maybe conv_to_win32_path needs to deal/strip with the trailing dots, depending upon whether it's a managed filesystem or not? 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: unison and cygwin on windows xp SP2
Now I was wondering if there was any progress in the meantime or if there are plans to develop a fix in the near future. Otherwise I would have to find a solution for unison without the cygwin ssh client. Your mileage should be greater if you use the cygwin build of unison, available through setup.exe. I've had much less problems after I switched. I'm glad to hear it :) Actually there are a few known bugs in the current cygwin release of Unison. I have a patched version, but because of some packaging issues I haven't released it yet. I'll do so as soon as I can. Andrew. -- To reply by email, replace deadspam.com by alumni.utexas.net -- 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/
Setup: 'Download From Internet' creates 'c:/cygwin/etc/setup'
Performing a new installation on a machine I selected the 'Download From Internet Option'. Files were saved to the root of a currently empty D:/ partition. Ordinarily I'd just delete the 'c:/cygwin/etc/setup' dirs and files as they seem to contain summmary download-specific information, but I'm wondering why this folder was created where it was. Maybe if I had selected 'Install from Internet' and picked 'c:/cygwin' (on this machine) for the installation directory (neither of which is the case), it might make more sense. Thanks. -- George -- 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: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
On Thu, 16 Dec 2004, bill BW wrote: For the last 6 hrs I have been fighting with latex2html and cygwin to get latex2html to work, but I give up. Has anyone got latex2html to work on cygwin? [snip install with no problems] 5. But now everytime I try the late2html command on a .tex file, I get the error $ latex2html foo.tex Fatal (use l2hconf): l2hconf.pm did not return a true value at (eval 7) line 2. BEGIN failed--compilation aborted at (eval 7) line 2. I look at the file l2hconf.pm, and I see this as first 3 lines: #!/perl # LaTeX2HTML l2hconf.pm # $Id: l2hconf.pin,v 1.17 2002/06/15 22:46:36 RRM Exp $ You should look at the whole file, to see what the last returned value is. The last line of the file is usually 1;. Ok, so line 2 is commented out. so what is wrong? What's that got to do with anything? It's a comment. I changed the first line to #!/usr/local/perl but it did not make any difference. Nor should it. The l2hconf.pm is not executed via the shell, but via the use() function, which ignores the shebang line altogether. FWIW, I think the invalid shebang is there exactly to prevent running that file via the shell (unless your system has perl in the root directory). more information: $ which perl /usr/bin/perl $ perl --version This is perl, v5.8.5 built for cygwin-thread-multi-64int Why does it say '64int' there? my machine is 32 bit P4. This means it supports 64-bit functions, that's all. I read on the net that latex2html might not work when using cygwin supplied perl, and I need to install windows perl, such as active Perl, and have that perl stub in cygwin tools, that calls windows perl.exe instead. may be I should try that? Try it first with the Cygwin version. Fixing l2hconf.pm should help. 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: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
-Original Message- From: cygwin-owner On Behalf Of Igor Pechtchanski Sent: 16 December 2004 17:52 $ latex2html foo.tex Fatal (use l2hconf): l2hconf.pm did not return a true value at (eval 7) line 2. BEGIN failed--compilation aborted at (eval 7) line 2. I look at the file l2hconf.pm, and I see this as first 3 lines: #!/perl # LaTeX2HTML l2hconf.pm # $Id: l2hconf.pin,v 1.17 2002/06/15 22:46:36 RRM Exp $ You should look at the whole file, to see what the last returned value is. The last line of the file is usually 1;. Ok, so line 2 is commented out. so what is wrong? What's that got to do with anything? It's a comment. Indeed. Which makes it somewhat surprising that the error message would claim the error to have occurred on that line. cheers, DaveK -- Can't think of a witty .sigline today -- 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: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
On Thu, Dec 16, 2004 at 12:51:51PM -0500, Igor Pechtchanski wrote: On Thu, 16 Dec 2004, bill BW wrote: Nor should it. The l2hconf.pm is not executed via the shell, but via the use() function, which ignores the shebang line altogether. FWIW, I think the invalid shebang is there exactly to prevent running that file via the shell (unless your system has perl in the root directory). more information: $ which perl /usr/bin/perl $ perl --version This is perl, v5.8.5 built for cygwin-thread-multi-64int Why does it say '64int' there? my machine is 32 bit P4. This means it supports 64-bit functions, that's all. Means perl was built to use 64 bit signed and unsigned integer types. That string is supposed to contain the most common build options that produce binary incompatibility between one perl build and another. -- 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/
XView for Cygwin
Is anyone out there able to supply the XView libraries and header files for Cygwin that can save me from reinventing the wheel? Even better would be the source code, working makefile system, and prerequisits so that I can debug into the code. Several people have said that they were working on it, but I have not seen the results of their labor anywhere. Extra credit is available for the SlingShot libraries. This is for a non-profit, academic, good cause. Please email me with any leads. Thank you very much. Keith. -- 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/
Piping output from sqlplus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having a strange problem reading the output from sqlplus in Cygwin. Sqlplus is a windows command line program used to access oracle databases. My command looks something like this... sqlplus -s ! | read line user/[EMAIL PROTECTED] set pagesize 0 linesize 200 feedback off tab off select col1||chr(9)||col2 from table; ! This should output one line to stdout with the two values separated by a tab character. The read command should read it into the variable $line. On my Solaris system it works perfectly. In Cygwin, $line is empty. If I remove the read line, the output displays on the tty just fine. I though it might be related to the line end characters so I tried converting them with the dos2unix filter. Didn't work. Neither did tr -d \\r. Both ways, $line still ends up being empty. If I replace the read line with od -c to dump the characters, it shows the one line as expected. If I redirect the output to a file, the file contains one line as expected. If I try to read the output into a variable, I get an empty variable Any ideas? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBwfAbzIf+rZpn0oQRAtcxAJ46XUAtR57DsuKAXj7nBFmR1V/QNQCfX/da 09U1qXkDrheltOlQrMSubzU= =pQxI -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/
1.5.7: problem using rexec and Windows batch files
Hi. I've installed Cygwin 1.5.7 on a Windows 2000 server. I'd like to rexec from a client (z/OS) to the Windows server, execute a Windows batch file (/tmp/tmp.bat), and view the output of the commands. The windows user has been added to the passwd file, and his initial program has been set to /bin/bash. I'm getting the following error and no command output (though the commands of the batch file are executed): The process tried to write to a nonexistent pipe. I've looked this up on the web and newsgroups, but haven't found the solution. I've read some of the Cygwin User's guide including the section describing problems running batch files in Windows. Here's what I've tried: 1. Created the CYGWIN system variable in Windows and set it to tty. No effect. 2. Changed the initial program of the user to /cygdrive/c/winnt/system32/cmd.exe. I was hoping to get the user to spawn a Windows command shell instead of a bash shell and run the .bat file from there. No ouput, and the .bat file didn't execute it's commands. 3. Redirecting STDOUT and STDERR to a file. No error produced, commands were executed, but I would rather have the output dumped to STDOUT for review. So, am I missing something here as far as my config/setup goes? The Cygwin Users guide kind of suggests that this might not work at all, but I was hoping someone else was running .bat files using rexec and had a solution. Please forgive me if this is a FAQ, but I couldn't find it on the net. If the answer is in some documentation, just point me there. Thanks for your help, JP Tulane University tmp.bat contents: dir dir tmp1.txt cygcheck.out: Cygwin Win95/NT Configuration Diagnostics Current System Time: Thu Dec 16 11:12:32 2004 Windows 2000 Server Ver 5.0 Build 2195 Service Pack 4 Path: d:\oracle\ora91\bin Output from d:\cygwin\bin\id.exe (nontsec) UID: 400(adminuser) GID: 401(mkpasswd) 401(mkpasswd) Output from d:\cygwin\bin\id.exe (ntsec) UID: 400(adminuser) GID: 401(mkpasswd) 0(root) 544(Administrators) 545(Users) 10545(mkgroup_l_d) 0(root) 544(Administrators) 545(Users) 401(mkpasswd) SysDir: C:\WINNT\system32 WinDir: C:\WINNT Path = `d:\oracle\ora91\bin' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\adminuser\Application Data' CLIENTNAME = `CLIENTCOMP' CommonProgramFiles = `C:\Program Files\Common Files' COMPUTERNAME = `SERVERCOMP' ComSpec = `C:\WINNT\system32\cmd.exe' HOMEDRIVE = `C:' HOMEPATH = `\Documents and Settings\adminuser' LOGONSERVER = `\\SERVERD' NUMBER_OF_PROCESSORS = `2' OS = `Windows_NT' Os2LibPath = `C:\WINNT\system32\os2\dll;' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 5 Stepping 2, GenuineIntel' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0502' ProgramFiles = `C:\Program Files' PROMPT = `$P$G' SESSIONNAME = `RDP-Tcp#19' SystemDrive = `C:' SystemRoot = `C:\WINNT' TEMP = `C:\DOCUME~1\adminuser\LOCALS~1\Temp\1' TMP = `C:\DOCUME~1\adminuser\LOCALS~1\Temp\1' USERDNSDOMAIN = `domain' USERDOMAIN = `domain' USERNAME = `adminuser' USERPROFILE = `C:\Documents and Settings\adminuser' windir = `C:\WINNT' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x0020 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `d:\cygwin' flags = 0x0008 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `d:\cygwin/bin' flags = 0x0008 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `d:\cygwin/lib' flags = 0x0008 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/X11R6/lib/X11/fonts (default) = `d:\cygwin\usr\X11R6\lib\X11\fonts' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options a: fd N/AN/A c: hd NTFS8754Mb 31% CP CS UN PA FC d: hd NTFS8754Mb 58% CP CS UN PA FC Programs e: cd CDFS 635Mb 100%CS UN 9201CLT s: hd NTFS8754Mb 37% CP CS UN PA FC d:\cygwin / system textmode d:\cygwin/bin /usr/bin system textmode d:\cygwin/lib /usr/lib system textmode d:\cygwin\usr\X11R6\lib\X11\fonts /usr/X11R6/lib/X11/fonts system binmode . /cygdrive system textmode,cygdrive Found: .\awk.exe Found: .\bash.exe Found: .\cat.exe Found: .\cp.exe Not Found: cpp (good!) Found:
RE: Piping output from sqlplus
At Thursday, December 16, 2004 3:29 PM, Chuck wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having a strange problem reading the output from sqlplus in Cygwin. Sqlplus is a windows command line program used to access oracle databases. My command looks something like this... sqlplus -s ! | read line user/[EMAIL PROTECTED] set pagesize 0 linesize 200 feedback off tab off select col1||chr(9)||col2 from table; ! This should output one line to stdout with the two values separated by a tab character. The read command should read it into the variable $line. On my Solaris system it works perfectly. In Cygwin, $line is empty. If I remove the read line, the output displays on the tty just fine. I though it might be related to the line end characters so I tried converting them with the dos2unix filter. Didn't work. Neither did tr -d \\r. Both ways, $line still ends up being empty. If I replace the read line with od -c to dump the characters, it shows the one line as expected. If I redirect the output to a file, the file contains one line as expected. If I try to read the output into a variable, I get an empty variable Any ideas? If the output shows up OK in a file, do VAR=$(cat file) -- 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: find command hangs for 20 sec before starting with cygwin1.dll is 1.5.12
I am experiencing the same delay with findutils 4.2.10-5. If I downgrade to an older version of findutils, the delay goes away. On my system, `find' was taking 30-40 seconds to start. I found that after I removed a bad mapped network drive, the delay dropped to 6-7 seconds for `find' to start. I am also finding that running `mount' to display the list of mounts pauses for the same 6-7 seconds, and if I run `mount' and `find' at the same time, they both always finish at the same time, even if I start running them a couple seconds apart. That is about the extent of diagnostic I have time to do right now. IF Andrew Stebakov wrote: Hi, I just updated my cygwin to latest (version 1.59) and cygwin1.dll is 1.5.12. I found that find command takes a long time to start (about 20 seconds). It shows in my xemacs when I load ecb and issue igrep-find. I replaced the cygwin1.dll with some old version and the problem went away (also I had to replace xargs, grep and find executables for the old ones). On another PC the same cygwin with xemacs doesnt show the problem. Both of them have the VirusScan on. I tried to disable the VirusScan but it doesnt fix the problem. What can I do fix it? Can I get the previous version of cygwin1.dll? Thanks in advance, Andrei -- 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: Piping output from sqlplus
On Thu, Dec 16, 2004 at 03:29:16PM -0500, Chuck wrote: I'm having a strange problem reading the output from sqlplus in Cygwin. Sqlplus is a windows command line program used to access oracle databases. My command looks something like this... sqlplus -s ! | read line user/[EMAIL PROTECTED] set pagesize 0 linesize 200 feedback off tab off select col1||chr(9)||col2 from table; ! This should output one line to stdout with the two values separated by a tab character. The read command should read it into the variable $line. On my Solaris system it works perfectly. In Cygwin, $line is empty. Just to demonstrate what you're seeing without the sqlplus requirement: bash$ echo hello | read line bash$ echo $line bash$ The reason for the behavior is apparently that when you use read in a pipe like this bash and ash fork a separate process so the variable only exists very briefly in that process and `line' is never defined in the main process. zsh does what you'd expect, so if you can use zsh instead of bash, that would be a solution. Otherwise, you probably will have to experiment with setting IFS and using either $(sqlplus) or `sqlplus` . 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: Piping output from sqlplus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Buchbinder, Barry (NIH/NIAID) wrote: | At Thursday, December 16, 2004 3:29 PM, Chuck wrote: | |-BEGIN PGP SIGNED MESSAGE- |Hash: SHA1 | |I'm having a strange problem reading the output from sqlplus in |Cygwin. Sqlplus is a windows command line program used to access |oracle |databases. My command looks something like this... | |sqlplus -s ! | read line |user/[EMAIL PROTECTED] |set pagesize 0 linesize 200 feedback off tab off |select col1||chr(9)||col2 |from table; |! | |This should output one line to stdout with the two values separated |by a tab character. The read command should read it into the variable |$line. |On my Solaris system it works perfectly. In Cygwin, $line is empty. | |If I remove the read line, the output displays on the tty just fine. | |I though it might be related to the line end characters so I tried |converting them with the dos2unix filter. Didn't work. Neither did tr |-d \\r. Both ways, $line still ends up being empty. | |If I replace the read line with od -c to dump the characters, it |shows the one line as expected. | |If I redirect the output to a file, the file contains one line as |expected. | |If I try to read the output into a variable, I get an empty variable | |Any ideas? | | | If the output shows up OK in a file, do | VAR=$(cat file) | That may work but it misses the point. I'm writing a script and I want it to work on Cygwin and unix. BTW the shell I'm using is ksh. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBwfaHzIf+rZpn0oQRAvKQAJ9WYJ6CbGrEeDwN9lMg2fzOIGsiOgCffjyz BxriTOuv4IqT3zdFMHUesIY= =jJGJ -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: Piping output from sqlplus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christopher Faylor wrote: | On Thu, Dec 16, 2004 at 03:29:16PM -0500, Chuck wrote: | |I'm having a strange problem reading the output from sqlplus in Cygwin. |Sqlplus is a windows command line program used to access oracle |databases. My command looks something like this... | |sqlplus -s ! | read line |user/[EMAIL PROTECTED] |set pagesize 0 linesize 200 feedback off tab off |select col1||chr(9)||col2 | |from table; | |! | |This should output one line to stdout with the two values separated by a |tab character. The read command should read it into the variable $line. |On my Solaris system it works perfectly. In Cygwin, $line is empty. | | | Just to demonstrate what you're seeing without the sqlplus requirement: | | bash$ echo hello | read line | bash$ echo $line | | bash$ | | The reason for the behavior is apparently that when you use read in a | pipe like this bash and ash fork a separate process so the variable only | exists very briefly in that process and `line' is never defined in the | main process. | | zsh does what you'd expect, so if you can use zsh instead of bash, that | would be a solution. Otherwise, you probably will have to experiment | with setting IFS and using either $(sqlplus) or `sqlplus` . | | cgf | Actually I'm using ksh. $ echo hello | read LINE $ echo $LINE $ Looks like you said. I know this is not the expectd behaviour for ksh though. On Solaris ksh ... Solaris$ echo hello | read LINE Solaris$ echo $LINE hello Solaris$ Why would ksh behave differently under Cygwin than under Solaris? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBwfYpzIf+rZpn0oQRAtnYAJ9jBdGzER29YzWnMOmREeQJv+fasQCdGFQc jRPqneau2f7PFhDXtwKGsn4= =bY4I -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/
iSeries: Lab400 Access Privileges
iSeries/AS400 Professionals: update your info for a chance to win $1,000.00 in iSeries/400 training and your own 1GB flash drive... Dear Lab400 user, Since we relaunched the Lab400 website for iSeries/400 professionals, some of our members have not yet updated their account info. There is no charge. If you have not yet done so, please take a minute now because without your updated info you can't access member content. (Please remember we protect your privacy at all times.) http://www.lab400.com/RI_pages.asp?idno=4131 Feeling Lucky? By updating or creating a new account you could win $1,000.00 worth of your choice of our acclaimed self-paced iSeries/400 training and a password protected 1GB flash drive. (Winner will be announced February 1, 2005.) See the courses you may choose from and that cool flash drive here: http://www.lab400.com/RI_pages.asp?idno=3975 Updating your account (or creating a new one) will entitle you to unlimited access to the members area where you will find over 50 complimentary tech downloads, including helpful tutorials with code, along with management intelligence on security and a lot more. http://www.lab400.com/RI_pages.asp?idno=4131 Please Note: If you already have a valid Lab400 account, you are automatically entered in our $1,000.00 iSeries training/flash drive offer. IMPORTANT REMINDER: The winner will be notified by email. If you or your organization utilizes email-filtering software, you may need to add us to your safe list or adjust your settings in order to be able to receive our tech updates and industry news publications. http://www.lab400.com/RI_pages.asp?idno=4131 Thanks for getting back to us. All of us at Rochester Initiative wish you a happy and safe holiday season. Best Regards, Steve Wilt Manager Rochester Initiative 1384 Poinsettia Ave., Lab C Vista, CA 92081 760-597-1400 www.lab400.com If this notice has reached you in error or if you no longer wish to receive emails from us please reply to this message with the word CANCEL in the subject line. Well promptly take you off. Thanks. -- 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: Piping output from sqlplus
Why would ksh behave differently under Cygwin than under Solaris? cygwin ksh is pdksh. The specific set of code you gave does not work in pdksh. Read about it here: http://web.cs.mun.ca/~michael/pdksh/ Its weak points are that there are still a few differences from ksh88 (the major one is that `echo hi | read x' does not set x in the current shell - the read is done in a separate process). See the NOTES file in the distribution for more details. You can get a Cygwin ksh from www.kornshell.com -- 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: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
On Thu, 16 Dec 2004, Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of Igor Pechtchanski Sent: 16 December 2004 17:52 $ latex2html foo.tex Fatal (use l2hconf): l2hconf.pm did not return a true value at (eval 7) line 2. BEGIN failed--compilation aborted at (eval 7) line 2. I look at the file l2hconf.pm, and I see this as first 3 lines: #!/perl # LaTeX2HTML l2hconf.pm # $Id: l2hconf.pin,v 1.17 2002/06/15 22:46:36 RRM Exp $ You should look at the whole file, to see what the last returned value is. The last line of the file is usually 1;. Ok, so line 2 is commented out. so what is wrong? What's that got to do with anything? It's a comment. Indeed. Which makes it somewhat surprising that the error message would claim the error to have occurred on that line. Oh, I missed that. The line 2 refers to the line of the eval statement, not the line in the file... I don't recall the exact source, but isn't use defined in terms of eval? Perl experts? 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: Non-US keyboard (PT) bash problem
On Thu, 16 Dec 2004, Lino Miguel Martins Tinoco wrote: Hi! I can't have special characters displayed correctly on bash (ç, Ç and accents). They are displayed as ? when I do a ls but they get displayed correctly if I pipe the results or send them to a file. On command line they are displayed as the respective octal value (ç is displayed as \347). Before I try the set meta-flag solution, bash was interpreting some of these symbols (hitting ç twice gave me an ls). For 'ls' you may wish to use the --show-control-chars flag. For bash (or, rather, readline), you will need all four of set meta-flag on set convert-meta off set input-meta on set output-meta on (see http://www.cygwin.com/faq/faq_3.html#SEC46), and/or the respective manpages. Also tried codepage:oem, but didn't worked. On a DOS box this characters are displayed ok. They are also displayed ok on any editor (vi, emacs, ...). This happens on console window and xterm or rxvt. When you say DOS box, I presume you mean the actual Windows Command Prompt window, so looks like your problem is with bash. Since you seem to have the same behavior in console, xterm, and rxvt, this doesn't look like a font issue. If the above doesn't help, please post the exact steps to reproduce the problem. 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/
1.5.12-1: deadlock in gmtime/localtime
Hello, the problem occurs in a multithreaded program, but only one thread calling gmtime_r (calling localtime_r locks as well). The other tread calls gettimeofday/time. The thread calling gmtime_r is stalled completely. Machine is XP SP2. I've tested this problem on multiple machines (w/ diff timezones) but there isn't one consistent system criterion which makes this problem occur. However, if it occurs, it occurs persistently. Since I required gmtime the workaround was to write a gmtime routine (based on the existing one) without the special case for !is_gmtime -- works fine, no dead locks. Has anyone encountered a similar problems and is there a generic workaround/fix for this problem? Thanks, Immanuel P.S. Attached cygcheck.out... Cygwin Configuration Diagnostics Current System Time: Thu Dec 16 16:30:23 2004 Windows XP Professional Ver 5.1 Build 2600 Service Pack 2 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\Tcl\bin c:\WINDOWS\system32 c:\WINDOWS c:\WINDOWS\System32\Wbem c:\PROGRAM FILES\THINKPAD\UTILITIES Output from C:\cygwin\bin\id.exe (nontsec) UID: 1004(Immanuel Patzschke) GID: 513(None) 513(None) Output from C:\cygwin\bin\id.exe (ntsec) UID: 1004(Immanuel Patzschke) GID: 513(None) 0(root) 513(None) 544(Administrators) 545(Users) SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS HOME = `C:\cygwin\home\Immanuel Patzschke' MAKE_MODE = `unix' PWD = `/cygdrive/c/st/tmp' USER = `Immanuel Patzschke' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\Immanuel Patzschke\Application Data' COMMONPROGRAMFILES = `C:\Program Files\Common Files' COMPUTERNAME = `TIPLAP' COMSPEC = `C:\WINDOWS\system32\cmd.exe' CVS_RSH = `/bin/ssh' FP_NO_HOST_CHECK = `NO' HOMEDRIVE = `C:' HOMEPATH = `\Documents and Settings\Immanuel Patzschke' HOSTNAME = `TIPLAP' INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:' LOGONSERVER = `\\TIPLAP' MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/ssl/man:/usr/X11R6/man' NUMBER_OF_PROCESSORS = `1' OLDPWD = `/cygdrive/c/st/tmp/bpmk1180' OS = `Windows_NT' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.tcl' PKG_CONFIG_PATH = `/usr/X11R6/lib/pkgconfig' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 11 Stepping 1, GenuineIntel' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0b01' PROGRAMFILES = `C:\Program Files' PROMPT = `$P$G' PS1 = `\[\033]0;\w\007 [EMAIL PROTECTED] \[\033[33m\w\033[0m\] $ ' SESSIONNAME = `Console' SHLVL = `1' SYSTEMDRIVE = `C:' SYSTEMROOT = `C:\WINDOWS' TEMP = `C:\DOCUME~1\IMMANU~1\LOCALS~1\Temp' TERM = `cygwin' TMP = `C:\DOCUME~1\IMMANU~1\LOCALS~1\Temp' USERDOMAIN = `TIPLAP' USERNAME = `Immanuel Patzschke' USERPROFILE = `C:\Documents and Settings\Immanuel Patzschke' WINDIR = `C:\WINDOWS' _ = `/usr/bin/cygcheck' POSIXLY_CORRECT = `1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x0022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `C:\cygwin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `C:\cygwin/bin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `C:\cygwin/lib' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/X11R6/lib/X11/fonts (default) = `C:\cygwin\usr\X11R6\lib\X11\fonts' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options c: hd NTFS 28947Mb 69% CP CS UN PA FC tiplap d: cd N/AN/A C:\cygwin / system binmode C:\cygwin/bin /usr/bin system binmode C:\cygwin/lib /usr/lib system binmode C:\cygwin\usr\X11R6\lib\X11\fonts /usr/X11R6/lib/X11/fonts system binmode . /cygdrive system binmode,cygdrive Found: C:\cygwin\bin\awk.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cpp.exe Found: C:\cygwin\bin\find.exe Found: C:\cygwin\bin\gcc.exe Found: C:\cygwin\bin\gdb.exe Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\mv.exe Found: C:\cygwin\bin\rm.exe Found: C:\cygwin\bin\sed.exe
Re: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
--- Igor Pechtchanski [EMAIL PROTECTED] wrote:
On Thu, 16 Dec 2004, bill BW wrote:
$ latex2html foo.tex
Fatal (use l2hconf): l2hconf.pm did not return a
true value at (eval 7) line 2.
BEGIN failed--compilation aborted at (eval 7) line
2.
I look at the file l2hconf.pm, and I
see this as first 3 lines:
#!/perl
# LaTeX2HTML l2hconf.pm
# $Id: l2hconf.pin,v 1.17 2002/06/15 22:46:36 RRM
Exp $
You should look at the whole file, to see what the
last returned value is.
The last line of the file is usually 1;.
Yes it is. I did not touch the file l2hconf.m
more information:
$ which perl
/usr/bin/perl
$ perl --version
This is perl, v5.8.5 built for
cygwin-thread-multi-64int
Why does it say '64int' there? my machine is
32 bit P4.
Try it first with the Cygwin version. Fixing
l2hconf.pm should help.
HTH,
Igor
--
but what is wrong with l2hconf.pm?
This is what I tried now:
I looked at latex2html to see where it calls
l2hconf.pm, it is at lines 120:130
-- from latex2html --
# Local configuration, read at runtime
# Read the $CONFIG_FILE (usually l2hconf.pm )
if($ENV{'L2HCONFIG'}) {
require $ENV{'L2HCONFIG'} ||
die Fatal (require $ENV{'L2HCONFIG'}): $!;
} else {
eval 'use l2hconf';
if($@) {
die Fatal (use l2hconf): [EMAIL PROTECTED];
}
}
- end latex2html cut -
so to test this, from cygwin shell I typed just
the command that calls l2hconf as follows:
start test -
$ perl
eval 'use l2hconf';
if($@) {
die Fatal (use l2hconf): [EMAIL PROTECTED];
}
Fatal (use l2hconf): Undefined subroutine
main::ignore_commands called at l2hconf.pm line
1216.
Compilation failed in require at (eval 1) line 2.
BEGIN failed--compilation aborted at (eval 1) line 2.
- end test
Ok, so the real problem is really at line 1216 in
l2hconf.pm. so I went to line 1216 there, and
this is the content starting from line 1216:
line 1216 to line 1217
::ignore_commands( _IGNORED_CMDS_);
htmlrule # [] # \$_ = join('',BRHR,\$_)
- end lines 1216 to line 1217
I can include the whole file if needed, but
this is out of the box, did not touch it, and
here is the text of the this file on this
URL, someone posted it for a problem:
http://www.mail-archive.com/latex2html@tug.org/msg00372.html
so, any ideas what to do now? I am very bad at
perl, having writting may be 10 lines in perl
all of my life. and this thing should work as
is, unless something wrong with perl build on
cygwin?
any more information I can provide on this?
thank you,
Bill
__
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
--
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/
Bad mirros
I've been trying for weeks to upgrade my Cygwin installation but the setup program, after I have spent 15 or 20 minutes selecting the software I want, comes back and says the download is aborted, would I like to try again? This is very frustrating because then I have to spend another 20 minutes on another mirror. So far, after 8 tries, I have not found a good mirror. Anyone know of a good mirror? Thanks, Siegfried -- 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: 1.5.12-1: deadlock in gmtime/localtime
On Thu, Dec 16, 2004 at 04:52:48PM -0800, Till Immanuel Patzschke wrote: the problem occurs in a multithreaded program, but only one thread calling gmtime_r (calling localtime_r locks as well). The other tread calls gettimeofday/time. The thread calling gmtime_r is stalled completely. Machine is XP SP2. Sounds like you understand the problem well enough to write a simple test case (tm) which would demonstrate the problem. This should be no more than twenty or thirty lines of code. Please send the test case here so that we can investigate. Thanks, 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: Bad mirros
On Thu, Dec 16, 2004 at 06:38:22PM -0700, Siegfried Heintze wrote: I've been trying for weeks to upgrade my Cygwin installation but the setup program, after I have spent 15 or 20 minutes selecting the software I want, comes back and says the download is aborted, would I like to try again? This is very frustrating because then I have to spend another 20 minutes on another mirror. So far, after 8 tries, I have not found a good mirror. Anyone know of a good mirror? Yes. I know of a good mirror, now that you mention it. I just avoid all of the bad ones. Otherwise, I'd be spending months or even years trying to download cygwin. 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: Bad mirros
At 08:38 PM 12/16/2004, you wrote: I've been trying for weeks to upgrade my Cygwin installation but the setup program, after I have spent 15 or 20 minutes selecting the software I want, comes back and says the download is aborted, would I like to try again? This is very frustrating because then I have to spend another 20 minutes on another mirror. So far, after 8 tries, I have not found a good mirror. Anyone know of a good mirror? I use http://mirrors.cn.net. YMMV. Typically, what makes a good or bad mirror has more to do with the specifics of the path from you to it than anything else. -- 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: Bad mirros
Siegfried Heintze wrote: I've been trying for weeks to upgrade my Cygwin installation but the setup program, after I have spent 15 or 20 minutes selecting the software I want, comes back and says the download is aborted, would I like to try again? Maybe it has been already fixed in setup, but if not, then you may be running into this: http://sources.redhat.com/ml/cygwin/2004-06/msg01103.html -- Jacek. -- 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: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
On Thu, Dec 16, 2004 at 05:10:38PM -0800, bill BW wrote:
--- Igor Pechtchanski wrote:
On Thu, 16 Dec 2004, bill BW wrote:
$ latex2html foo.tex
Fatal (use l2hconf): l2hconf.pm did not return a
true value at (eval 7) line 2.
BEGIN failed--compilation aborted at (eval 7) line
2.
I look at the file l2hconf.pm, and I
see this as first 3 lines:
#!/perl
# LaTeX2HTML l2hconf.pm
# $Id: l2hconf.pin,v 1.17 2002/06/15 22:46:36 RRM
Exp $
You should look at the whole file, to see what the
last returned value is.
The last line of the file is usually 1;.
Yes it is. I did not touch the file l2hconf.m
This is what I tried now:
I looked at latex2html to see where it calls
l2hconf.pm, it is at lines 120:130
-- from latex2html --
# Local configuration, read at runtime
# Read the $CONFIG_FILE (usually l2hconf.pm )
if($ENV{'L2HCONFIG'}) {
require $ENV{'L2HCONFIG'} ||
die Fatal (require $ENV{'L2HCONFIG'}): $!;
} else {
eval 'use l2hconf';
if($@) {
die Fatal (use l2hconf): [EMAIL PROTECTED];
}
}
- end latex2html cut -
so to test this, from cygwin shell I typed just
the command that calls l2hconf as follows:
start test -
$ perl
eval 'use l2hconf';
if($@) {
die Fatal (use l2hconf): [EMAIL PROTECTED];
}
Fatal (use l2hconf): Undefined subroutine
main::ignore_commands called at l2hconf.pm line
1216.
Compilation failed in require at (eval 1) line 2.
BEGIN failed--compilation aborted at (eval 1) line 2.
- end test
Ok, so the real problem is really at line 1216 in
l2hconf.pm. so I went to line 1216 there, and
this is the content starting from line 1216:
line 1216 to line 1217
::ignore_commands( _IGNORED_CMDS_);
htmlrule # [] # \$_ = join('',BRHR,\$_)
That doesn't follow. That error indicates that l2hconf is expecting
whatever used it to have set up an ignore_commands sub, which your test
doesn't do.
I'd recommend using the perl debugger (perl -d latex2html foo.tex)
to step through and see if you can isolate where things are going
astray. See perldoc perldebtut for help.
any more information I can provide on this?
Does the file on the website you linked to exactly match yours? There's
a part of it that says it is site specific. If there were a place you
could put your l2hconf.pm and latex2html on the web, I'd recommend you
ask at http://perlmonks.org/?node=Seekers%20of%20Perl%20Wisdom if using
the debugger doesn't help 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: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
--- Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: I'd recommend using the perl debugger (perl -d latex2html foo.tex) to step through and see if you can isolate where things are going astray. See perldoc perldebtut for help. Ok thanks, I did not know that one can debug perl that way. that is usefull to know. I am trying now to do this, for some reason it is not working, but I have not yet looked more to see why (it perl -d is not starting, as something is terminating right away). btw I am using XP pro, sp 2. $ uname -a CYGWIN_NT-5.1 me 1.5.12(0.116/4/2) 2004-11-10 08:34 i686 unknown unknown Cygwin $ which perl /usr/bin/perl $ perl --version This is perl, v5.8.5 built for cygwin-thread-multi-64int Copyright 1987-2004, Larry Wall $ which latex2html /usr/local/bin/latex2html $ perl -d latex2html foo.tex Loading DB routines from perl5db.pl version 1.27 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. Debugged program terminated. Use q to quit or R to restart, use O inhibit_exit to avoid stopping after program termination, h q, h R or h O to get additional info. DB1 May be this from man perldebug is realted to the above? In Perl, the debugger is not a separate program the way it usually is in the typical compiled environment. Instead, the -d flag tells the compiler to insert source information into the parse trees it's about to hand off to the interpreter. That means your code must first compile correctly for the debugger to work on it. Then when the inter-preter starts up, it preloads a special Perl library file containing the debugger. The program will halt right before the first run-time executable statement (but see below regarding compile-time statements) and ask you to enter a debugger command. Contrary to popular expectations, whenever the debugger halts and shows you a line of code, it always displays the line it's about to execute, rather than the one it has just executed. I have the feeling it will be another long night debugging this, all to get latex2html to work. Sometimes I think may be I should just switch to Linux and be done with it :) thanks for your help Bill __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail -- 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: Anyone got latex2html to work on cygwin?? Fatal (use l2hconf): l2hconf.pm
I just tried the following: - Uninstall perl from cygwin using cygwin setup.exe - installed Active Perl 5.8 on window. - use the cygutils perl.exe stub as described on http://cygutils.fruitbat.org/perl-contrib/index.html - Now when I try latex2html, I get other errors, and when I try to build latex2html, I got zillions of errors. - So, I removed Active Perl, and the perl.exe stub, it is just not working, and reinstalled cygwin perl again from setup.exe. And back to debugging this perl to see what I can find. If I know at least anyone out there got latex2html working on cygwin, this will give me hope. --- bill BW [EMAIL PROTECTED] wrote: --- Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: I'd recommend using the perl debugger (perl -d latex2html foo.tex) to step through and see if you can isolate where things are going astray. See perldoc perldebtut for help. Ok thanks, I did not know that one can debug perl that way. that is usefull to know. I am trying now to do this, for some reason it is not working, but I have not yet looked more to see why (it perl -d is not starting, as something is terminating right away). btw I am using XP pro, sp 2. $ uname -a CYGWIN_NT-5.1 me 1.5.12(0.116/4/2) 2004-11-10 08:34 i686 unknown unknown Cygwin $ which perl /usr/bin/perl $ perl --version This is perl, v5.8.5 built for cygwin-thread-multi-64int Copyright 1987-2004, Larry Wall $ which latex2html /usr/local/bin/latex2html $ perl -d latex2html foo.tex Loading DB routines from perl5db.pl version 1.27 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. Debugged program terminated. Use q to quit or R to restart, use O inhibit_exit to avoid stopping after program termination, h q, h R or h O to get additional info. DB1 May be this from man perldebug is realted to the above? In Perl, the debugger is not a separate program the way it usually is in the typical compiled environment. Instead, the -d flag tells the compiler to insert source information into the parse trees it's about to hand off to the interpreter. That means your code must first compile correctly for the debugger to work on it. Then when the inter-preter starts up, it preloads a special Perl library file containing the debugger. The program will halt right before the first run-time executable statement (but see below regarding compile-time statements) and ask you to enter a debugger command. Contrary to popular expectations, whenever the debugger halts and shows you a line of code, it always displays the line it's about to execute, rather than the one it has just executed. I have the feeling it will be another long night debugging this, all to get latex2html to work. Sometimes I think may be I should just switch to Linux and be done with it :) thanks for your help Bill __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail -- 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/ __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 -- 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/
Does wxWidgets 2.5.3 compile with Cygwin for anyone?
Hi all, Is there anyone who has wxWidgets 2.5.3 compiled with Cygwin after running ./configure --enable-debug? I get the follwoing error whic I cannot resolve: $ make ./bk-deps g++ -c -o netdll_fs_inet.o -D__WXMSW__ -DwxUSE_GUI=0 -DWXUSINGDLL -DWXMAKINGDLL_NET -D__WXDEBUG__ -I lib/wx/include/msw-ansi-debug-2.5 -I../include -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -g -O0 -Wall ../src/common/fs_inet. cpp In file included from ../include/wx/gsocket.h:172, from ../include/wx/sckaddr.h:24, from ../include/wx/socket.h:28, from ../include/wx/protocol/protocol.h:28, from ../include/wx/url.h:24, from ../src/common/fs_inet.cpp:30: ../include/wx/msw/gsockmsw.h:81: error: 'SOCKET' is used as a type, but is not defined as a type. ../include/wx/msw/gsockmsw.h:92: error: field `m_timeout' has incomplete type make: *** [netdll_fs_inet.o] Error 1 I have tried including several headers (including all the obvious ones) at various places in an attempt to resolve this problem but noting worked. Including winsock.h at a reasonable place gives me all kind of errors regarding conflicts with declarations in sys/socket.h Anyone any ideas where to look for a sollution? Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 e-mail: [EMAIL PROTECTED] web: www.askesis.nl -- 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: lilypond-2.4.2-1
I've made the latest stable version of LilyPond (http://www.lilypond.org) available for installation. This is a major upgrade from the previous 2.2.5. With this release, LilyPond does not rely anymore on TeX to do titling and page layout, but distributes page breaks optimally by itself to produce evenly spaced pages, while respecting user specified turning points. The slur formatting code has been completely rewritten, and now yields classical engraving quality results for most cases. In addition, version 2.4 adds fret diagrams, a safe execution mode for webserver use, a further simplified input format, better typography for ledger lines, many bugfixes and a fully revised and updated manual. This new package depends on the ec-fonts-mftraced package that's been available for some time now. For a brief descripton of this package, and listing of the files it contains, see http://cygwin.com/packages/lilypond http://cygwin.com/packages/findutils . 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. findutils should be updated automatically, assuming that you are using a mirror which has grabbed the latest version from sourceware.org. If you have questions or comments about the installation procedure please send them to the Cygwin mailing list. Bert -- 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/
rpm 4.1-1 problem
Hi guys, I'm using the rpm 4.1-1 package and I noticed that RPM_INSTALL_PREFIX is never set even in case we specify the --prefix or --relocate options. It looks like this bug is well known on this version (see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75550). I'm unfortunately not good enough to correct the bug by myself. The only fast solution I can think of is to use the previous version. Could you give me a hint where I could download it? Thanks for your help. Nick -- 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: find crashes in /proc/registry
Igor Pechtchanski schrieb: On Tue, 14 Dec 2004, Reini Urban wrote: Chuck schrieb: Christopher Faylor wrote: | On Mon, Dec 13, 2004 at 04:52:31PM -0500, Chuck wrote: |I don't know if this has been reported before | | It has. | The conclusion? | Don't use find on /proc. Are there any plans to fix it? Thanks. How? '*' is by POSIX definition an invalid filename character. '*' is by MS definition a valid registry key, which is mapped into a virtual file-system. '*' is a valid filename character (if not, please cite the part of POSIX that claims that). AFAIK, the only invalid filename character is '/', which is a directory separator. The problem with /proc/registry is that '/' is a valid value name character, so keys like HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin end up as /proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Cygnus\ Solutions/Cygwin/mounts\ v2'/usr/bin', which any Cygwin program (including bash) will choke on. Yep, sorry for wrong posts. I mixed that up with FAT/NTFS limitations. Which have nothing to do with our proc_fs. If the findutils maintainer decides to add a /proc/registry patch to make '*' a valid filename char, other fileutils should be fixed also. ls and cat at least. So it should be better fixed in cygwin. How? Make it a valid file character there? How not to break all other file-,find-,text-,shellutils then, which will have to deal with this and glob expansion. Replace it by some other character? Which? If there's a solution, it should probably have something in common with managed mounts... Just a simple find patch is needed. -- Reini Urban -- 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: Error with managed mount point.
-Original Message- From: cygwin-owner On Behalf Of Mark Paulus Sent: 16 December 2004 14:32 No, they need to be removed. Windows behavior is to ignore one or more '.'s at the end of a file so we're stuck with that in normal Cygwin-working mode. I actually haven't delved into the inner workings of the managed mount option code but if there's going to be a place to hang onto and translate the trailing '.'s, it would be in this special case code. Without looking at more than just the patch lines, I'm guessing that the patch you made (submitted to the Cygwin patches list) to path_conv::check() are going to be in too generic of a spot to be the right thing to do for just managed mount mode, though I could be wrong. I'll try to find a minute tonight to comment further. I am going to have to disagree with you on this point. If you are going to have a truly managed filesystem, then it needs to handle all characters, and not arbitrarily remove/drop any characters. I believe he was only disagreeing with you about where the patch should be made, not about the issue that trailing dots should be handled. cheers, DaveK -- Can't think of a witty .sigline today -- 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: Setup: 'Download From Internet' creates 'c:/cygwin/etc/setup'
George wrote: Internet Option'. Files were saved to the root of a currently empty D:/ partition. Ordinarily I'd just delete the 'c:/cygwin/etc/setup' dirs and files as they seem to contain summmary download-specific information, but I'm wondering why this folder was created where it was. Maybe if I had selected 'Install from Internet' and picked 'c:/cygwin' (on this machine) for the installation directory (neither of which is the case), it might make more sense. Since you selected Download only then setup bypassed the question for the Root Directory for the install but defaulted to C:\cygwin and as you point out the C:\cygwin\etc\setup directory has summary download and log information for the install. It would normally place it whereever you installed Cygwin but since this was a download only - it had to assume where that might be. I remember seeing this before and wondered where else we might place these setup files when it is a download only - at one time I beleive these were actually kept as part of the download directory and then later moved to /etc/setup but I am not 100% on that. bk -- 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/
cdecl for cygwin
Hello dear forum participants, there is no default cdecl in default cygwin distribution, so I tried to get and compile one myself, I run there in problems with mismatch of declaration in functions getopt and setprogname. Before I start to tweak the declarations and/or includes -- the question: Has anyone succesfully built the cdecl for cygwin already? With Best Regards Ariel Burbaickij -- 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: Setup: 'Download From Internet' creates 'c:/cygwin/etc/setup'
On Thu, Dec 16, 2004 at 11:15:05AM -0500, Brian Keener wrote: George wrote: Internet Option'. Files were saved to the root of a currently empty D:/ partition. Ordinarily I'd just delete the 'c:/cygwin/etc/setup' dirs and files as they seem to contain summmary download-specific information, but I'm wondering why this folder was created where it was. Maybe if I had selected 'Install from Internet' and picked 'c:/cygwin' (on this machine) for the installation directory (neither of which is the case), it might make more sense. Since you selected Download only then setup bypassed the question for the Root Directory for the install but defaulted to C:\cygwin and as you point out the C:\cygwin\etc\setup directory has summary download and log information for the install. It would normally place it whereever you installed Cygwin but since this was a download only - it had to assume where that might be. I remember seeing this before and wondered where else we might place these setup files when it is a download only - at one time I beleive these were actually kept as part of the download directory and then later moved to /etc/setup but I am not 100% on that. Thanks for the comments, Brian. What you say makes perfect sense, though my own opinion is that a 'download only' should be self-contained to avoid putting a user in a position where he's left wondering why there's a a mostly empty 'c:/cygwin' folder when he's installed it in, say, 'd:/cygwin'. Either way, no big deal. I'll go ahead and delete the dirs/files. -- George -- 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: 1.5.7: problem using rexec and Windows batch files
JP wrote: Hi. I've installed Cygwin 1.5.7 on a Windows 2000 server. I'd like to ... So, am I missing something here as far as my config/setup goes? The Cygwin THe very first thing you should do is use the current version of Cygwin. 1.5.7 is about five (likely soon to be six) releases old. Many bugs are fixed in each release, and I don't think anyone here would appreciate helping you any further only to discover that it was a bug fixed months ago. So the first thing to do is install the current version of all packages on your Cygwin install, using the setup.exe app. This list does not have the resources to support anything but the current version. 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: Piping output from sqlplus
At Thursday, December 16, 2004 3:57 PM, Chuck wrote: Buchbinder, Barry (NIH/NIAID) wrote: At Thursday, December 16, 2004 3:29 PM, Chuck wrote: I'm having a strange problem reading the output from sqlplus in Cygwin. Sqlplus is a windows command line program used to access oracle databases. My command looks something like this... sqlplus -s ! | read line user/[EMAIL PROTECTED] set pagesize 0 linesize 200 feedback off tab off select col1||chr(9)||col2 from table; ! This should output one line to stdout with the two values separated by a tab character. The read command should read it into the variable $line. On my Solaris system it works perfectly. In Cygwin, $line is empty. If I remove the read line, the output displays on the tty just fine. I though it might be related to the line end characters so I tried converting them with the dos2unix filter. Didn't work. Neither did tr -d \\r. Both ways, $line still ends up being empty. If I replace the read line with od -c to dump the characters, it shows the one line as expected. If I redirect the output to a file, the file contains one line as expected. If I try to read the output into a variable, I get an empty variable Any ideas? If the output shows up OK in a file, do VAR=$(cat file) That may work but it misses the point. I'm writing a script and I want it to work on Cygwin and unix. BTW the shell I'm using is ksh. Well, I don't have access to a Unix or Linux machine, but I would have thought outputting a file and filing the variable by cat'ting it would work there, too. I don't use ksh. If what I suggested does not work there, something like the following should. VAR=`cat file` If the trailing \n gets converted into an undesirable space, you could always do VAR=`cat file | tr -d '\n'` -- 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: 1.5.7: problem using rexec and Windows batch files
Hi. I've installed Cygwin 1.5.7 on a Windows 2000 server. I'd like to ... So, am I missing something here as far as my config/setup goes? The Cygwin THe very first thing you should do is use the current version of Cygwin. 1.5.7 is about five (likely soon to be six) releases old. Many bugs are fixed in each release, and I don't think anyone here would appreciate helping you any further only to discover that it was a bug fixed months ago. So the first thing to do is install the current version of all packages on your Cygwin install, using the setup.exe app. This list does not have the resources to support anything but the current version. Brian Fair enough. I thought someone would suggest that, but I was banking on it not being a bug. I'll give the upgrade a shot. Thanks for the response, JP -- 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/
