Re: Doxygen
When I want to compile doxygen, I must setup libpng and qt library and .., It's a troublesome. I expec that This is the reason is why doxygen soruce include libpng and qt library. By in setup.exe we have a (shared, AFAIR) libpng libreary... using it would reduce both source and binary package, and moreover would solve bugs like when libz had problems and everyone included it statically in a local copy... Just my 2 eurocents. Lapo -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796)
Re: Doxygen
On Sat, 5 Oct 2002, Ryunosuke Satoh wrote: I don't understand what do you want to show with that exmaple ? Please, give more details. _WIN32 is not defined on Cygwin, so gswin32c.exe should not be picked up if everything is set up correctly. See below the output of gcc -v on Cygwin: _WIN32 is used for VC++. Doxygen can be compiled with VC++. If _WIN32 is undefined, fail to compile. Doxygen use Qt library for dealing with string. (See qtools dir) --- In file included from qiodevice.h:42, from qbuffer.h:42, from qbuffer.cpp:38: qglobal.h:132: #error Qt has not been ported to this OS - talk to qt-bugs@troll tech.com --- I don't want to edit Qt library's headers. For compiling Qt library, I define _WIN32. I'll let someone else, more experienced than me, comment on this, but IMO you're not doing the right thing. The following simple change allows the qtools subdirectory to be compiled without any complints on Cygwin without having to define _WIN32: #elif defined(__CYGWIN__) #define _OS_CYGWIN_ #else #error Qt has not been ported to this OS - talk to [EMAIL PROTECTED] #endif Do you have a reason to avoid a patch like this ? Then again - you do not define D_WIN32 only for qtools subdir, but also for the src subdir. This means that anycode in the main doxygen body which has #ifdef _WIN32 clause in it will choose to use the wrong branch. Or if you really want to use the _WIN32 code then add to the #ifdef _WIN32 also a check for __CYGWIN__. But this should be done on your prior knowledge that this is really the way it must be done. Ie you have to check the source by yourself and decide where _WIN32 is needed and where not. The way you're doing it now, again IMO, will spread confusion to anyone who is using the source package. I think if I'm a VC++ user on Windows, When I want to compile doxygen, I must setup libpng and qt library and .., It's a troublesome. I expec that This is the reason is why doxygen soruce include libpng and qt library. Well, you choose to be a port maintainer :) Then maintain it! :) Anyway, I am saying it again - it is not a showstopper... but it would be nice to have it linked against the dll. It'll save some space and also will utilize the work of other peoples which spent time on portin libpng to Cygwin and made it possible to build it as dll.
RE: Doxygen
Do you have a reason to avoid a patch like this ? Then again - you do not define D_WIN32 only for qtools subdir, but also for the src subdir. This means that anycode in the main doxygen body which has #ifdef _WIN32 clause in it will choose to use the wrong branch. Or if you really want to use the _WIN32 code then add to the #ifdef _WIN32 also a check for __CYGWIN__. But this should be done on your prior knowledge that this is really the way it must be done. Ie you have to check the source by yourself and decide where _WIN32 is needed and where not. You should not be using _WIN32 in the Cygwin port because the Qt library will not deal with UNIX filenames properly. You can use the version of the Qt files from kde-cygwin and copy those over the files in doxygen. That should work. Chris
Re: Doxygen
I think if I'm a VC++ user on Windows, When I want to compile doxygen, I must setup libpng and qt library and .., It's a troublesome. I expec that This is the reason is why doxygen soruce include libpng and qt library. Well, you choose to be a port maintainer :) Then maintain it! :) Anyway, I am saying it again - it is not a showstopper... but it would be nice to have it linked against the dll. It'll save some space and also will utilize the work of other peoples which spent time on portin libpng to Cygwin and made it possible to build it as dll. I tried compiling with the Cygwin supplied libpng package and doxygeb compiled and linked just fine (to the dll version). What I did was just to follow the instructions in /usr/doc/Cygwin/libpng12-devel-*.README. So I think it is worth to build that way. I can send you my Makefile.doxy* and Makefile.libdoxy* if you want to take a look at the compiler and linker flags I've used.
Re: Doxygen
I tried compiling with the Cygwin supplied libpng package and doxygeb compiled and linked just fine (to the dll version). What I did was just to follow the instructions in /usr/doc/Cygwin/libpng12-devel-*.README. So I think it is worth to build that way. I can send you my Makefile.doxy* and Makefile.libdoxy* if you want to take a look at the compiler and linker flags I've used. Thank you very much. I see I'm wrong. Anyway, I am saying it again - it is not a showstopper... but it would be nice to have it linked against the dll. It'll save some space and also will utilize the work of other peoples which spent time on portin libpng to Cygwin and made it possible to build it as dll. If you are saying doxygen must link against the dll and exclude libpng sources, it' out of my competence. I will link on cygwin platform only. OK? Ryu
Re: Doxygen
On Sun, 6 Oct 2002, Ryunosuke Satoh wrote: I tried compiling with the Cygwin supplied libpng package and doxygeb compiled and linked just fine (to the dll version). What I did was just to follow the instructions in /usr/doc/Cygwin/libpng12-devel-*.README. So I think it is worth to build that way. I can send you my Makefile.doxy* and Makefile.libdoxy* if you want to take a look at the compiler and linker flags I've used. Thank you very much. I see I'm wrong. Just to clarify something - it wasn't my intention to point a finger at you and say You are wrong or something like this. I just wanted to point that there is an alternative (better) solution. Anyway, I am saying it again - it is not a showstopper... but it would be nice to have it linked against the dll. It'll save some space and also will utilize the work of other peoples which spent time on portin libpng to Cygwin and made it possible to build it as dll. If you are saying doxygen must link against the dll and exclude libpng sources, it' out of my competence. I will link on cygwin platform only. OK? I don't understand what are you saying here - please explain. Are you going to link agains cygpng12.dll or not ? :) What does it mean that you will link on cygwin platform only ?
Re: Doxygen
If you are saying doxygen must link against the dll and exclude libpng sources, it' out of my competence. I will link on cygwin platform only. OK? I don't understand what are you saying here - please explain. Are you going to link agains cygpng12.dll or not ? :) What does it mean that you will link on cygwin platform only ? I'm going to link, but I have no competence of excluding libpng source files from doxygen. Ryu
RE: Doxygen
Do you have a reason to avoid a patch like this ? Then again - you do not define D_WIN32 only for qtools subdir, but also for the src subdir. This means that anycode in the main doxygen body which has #ifdef _WIN32 clause in it will choose to use the wrong branch. Or if you really want to use the _WIN32 code then add to the #ifdef _WIN32 also a check for __CYGWIN__. But this should be done on your prior knowledge that this is really the way it must be done. Ie you have to check the source by yourself and decide where _WIN32 is needed and where not. You should not be using _WIN32 in the Cygwin port because the Qt library will not deal with UNIX filenames properly. You can use the version of the Qt files from kde-cygwin and copy those over the files in doxygen. That should work. I have tried, it could be compiled out of the box with qt 2.3 including doxywizard. Ralf
Re: Doxygen
Cygwin has qt 2.3 package? I can't see qt2.3 in the list of setup.exe. I have tried, it could be compiled out of the box with qt 2.3 including doxywizard. Ralf Ryu
qt package for Cygwin [was RE: Doxygen]
Cygwin has qt 2.3 package? I can't see qt2.3 in the list of setup.exe. http://kde-cygwin.sourceforge.net Chris
Re: Doxygen
Updated. http://www.geocities.co.jp/SiliconValley-SanJose/5153/cygwin-package/doxygen-1.2.18-1-package.tgz CHANGES: link (-Lpng.dll) removed _WIN32 Thanks for many advice. setup.hint: sdesc: Doxygen is a documentation system for C++, C, Java, IDL (Corba, Microsoft, and KDE-DCOP flavors) and to some extent PHP. ldesc: Doxygen is a documentation system for C++, C, Java, IDL (Corba, Microsoft, and KDE-DCOP flavors) and to some extent PHP. category: Devel requires: cygwin libpng12 I'm not certain the requires line is correct. libpng12 or libpng12-devel? Ryu
Re: x apps cant start from bash
Solved my own problem; sorry to bother y'all FTR, the solution is that a) if the DISPLAY variable in bash is set without export, then when SSH starts up its not noticed, and then SSH does not notice where to send the X11 stream b) you have to set and export the display variable, it is neither set automatically, nor does ssh have a default. I'm a tcsh user, so didnt realize that necessity under bash. This seems to be covered in the SSH notes message, sorry I didn't see that before. Rupert B On Sat, 5 Oct 2002, Rupert Brooks wrote: Hi - having a strange problem here. Just installed a fresh install of Cygwin / Xfree. startxwin.bat works, and an xterm appears. From that xterm I can start other xapps and they work. BUT, from another cygwin bash shell, started independently, I get the following error xterm XT error: Can't open display: I have tried with numerous variations in the DISPLAY variable localhost:0 localhost:0.0 127.0.0.1:0 127.0.0.1:0.0 192.168.1.150:0.0 etc I have done a tracert on all those addresses, and my routing seems ok, that is packets for the localhost don't get routed out into the network where the router might frig with them. Xwin.log shows no signs of having refused the connections. So I am guessing that the request never made it to the Xserver. The problem I am ultimately trying to solve, is to get a remote connection tunnelled over openSSH or putty. I have that setup on another machine, and working well. there are two differences with this machine - this OS is WinME not Win2K, and this one lives behind a LinkSys router. Anyway, I think I should get the local set up working right first before trying to diagnose the SSH part. I don't see, though, why the router should stop packets from the localhost. There is no firewall software on this machine. Has anyone seen this before? Can anyone suggest where else to look? Thanks much Rupert B. -- -- Rupert Brooks McGill Centre for Intelligent Machines (www.cim.mcgill.ca) PhD. Student http://www.cyberus.ca/~rbrooks [EMAIL PROTECTED] ICQ: 27978014 CELL: 6137997873 SMS: send short mail to CELL#@pcs.rogers.com
RE: x apps cant start from bash
Rupert, Hey, we like users that solve their own problems, we would like you to stick around :) Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rupert Brooks Sent: Saturday, October 05, 2002 4:00 PM To: [EMAIL PROTECTED] Subject: Re: x apps cant start from bash Solved my own problem; sorry to bother y'all FTR, the solution is that a) if the DISPLAY variable in bash is set without export, then when SSH starts up its not noticed, and then SSH does not notice where to send the X11 stream b) you have to set and export the display variable, it is neither set automatically, nor does ssh have a default. I'm a tcsh user, so didnt realize that necessity under bash. This seems to be covered in the SSH notes message, sorry I didn't see that before. Rupert B On Sat, 5 Oct 2002, Rupert Brooks wrote: Hi - having a strange problem here. Just installed a fresh install of Cygwin / Xfree. startxwin.bat works, and an xterm appears. From that xterm I can start other xapps and they work. BUT, from another cygwin bash shell, started independently, I get the following error xterm XT error: Can't open display: I have tried with numerous variations in the DISPLAY variable localhost:0 localhost:0.0 127.0.0.1:0 127.0.0.1:0.0 192.168.1.150:0.0 etc I have done a tracert on all those addresses, and my routing seems ok, that is packets for the localhost don't get routed out into the network where the router might frig with them. Xwin.log shows no signs of having refused the connections. So I am guessing that the request never made it to the Xserver. The problem I am ultimately trying to solve, is to get a remote connection tunnelled over openSSH or putty. I have that setup on another machine, and working well. there are two differences with this machine - this OS is WinME not Win2K, and this one lives behind a LinkSys router. Anyway, I think I should get the local set up working right first before trying to diagnose the SSH part. I don't see, though, why the router should stop packets from the localhost. There is no firewall software on this machine. Has anyone seen this before? Can anyone suggest where else to look? Thanks much Rupert B. -- -- Rupert Brooks McGill Centre for Intelligent Machines (www.cim.mcgill.ca) PhD. Student http://www.cyberus.ca/~rbrooks [EMAIL PROTECTED] ICQ: 27978014 CELL: 6137997873 SMS: send short mail to CELL#@pcs.rogers.com
src/winsup/w32api/include/ddk
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2002-10-05 05:28:09 src/winsup/w32api/include/ddk Update of /cvs/src/src/winsup/w32api/include/ddk In directory sourceware.cygnus.com:/sourceware/cvs-tmp/cvs-serv30078/ddk Log Message: Directory /cvs/src/src/winsup/w32api/include/ddk added to the repository
src/winsup/w32api/lib/ddk
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2002-10-05 05:32:57 src/winsup/w32api/lib/ddk Update of /cvs/src/src/winsup/w32api/lib/ddk In directory sourceware.cygnus.com:/sourceware/cvs-tmp/cvs-serv31443/ddk Log Message: Directory /cvs/src/src/winsup/w32api/lib/ddk added to the repository
winsup/cygwin thread.cc
CVSROOT:/cvs/uberbaum Module name:winsup Changes by: [EMAIL PROTECTED] 2002-10-05 10:47:25 Modified files: cygwin : thread.cc Log message: whitespace Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/cygwin/thread.cc.diff?cvsroot=uberbaumr1=1.99r2=1.100
winsup/cygwin ChangeLog cygthread.cc exceptions.cc
CVSROOT:/cvs/uberbaum Module name:winsup Changes by: [EMAIL PROTECTED] 2002-10-05 18:01:58 Modified files: cygwin : ChangeLog cygthread.cc exceptions.cc Log message: * cygthread.cc (cygthread::stub): Very minor cleanup. (cygthread::stub): Report overflows in cygwin thread pool when DEBUGGING is on and special environment variable is not set. (cygthread::terminate): Set event only when event actually exists. * exceptions.cc (signal_exit): Set priority of main thread to low before setting current thread to high. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/cygwin/ChangeLog.diff?cvsroot=uberbaumr1=1.1517r2=1.1518 http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/cygwin/cygthread.cc.diff?cvsroot=uberbaumr1=1.9r2=1.10 http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/cygwin/exceptions.cc.diff?cvsroot=uberbaumr1=1.126r2=1.127
Re: gawk not taking redirected input under command.com
- Original Message -
From: Barry Buchbinder [EMAIL PROTECTED]
To: Cygwin [EMAIL PROTECTED]
Sent: Friday, October 04, 2002 1:55 PM
Subject: RE: gawk not taking redirected input under command.com
I get the same problems under under win95cmd.exe. It
fails with redirection but not reading input from a
file:
C:\ c:\cygwin\bin\gawk -f t autoexec.bat
gawk: t:3: fatal: file `-' is a directory
Running under strace and back under command.com I get
the following:
C:\ type t | c:\cygwin\bin\strace -o strace.out
c:\cygwin\bin\gawk -f t
gawk: t:3: fatal: file `-' is a directory
I've attached strace's output.
Might the fact that the line number quoted is *after*
the end of the file tell us something? (t has 2 lines
but the error is in line 3. When the script is on the
command line, the error is in line 2.)
Thanks again,
- Barry Buchbinder
On my system (Win98SE) using Win95Cmd I get (with Cygwin gawk-3.1.1-3):
C:\WINDOWS\cygwin\bin\gawk BEGIN {print \hi\}; END {print \bye\}
\autoexec.bat
hi
gawk: cmd. line:1: fatal: file `-' is a directory
C:\WINDOWS
OTOH:
C:\WINDOWS\cygwin\bin\gawk BEGIN {print \hi\};END {print \bye\}
\autoexec.bat
hi
bye
C:\WINDOWS
works fine.
I don't get this problem if I run the GNUWin32 port of gawk-3.1.0-2 or
the DJGPP version of gawk-3.1.1 at a Win95Cmd command line. So it looks
like there's problem with the Cygwin port running under command.com or
win95cmd somewhere. I suppose it isn't something to do with the cygwin
dlls not being in the path? Although I'd expect some missing dll
messages if that were the case.
Peter S Tillier[EMAIL PROTECTED]
__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
RE: Tk?
Tiller, Jason [EMAIL PROTECTED] wrote around 04 Oct 2002 ADBFFED9CB40D5118C5A0008C7864BA10185AE2C@USSVML03:">news:ADBFFED9CB40D5118C5A0008C7864BA10185AE2C@USSVML03: Enjoy, and thanks to everyone who made this possible! You're welcome ;-) And yes, just to clarify, to the O.P.; this Perl Tk is using native Windows GUI interfaces, *not* any X server interface. That's feasible and dictated by the way the Tk-Perl extension is set up: at build time, one gets to make a choice of which configuration to create. So just because it is built to and extends cygwin perl, doesn't dictate that it must use a cygwin port of X (XFree86). Soren A -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Patch to get bc 1.06 to compile under Cygwin with readline library.
Francis Litterio [EMAIL PROTECTED] wrote around 03 Oct 2002
[EMAIL PROTECTED]:">news:[EMAIL PROTECTED]:
I downloaded and installed the Cygwin source code to bc 1.06, but it
would not build under Cygwin 1.3.12-2 when {...}
Thanks for your posting. 'bc' is a useful tool and sometimes shell
scripts just don't come together at all easily without it.
I cannot verify the need for or methodology of your patch, yet, but
thanks for posting.
Best,
Soren A
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Tk?
Hallo Jason, Am Freitag, 4. Oktober 2002 um 21:02 schriebst du: Hi, Steve, :) Wow, I get to post to the Cygwin list! Rare! :) From: Steve Landry [mailto:[EMAIL PROTECTED]] If I want to run or write Perl/Tk apps that run as Windows apps (not in the X environment), can I do that w/Cygwin Perl or do I need to run ActiveState as well? Gerrit P. Haase has packaged up a binary distribution of Tk800.023 for Cygwin perl that uses native Windows GUI calls so it doesn't rely on X. I've been using it for a short while and it seems to meet all of my needs. I found Gerrit's package here: http://www.perltk.org/binaries/ Hey, cool, I didn't know that it is available there! This version is linked against perl-5.6.1, Soren Anderson has managed to build later versions of TK and has also logs at his site, unfortunately I couldn't reproduce it for perl-5.8 :-( The original location of Tk for perl 5.6.1 is here (including the patch and the origional sources and a short README): ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/porters/Haase_Gerrit/1.3/perl/ Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: executing perl from command line (cygwin)
Hallo Smithesh, Am Samstag, 5. Oktober 2002 um 01:34 schriebst du: Hi Peter, Like Mark said cygwin perl is a much better option. I use it quite often. I think you still can execute active perl or any windows executable on Cygwin. Make sure you are escaping '\' by '/' on the directory paths. For e.g., if you are trying to execute something on your windows at C:\Sample\pscp.exe. Then you will do the following on your cygwin prompt admin@TMLA_SRAMACHAND ~ C:/\Sample/\pscp.exe The problem with ActiveStates Perl is that it knows nothing about Cygwin paths. If you want to read a file '/usr/test/text.txt' with ActiveState Perl you need to translate the paths to Windows syntax (- 'C:\cygwin\usr\test\text.txt'). There are tools included with Cygwin to help with this (cygpath.exe), but it is a pita. Cygwin Perl is linked against cygwin1.dll and all this translation is done automatically for you. Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
invalid user?
Hallo, I installed sshd as 'cygrunsrv -I sshd -p /usr/sbin/sshd -a -D -d' - which worked. The server starts (cygrunsrv -S sshd) properly. Then I tried to connect: ssh localhost -l Uwe Mayer Where Uwe Mayer is my regular W2k login. The following is what was printed to the /var/log/sshd.log: Connection from 127.0.0.1 port 1605 [..snip..] debug1: attempt 0 failures 0 input_userauth_request: illegal user Uwe Mayer Failed none for illegal user Uwe Mayer from 127.0.0.1 port 1605 ssh2 debug1: userauth-request for user Uwe Mayer service ssh-connection method publickey debug1: attempt 1 failures 1 Failed publickey for illegal user Uwe Mayer from 127.0.0.1 port 1605 ssh2 debug1: userauth-request for user Uwe Mayer service ssh-connection method keyboard-interactive debug1: attempt 2 failures 2 debug1: keyboard-interactive devs debug1: auth2_challenge: user=Uwe Mayer devs= debug1: kbdint_alloc: devices '' Failed keyboard-interactive for illegal user Uwe Mayer from 127.0.0.1 port 1605 ssh2 debug1: userauth-request for user Uwe Mayer service ssh-connection method password debug1: attempt 3 failures 3 Failed password for illegal user Uwe Mayer from 127.0.0.1 port 1605 ssh2 debug1: userauth-request for user Uwe Mayer service ssh-connection method password debug1: attempt 4 failures 4 Failed password for illegal user Uwe Mayer from 127.0.0.1 port 1605 ssh2 debug1: userauth-request for user Uwe Mayer service ssh-connection method password debug1: attempt 5 failures 5 Failed password for illegal user Uwe Mayer from 127.0.0.1 port 1605 ssh2 Connection closed by 127.0.0.1 debug1: Calling cleanup 0x41c9c0(0x0) debug1: Calling cleanup 0x41c9c0(0x0) ... what does illegal user mean? Doesn't it like the space in my login name? Is there any way arround it? My guess is that even supplying an alternative to the /etc/passwd file (i.e. U-uwe) won't permit me to login as ssh localhost -l uwe or? Can somebody please help me here? Thanks in advance Uwe mailto:[EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
md5sum : strange error message : invalid option
I'm getting a strange error message from md5sum: the command has worked fine in the past. It looks like this: ~ md5sum `find /cygdrive/c/WINDOWS/Desktop` md5sum: invalid option -- M Try `md5sum --help' for more information. ~ There's no problem with md5sum `find .` for example. I can't see anything odd about my desktop, or files on it or under it. In particular, nothing beginning with a upper-case M. Any ideas? Fergus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: md5sum : strange error message : invalid option
I'm getting a strange error message from md5sum: the command has worked fine in the past. It looks like this: ~ md5sum `find /cygdrive/c/WINDOWS/Desktop` md5sum: invalid option -- M Try `md5sum --help' for more information. ~ There's no problem with md5sum `find .` for example. I can't see anything odd about my desktop, or files on it or under it. In particular, nothing beginning with a upper-case M. Does it have a file name with an embedded hyphen, maybe? Something like: /cygdrive/c/WINDOWS/Desktop/Data -Modified.lnk -- Cliff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: md5sum : strange error message : invalid option
Does it have a file name with an embedded hyphen, maybe? Something like: /cygdrive/c/WINDOWS/Desktop/Data -Modified.lnk Absolutely right. Thank you. Fergus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: General Question - support for Windows DDKs, specifically SPTI
Hi folks - hope I'm not wasting anybody's bandwith here, but I've spent quite some time trapsing through docs and archives and source code and haven't come up with a lot of answers and just a little insight. (If yer busy, you may want to skip to the end - between here and there simply lies a verbose description of why I'm asking those questions - or perhaps it's a bit of venting. :-) My goal is to make use of the SCSI Pass-thru Interface on Windows (SPTI) from programs compiled in and running within the Cygwin environment. (I'm a U*x-type programmer, and this stuff will be ported to many different OSs - Solaris, Linux, Digital Unix, as well as Windows NT, 2k and XP (and who knows what others :-). So, I wanted to use cygwin to protect my fairly simple source code from the, um, intricacies of having common code betwixt Windows and Unix.) My initial take was to (somehow) recreate the appropriate structures and values and simply call ioctl() after opening the SCSI device. Needless to say, after seeing what ioctl actually boiled down to in this case (in fhandler.cc), I saw this approach wasn't going to work well. (That actually makes sence to me - ioctl() doesn't map very well to DeviceIoControl, with things appearantly being bi-direction in the Windows side.) So, my next take was to actually use CreateDevice() and DeviceIoControl() within my code; and, lo and behold, it actually compiled and ran. (Whee!) However, once I established that fact, I went on to try and include the SPTI structure and ioctl definitions, which seeming are not covered in the cygwin headers (or, at least, not completely ...) This got me into the Windows DDK mess - who knows which ones (NT DDK, Win2k DDK, MEDDK, ack!) are supported on which platform, and they disagree is a lot of places, and they're all turning into the Windows DDK this month, anyway (which purportedly works for all platforms; I'm thinking it's more like moving all the problems under one include directory, but what do I know. :-) In any case, the amount of success I have depends entirely on which headers I include from which DDK on whatever plaform I happen to be on at the moment. I had managed to craft things such that I could #include files for the IOCTL_SCSI_GET_ADDRESS ioctl to work on NT 4.0 (using the NT DDK) and on WinXP (sing the Win2K DDK). (This feat worked 'cuz all that's needed are NTDDSCSI.H - from the DDK - and winioctl.h, from cygwin.) As a general rule I would advise using the latest DDK and checking by hand you aren't using APIs that don't exist in the older versions of Windows you want to target. The newer DDKs tend to include more structure definitions, bug fixes, etc. I then moved on to try the IOCTL_GET_DEVICE_NUMBER - not so good. On NT, the fault lies with the NT DDK - the STORAGE_DEVICE_NUMBER structure isn't defined anywhere. After I crafted my own, it seemed to work (or at least compile.) On WinXP/W2KDDK, I ran into a different problem: including NTDDSTOR.H, where the STORAGE_DEVICE_NUMBER is defined, causes a redefinition of the PREVENT_MEDIA_REMOVAL structure, which I was surprised to find was defined in a cygwin header! (/usr/include/w32api/winioctl.h, to be precise.) Note that the DDK includes are not designed to be included at the same time as the Win32 includes. That's probably why you saw a redefinition. The solution that Gary Nebbett (and probably others) came up with was to include the DDK includes within a separate namespace. This is the only way I've seen to allow them to co-exist with the Win32 ones without major editing. It is now pretty clear to me that there is some very limited support in cygwin for standard Windows device interfaces like the SPTI (although the word standard doesn't belong anywhere near Windows - their different DDKs don't support or define the same things!) Now, I'm quite sure I can get this all to work by crafting my own headers, essentially translating what I need from whichever DDK seems to be working at the time; heck, I could even try to write a script to do it. (That leaves me a bit at the mercy of changes in the DDK headers; every time it changes, I have to recraft my headers. Not that cygwin would be in a different boat ...) But this (finally!) leads to my questions: The presence of a define in a header is not indication of support. The w32api includes simply aim to be a free replacement of the Microsoft Win32 includes. They are pretty separate from Cygwin in most ways, other than that Cygwin depends on them. (1) To what extent does the cygwin environment intend to support interfaces like SPTI, if at all, within it's own compilation environment? Having PREVENT_MEDIA_REMOVAL in there implies some kind of support for DDK interfaces, but was it done to the end of supporting a larger interface definition, or simply to get what's needed now into cygwin? AFAIK, Cygwin doesn't really support SPTI at all. Feel
crontab: no changes made
Hi, When I start crontab -e it won't run, because I haven't vi installed. I remembered reading something about an EDITOR or VISIBLE environment variable, though I couldn't find it any more. Thus I set export EDITOR=emacs Then crontabs starts up emacs, editing a temporary file (i.e. /tmp/cron.1900) However, when I close emacs (with or without saveing changes to the tmp file) crontab displays crontab: no changes made to crontab. Where's the flaw? Thanks Uwe -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Porting software from Red Hat Linux to Cygwin
I believe someone is working on rpm (search the list archives.) for telnetd and rshd etc just install the inetutils package in the net category. -Original Message- From: Gregg C Levine [mailto:[EMAIL PROTECTED]] Sent: 05 October 2002 01:16 To: [EMAIL PROTECTED] Subject: Porting software from Red Hat Linux to Cygwin Hello from Gregg C Levine Obviously people are actively porting software from the library of software, that was written for Linux, to Cygwin. On this list, several people have mention the rpm program. Was it a successful build? And does it work? And where can I obtain a copy? Also, what about the telnet server daemon that Red Hat makes available for its Linux distribution, has anyone taken a shot at porting it to Cygwin? It happens I happen to need a copy of the program for my work. That also includes several other daemons. Rsh, and one other spring to mind. Gregg C Levine [EMAIL PROTECTED] Oh my! The Second Doctor's nearly favorite phrase. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Tk?
Gerrit P. Haase [EMAIL PROTECTED] wrote around 05 Oct 2002 [EMAIL PROTECTED]:">news:[EMAIL PROTECTED]: This version is linked against perl-5.6.1, Soren Anderson has managed to build later versions of TK and has also logs at his site, unfortunately I couldn't reproduce it for perl-5.8 :-( Hmm! I wonder what was the obstacle. Anyway, you mentioned my site but a reader might wonder 'where?' (although really should be able to find the past List messages by searching the archive, granted). So here's a url: http://home.att.net/~perlspinr/perlproj/pTk/index.html Regards, Soren A -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gawk not taking redirected input under command.com
On Wed, Oct 02, 2002 at 08:14:26AM -0700, Barry Buchbinder wrote: It's definitly cygwin's gawk doing it. C:\ c:\cygwin\bin\gawk -f t autoexec.bat GAWK: t:3: fatal: file `-' is a directory I'm not sure how or why this was fixed, but it seems like this is fixed in the current cygwin snapshots and so will be fixed in the 1.3.13 release. We're still having some problems with the DLL, though, so I don't have an ETA for the official release. In the meantime, try a snapshot: http://cygwin.com/snapshots/ . cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
copying installed CYGWIN
Hi! I have installed CYGWIN on one computer in c:\cygwin. I transfered this directory to another computer, but when i run cygwin.bat, it doesn't work. Are there some items in Registry or something based on PATH which must be transfered too? Thank you. David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
FYI: sed-3.95
Hallo, just built sed-3.95, All tests pass, though I did not test how it behaves on textmounts. Now I wonder if the sed included with the Cygwin net release has/had issues with CR/LF thingies and if 3.02 is linked against automode.o. No patches needed: ftp://alpha.gnu.org/gnu/sed/sed-3.95-fixed.tar.gz See also the announcement: http://sources.redhat.com/ml/libc-alpha/2002-10/msg00025.html Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Tk?
Hallo Soren, Am Samstag, 5. Oktober 2002 um 19:32 schriebst du: Gerrit P. Haase [EMAIL PROTECTED] wrote around 05 Oct 2002 [EMAIL PROTECTED]:">news:[EMAIL PROTECTED]: This version is linked against perl-5.6.1, Soren Anderson has managed to build later versions of TK and has also logs at his site, unfortunately I couldn't reproduce it for perl-5.8 :-( Hmm! I wonder what was the obstacle. I got some undefined references which I wasn't able to resolve yet. Anyway, you mentioned my site but a reader might wonder 'where?' [...] http://home.att.net/~perlspinr/perlproj/pTk/index.html Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Question about Running GNU Utilities on Windows XP
Hi, We are running into a problem using the GNU utilities, (specifically TAIL.EXE) on Windows XP when we run them against names that are not in the 8.3 format. For example: The command: tail paratestdatalog.out produces a 'No file or directory' error The command: tail paratestdatalog.gold produces a 'No file or directory' error The command: tail parate~1.gold produces a 'No file or directory' error The command: tail parate~1.out works Is there is an update or do we need to recompile or something? Thanks, Yu Wang __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gawk not taking redirected input under command.com
On Sun, Oct 06, 2002 at 04:28:54AM +1000, Gareth Pearce wrote: I'm not sure how or why this was fixed, but it seems like this is fixed in the current cygwin snapshots and so will be fixed in the 1.3.13 release. We're still having some problems with the DLL, though, so I don't have an ETA for the official release. you must ofcourse realise that its the version number which is causing all the problems .. skip to 1.3.14... Gareth - who just watched Amelie and is in rather twisted mood. I think you're a little confused. 1.3.13 actually solves the problem. That would sort of make sense since I was born on a Friday 13th. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gawk not taking redirected input under command.com
... We're still having some problems with the DLL, though, so I don't have an ETA for the official release. you must ofcourse realise that its the version number which is causing all the problems .. skip to 1.3.14... Gareth - who just watched Amelie and is in rather twisted mood. I think you're a little confused. 1.3.13 actually solves the problem. That would sort of make sense since I was born on a Friday 13th. I think he was suggesting that your DLL problems might clear up if you skipped 1.3.13! If all else fails... -- Cliff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: copying installed CYGWIN
At 01:41 PM 10/5/2002, David =?ISO-8859-2?B?qWlyb2v9?= wrote: Hi! I have installed CYGWIN on one computer in c:\cygwin. I transfered this directory to another computer, but when i run cygwin.bat, it doesn't work. Are there some items in Registry or something based on PATH which must be transfered too? Yes, setup does more than just installing the software. You're better off running setup again on the new machine. Then you don't have to debug your current situation. But if you're interested in pursuing your personalized installation, you can look through the email archives for suggestions. In general, this list can't help people debug their custom installations. It has too much volume to take on discussions about customized installs. Sorry. Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gawk not taking redirected input under command.com
On Sun, Oct 06, 2002 at 01:22:21AM +0100, Cliff Hones wrote: ... We're still having some problems with the DLL, though, so I don't have an ETA for the official release. you must ofcourse realise that its the version number which is causing all the problems .. skip to 1.3.14... Gareth - who just watched Amelie and is in rather twisted mood. I think you're a little confused. 1.3.13 actually solves the problem. That would sort of make sense since I was born on a Friday 13th. I think he was suggesting that your DLL problems might clear up if you skipped 1.3.13! If all else fails... Um, yeah. But it doesn't make a lot of sense, really. 1.3.13 already does solve some problems, so... Nevermind. This discussion is too silly. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
ghostscript 7 textmounts
i reported this bug some time ago: ghostscript 7.05 does not work properly if cygwin is configured to enable textmode-conversations chris faylor already suggested to link against binmode.o (i don't know if this is an easy step, but it sounds easy) the ghostscript-maintainer should take care of this bug. Thx Sven -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Remote mounts unavailable via rsh/rlogin/telnet
Hello, I've read all your postings related to rsh/rlogin, but I've been unable login with write access to my home. My home directory is shared by my Windows boxes, and lives on the Linux machine I'm attempting to come in from. My Windows HOME is k:, which I've mounted by way of Windows: Tools | Map Network Drive Its persistent across logins to Windows and works fine. I install the inetd service thusly: cygrunsrv -I inetd -d CYGWIN inetd -p /usr/sbin/inetd -a -d -e CYGWIN=ntsec and I can rlogin, but remote mounts are UNAVAILABLE. The problem I guess is that all my attempts to mount from the rlogin session, yield a different uid/gid, the simplest is: cmd C:\cygwin net use k: \\Tor\win-kirke I created a symbolic link for /home/kirke - h: And I can rlogin, but: vi ~/.bashrc- yields a readonly session cat it - creates but won't give 'it' size 0 Windows: [kirke@XOR k]$ l .bashrc -rw-r--r--1 kirkeNone 1174 Oct 5 16:15 .bashrc [kirke@XOR k]$ id uid=1003(kirke) gid=513(None) groups=513(None),544(Administrators) via Linux: [kirke@XOR kirke]$ l .bashrc -rwxr--r--1 199381021 1174 Oct 5 16:15 .bashrc* [kirke@XOR kirke]$ id uid=1003(kirke) gid=513(None) groups=0(Everyone),513(None),544(Administrators), 45(Users) I've scoured the mail archives and Google for a couple days, fiddled with --user in starting inetd, and several mount and 'net use' commands no avail. mount -b -s -f \\tor\win-kirke /home/kirke I've placed the Linux machine's name in /etc/hosts.equiv, and in ~/.rhosts - but apparently .rhosts is inaccessible from this angle... Any suggestions appreciated, kirk -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
