Re: glwDrawingAreaWidgetClass
I apologize for being so vague.
I have a fairly large program that I developed on Fedora Linux. It uses
glwDrawingAreaClassRec to create a GL window. I attempted to compile
and run it on Cygwin, and I got the failure.
I added a print statement just before calling XtCreateManagedWidget()
and discovered the value was 0 on Cygwin and an address on Linux. I
presumed that meant there was an issue.
To get around the problem, I downloaded the source from Mesa and
compiled it myself. The .a that was generated identifies the following
(using nm):
0640 D glwDrawingAreaClassRec
0728 D glwDrawingAreaWidgetClass
I then compared it to /lib/libGLw.dll.a and got this:
nm /lib/libGLw.dll.a | grep DrawingAreaClass
I __imp_glwMDrawingAreaClassRec
I __nm_glwMDrawingAreaClassRec
I __imp_glwDrawingAreaClassRec
I __nm_glwDrawingAreaClassRec
Now I tried compiling your test program and found that it did work as
you showed, but I then added the include of GLwDrawA.h, and it fails.
This doesn't make a whole lot of sense to me, and it doesn't seem right.
What do you think? If I want to use the GLwDrawingAreaWidgetClass, I
would presume that I should include the corresponding header file and
the class would be defined.
Thanks for your time, and I really do appreciate you and Cygwin.
Chris Carlson
On 10/7/2014 6:50 AM, Jon TURNEY wrote:
On 07/10/2014 03:31, Chris Carlson wrote:
I've discovered that the constant glwDrawingAreaWidgetClass is set to
0. It's supposed to be defined as:
WidgetClass
glwDrawingAreaWidgetClass=(WidgetClass)glwDrawingAreaClassRec;
Can I ask you to please provide some more details as to how you made
this discovery?
If you do this:
$ cat glw-test.c
#include Xm/Xm.h
#include GL/GLwDrawA.h
#include stdio.h
int main()
{
printf(glwDrawingAreaWidgetClass %p, glwDrawingAreaWidgetClass);
}
then you could reach that conclusion:
$ gcc glw-test.c ; ./a
glwDrawingAreaWidgetClass 0x0
but this isn't testing correctly as glwDrawingAreaWidgetClass isn't
marked as extern in GLwDrawA.h
$ cat glw-test.c
#include Xm/Xm.h
#include stdio.h
extern WidgetClass glwDrawingAreaWidgetClass;
int main()
{
printf(glwDrawingAreaWidgetClass %p, glwDrawingAreaWidgetClass);
}
$ gcc glw-test.c -lGLw ; ./a
glwDrawingAreaWidgetClass 0x5bd8e3640
Is it broken?
I don't know.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Re: X11 crashing - no errors in log file
I also have been getting crashes, but I can't figure out what is causing it. I opened Microsoft Word, and X just crashed in the background. It's happened twice now, but the first time, I can't remember what I did to make it happen. Note that I have Cygwin 1.16 running on a Windows 7 laptop, and I often close the lid to hibernate until later. I started X with -logverbose 3, but I haven't had it crash, yet. I'll send the log when it crashes, presuming it does before I run out of disk space. :-) Chris Carlson On 10/8/2014 11:51 AM, Nem W Schlecht wrote: X11 has been crashing on me in 2 cases since upgrading to 1.16.1-1 1) Using 'xv' on any image. I compiled this myself and it was running fine in the past, but now when I try to open any image, all of X11 crashes. I tried to recompile it, but same issue. Nothing is showing up in the XWin.0.log 2) Using 'rdesktop' to a remote Windows host and then selecting and hitting 'Ctrl-C' on a list of files. About 2 seconds after the Ctrl-C, X11 crashes (again, nothing in XWin.0.log). Is there additional debugging I can turn on to try to catch the error that is happening? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: [ANNOUNCEMENT] Updated: xorg-server-1.16.1-2
No sooner did I respond than I see the update. Nevermind. Chris Carlson On 10/8/2014 8:31 PM, Nem W Schlecht wrote: I just remembered that my version of xv has been modified to place the current image filename in the X11 clipboard. That might have been the cause of the issue. Regardless, my crashes seem to have gone away with this update. Thanks for all the hard work on Cygwin X11! On Wed, Oct 8, 2014 at 3:09 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.16.1-2 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.16.1-1: * Fix transposed format specifiers in some logging added in 1.16.1-1, which is probably the cause of some crashes/hangs (Thanks to Colin Harrison for patch) x86: 2487d4ffba759b3023150298d53616e7 *xorg-server-1.16.1-2-src.tar.xz fba03eb030540c292188c736f410ab77 *xorg-server-1.16.1-2.tar.xz e988cd1a540f3b5a4ebc44619ca340fd *xorg-server-common-1.16.1-2.tar.xz 9b4ccf2d47947820eded95dcc4e855b8 *xorg-server-debuginfo-1.16.1-2.tar.xz 369e9a8ef1d80225d742dec17e69b88e *xorg-server-devel-1.16.1-2.tar.xz a091007b24dd1ae64d4a80be5a3ea279 *xorg-server-dmx-1.16.1-2.tar.xz ba1e3a9cbd7ffe4834b7387a09169528 *xorg-server-extra-1.16.1-2.tar.xz d19cd8a9cd65657c20af1c0f440cd40f *xwinclip-1.16.1-2.tar.xz x86_64: 78666e1511ce24b8786d4cc2697ca71d *xorg-server-1.16.1-2-src.tar.xz de105c6b353d0bc98493a80bc1bfe9d5 *xorg-server-1.16.1-2.tar.xz 5f8b3f6b6c63c7e99bf35a966a5b5252 *xorg-server-common-1.16.1-2.tar.xz 395931026c9f63d7cac23ac433931527 *xorg-server-debuginfo-1.16.1-2.tar.xz 4cfc2b7aac8e7ab18329303f3b378f42 *xorg-server-devel-1.16.1-2.tar.xz 8fa287196a578e4eeb2e8ec57bccf9a9 *xorg-server-dmx-1.16.1-2.tar.xz ae1207c3b901cbb0da96eaf55ff9c8be *xorg-server-extra-1.16.1-2.tar.xz 51a9cb28eaab5ae481aaa45283554e7f *xwinclip-1.16.1-2.tar.xz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
glwDrawingAreaWidgetClass
I'm running Cygwin: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 Cygwin under Windows 7. I've discovered that the constant glwDrawingAreaWidgetClass is set to 0. It's supposed to be defined as: WidgetClass glwDrawingAreaWidgetClass=(WidgetClass)glwDrawingAreaClassRec; Is it broken? Thanks. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem with Cygwin/X from remote Linux
Hello, Jon. The version of Fedora I'm running is: Linux rolf 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I thought the two logs that you requested were a bit large for this e-mail, so I put them on my web site. You can access them as: http://beachware.org/Cygwin/glxinfo.cygwin http://beachware.org/Cygwin/X.log Believe it or not, I just so happen to have an XWin.0.log from my old, old, old version of Cygwin. It was: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.1 grover 1.7.30(0.272/5/3) 2014-05-23 10:36 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601](Win64) Package: version 1.15.1-2 built 2014-05-06 XWin was started with the following command line: X :0 -multiwindow Let me know if there's anything else I can provide. Chris Carlson On 10/2/2014 5:05 AM, Jon TURNEY wrote: On 02/10/2014 04:53, Chris Carlson wrote: I've been using Cygwin on a Windows 7 laptop for a few years as an X server from my Fedora Linux system. I ssh -X to my Linux system and run various X programs (thunderbird, chrome, nautilus, etc.) with very few issues. [...] Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.1.0 OS: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.1-1 built 2014-09-29 XWin was started with the following command line: X :0 -multiwindow I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. There are visuals available to direct connections, but not for remote. Thanks for reporting this problem. Unfortunately, I can't reproduce it. Please can you attach the output of 'X -multiwindow -logverbose 3', so I can see what visuals the server thinks should be available, and the output of running 'glxinfo' on your remote system. Can you give the version of Fedora you are using, and the version of the libGL package you have? I tried looking through the FAQ for answers, but I didn't see anything. Is this something that has intentionally changed? Where would I find it if it is (for future reference so I don't bug you)? No, this is not intentional. I guess this is an unintended consequence of a change. It would be useful in tracking down that change if you could identify the last X server release which worked correctly. The release announce mails are a hopefully accurate summary of intended changes (e.g [1]) [1] https://cygwin.com/ml/cygwin-xfree-announce/2014-09/msg4.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Problem with Cygwin/X from remote Linux
I've been using Cygwin on a Windows 7 laptop for a few years as an X server from my Fedora Linux system. I ssh -X to my Linux system and run various X programs (thunderbird, chrome, nautilus, etc.) with very few issues. Every now and then, I will upgrade Cygwin_64 just to get the latest changes. I hope that the few issues I have will be cleared up. I believe the one issue I have with Thunderbird may be Thunderbird, not Cygwin/X. Anyway, over the past weekend, I upgraded again. The upgrade seemed to go well. No surprises until... One of the things I've been doing is learning OpenGL. I'm converting a sample program that I acquired while working at SGI to OpenGL (it was written in gl, the original SGI graphics language). For the past few months, all of my OpenGL programs have worked fine over the network. Suddenly, with the latest version of Cygwin/X, it doesn't. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.1.0 OS: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.1-1 built 2014-09-29 XWin was started with the following command line: X :0 -multiwindow I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. There are visuals available to direct connections, but not for remote. I tried looking through the FAQ for answers, but I didn't see anything. Is this something that has intentionally changed? Where would I find it if it is (for future reference so I don't bug you)? Thanks, Chris Carlson -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Problem opening remote X applications
I just downloaded Cygwin 64-bit for the first time. I've been using Cygwin 32-bit for years. I'm running on Windows 7, and my Cygwin 32-bit has been working reasonably well for a long time. My only issue with it was a problem it had with my Caps Lock key. For whatever reason, focus would switch windows whenever I pressed the Caps Lock key. The caps would lock, but focus would change. I finally decided to download the latest and greatest to see if it has been fixed. It appears that it is no longer an issue. Now I have a new problem. I usually ssh -X remote to a remote Linux machine. I can then read mail (thunderbird), edit documents (LibreOffice 3.x), run Chrome, and edit programs (Emacs). I'll have half a dozen windows open through the X tunnel provided by ssh. Works well and lasts for hours. After upgrading to Cygwin 64-bit (this last weekend), everything *seems* to be okay for a while. After about 20 minutes, though, I can no longer open windows remotely. Even though I have thunderbird currently open, when I try to run Chrome, I get (google-chrome:20006): Gtk-WARNING **: cannot open display: localhost:10.0. If I try to open xclock from the command line, I get: xclock Error: Can't open display: localhost:10.0 Does anybody know what happened? Why has the tunnel disappeared? It hasn't actually disappeared because I'm still running thunderbird through it. Thanks for any assistance on this. Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Ignore me
I've subscribed to this list, but my messages don't appear. This is a test to see if this one does. Thanks for your patience. Chris -- 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/
XWin refresh
I prefer to run my Cygwin X window as a separate window. I start XWin with the following command line: %RUN% XWin -clipboard -silent-dup-error What I find, though, is that if my session goes to screen saver or my system goes to sleep, the X window becomes black and won't refresh. I haven't found a way to get it to refresh (there may be some trick, but I haven't figured it out, yet). I've tried minimizing the window and then restoring it, but that doesn't work. I've tried right clicking inside the window, but no menu appears. Is there a simple function key, ALT function key or some secret combination of keys that will force a refresh of the entire window? I use mwm as my window manager, maybe it is this that needs to do the refresh. If it is, does anyone know of a secret incantation that refreshes the window? Thanks for your assistance, Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: fresh install questions
Torsten, I noticed you said installing everything was not a good idea. Yet the web page suggest it if you want all the products. Also, I've found that when I go through the products and pick and choose, 100% of the time nothing installs because there's some problem with the server (some connection times out). Yet I never have a connection problem when I ask for everything or the default. Also note, it happens on every server I've tried, yet I can go back to the servers and ask for everything or the default and it downloads fine. I have yet to figure out how to download anything other than the default or everything. Chris Carlson iStor Networks, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thorsten Kampe Sent: Friday, June 25, 2004 7:56 AM To: [EMAIL PROTECTED] Subject: Re: fresh install questions * Erik Weibust (2004-06-25 16:45 +0200) I just had my XP machine at work rebuilt and the first thing I went to install was cygwin. I went with a complete everything install. Not so clever. You won't need anything so this approach will obfuscate your problem. The problem is the same one I've seen before. When the install is complete I run the shortcut to start cygwin and get a vague message that makes me think the install didn't go so well. Error messages should always be cited in full - not some vague interpretation of you. The work around is easy. I edit /etc/passwd in notepad and change what cygwin uses for $HOME from /cygdrive/h to /home/erikweibust. You open /etc/passwd in *NOTEPAD*?!! Notepad is the unappropriate tool for that possible. It doesn't even understand Unix line endings. /home/erikweibust was not created as part of the install. I think I've had it created before on other machines on the first use of cygwin. I'm not sure why I get this problem. Is cygwin trying to use some XP env vars on it's first start? http://cygwin.com/problems.html -- 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/ -- 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: /usr/bin exists not; man can't find nroff; permissions inconsistent
A lot of times, when you see something like this on a shell script, it's the program it's trying to run to run the shell script. In other words, /usr/bin/nroff is a shell script that requires /bin/sh (the first line). Is /bin/sh defined? Then the next question is, since nroff is emulated by groff, does /usr/bin/groff exist? Chris Carlson iStor Networks, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlo Florendo Sent: Tuesday, June 22, 2004 3:54 PM To: Carlo Florendo Cc: [EMAIL PROTECTED] Subject: Re: /usr/bin exists not; man can't find nroff; permissions inconsistent Sorry, forgot cygcheck. Here it is: Carlo Florendo wrote: Hello, After installing cygwin, I am encountering some issues. cygcheck's output attached: First, I tried to man bash. Nothing appeared on screen so I hit `q'. Then, it says that nroff was not found. $ man bash /usr/bin/nroff: not found Then, I checked whether nroff existed: $ ls -l /usr/bin/nroff -rw-r--r--1 CarloNone 1955 Dec 16 2002 /usr/bin/nroff Thus, I thought it existed but the permissions were not set well. I then tried to change the permissions: $ chmod 755 /usr/bin/nroff chmod: changing permissions of `/usr/bin/nroff': No such file or directory As you see, it says that the file does not exist. Strange, isnt't it? Then, I tried catting the file. Here's what I got. $ cat /usr/bin/nroff cat: /usr/bin/nroff: No such file or directory Thus, I tried going to the /usr/bin directory itself and catted nroff to see if it really existed: $ cd /usr/bin $ ls -l nroff -rwxr-xr-x1 CarloNone 1955 Dec 16 2002 nroff $ cat nroff #!/bin/sh # Emulate nroff with groff. prog=$0 # Default device. # First try the locale charmap command, because it's most reliable. Rest of output snipped Thus, it exists. Then, I again tried doing an `ls -l' on nroff, first *not* specifying its fully qualified name (FQN), and afterwards, specifying its FQN. Here's what I got: $ pwd /usr/bin $ ls -l nroff -rwxr-xr-x1 CarloNone 1955 Dec 16 2002 nroff $ ls -l /usr/bin/nroff -rw-r--r--1 CarloNone 1955 Dec 16 2002 /usr/bin/nroff As you can see, the first listing says the permission is a 755. The second listing says the permission is a 644. This seems to me strange. Why does the permission for the same file appear differently when accessed via different means. (i.e. specifying its FQN; not specifying its FQN)? Thus, I thought that /usr/bin/nroff was probably hardlinked from /bin/nroff and that this linking might have caused some problems so I checked out /bin/nroff. /bin/nroff existed. I found out that /usr/bin/nroff is indeed a hardlink to /bin/nroff but I didn't see why this could really cause a problem. Then, I tried opening a cmd prompt to check if there is any clue I could get from it. This is what I got: Start windows cmd output $ cmd Microsoft Windows 2000 [Version 5.00.2195] (C) Copyright 1985-2000 Microsoft Corp. d:\cygwincd usr cd usr D:\cygwin\usrdir /w dir /w Volume in drive D is PROGRAMS Volume Serial Number is 701A-F5A8 Directory of D:\cygwin\usr [.] [..] [src] [local] [tmp] [include] [share] [doc] [man] [sbin][autotool][info] [i686-pc-cygwin] [etc] [var] [X11R6] [grace] [ssl] [libexec] [logs] [i686-pc-mingw32] 0 File(s) 0 bytes 21 Dir(s) 1,703,936,000 bytes free D:\cygwin\usrdir bin dir bin Volume in drive D is PROGRAMS Volume Serial Number is 701A-F5A8 Directory of D:\cygwin\usr File Not Found D:\cygwin\usrdir d:\cygwin\usr\bin dir d:\cygwin\usr\bin Volume in drive D is PROGRAMS Volume Serial Number is 701A-F5A8 Directory of d:\cygwin\usr File Not Found d:\cygwin\usr End windows cmd output The directory d:\cygwin\usr\bin does not exist. (i.e. It is neither listed with `dir /w' nor `dir bin' nor `dir d:\cygwin\usr\bin') It appears to be linked somewhere else. I would appreciate it very much if anyone could point out which part of the source code I could tweak. I'd like to learn diagnosing problems in source code level. Another thing to note is that cygcheck reports several warnings of this sort: Found: d:\cygwin\\bin\ls.exe Found: d:\cygwin\bin\ls.exe Warning: d:\cygwin\\bin\ls.exe hides d:\cygwin\bin\ls.exe What could be the problem on my system? I know I'm missing something. Thank you so much! Best Regards, Carlo -- Carlo Florendo y Flora Astra Philippines Inc. www.astra.ph -- 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: Carriage Returns
-Original Message- [snip] I just really, really, *really* don't think that _anything_ is going to work around the issue that if you strip all the newlines from a CRLF terminated file[+], what you end up with is something that won't be any good for either 'doze ~OR~ *nix! Apart from maybe _not_ stripping all the newlines, perhaps? The best workaround would be to get an Amiga or Mac... they're the only systems that use CR lineends! -Original Message- I just have to butt in, though it's none of my business. There are many times when one wants to read a line from a file and strip carriage-returns and line-feeds. I don't know Perl like the back of my hand, but I seem to remember there is even a special feature/function that is supposed to do it. In C, I usually programmatically check for both carriage returns and line feeds and replace them with '\0'. I only do this because M$ uses both. I never had to worry about it in *nix-land. As defined in C, there is a concept of end-of-line character. I was under the impression that Perl understood this concept, too. It just so happens that M$ doesn't have one end-of-line character, but a pair of them. In some scripting languages, the carriage-return/line-feed pair is considered one end-of-line character and removing one removes both. It would be logical to assume that a function that removes the end-of-line character on a M$ box would remove both the carriage-return and the line-feed. I think this is what Mr. Kramer is trying to say. -- 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/
Installation problems
I just thought I'd post a problem I've been having for a while now in case if someone wants to look into it. uname -a returns: CYGWIN_NT-5.0 jackal 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin I just did an update. My previous download was last week. At the time, I requested everything to be installed. This time I just allowed Default. Both during the initial installation and the current installation, one of the shell scripts failed with find.exe because it couldn't find cygintl-1.dll. I copied this file from a previous installation in order to complete the installation. My guess is that the new cygwin uses cygintl-2.dll (which exists) but some of the applications (find.exe and grep.exe) still expect cygintl-1.dll. Also, I discovered the following in /var/log/setup.log.full: 2004/06/08 09:36:42 running: C:\cygwin\bin\sh.exe -c /etc/postinstall/postinstall-lilypond.sh rm: too few arguments Try `rm --help' for more information. Chris Carlson iStor Networks, 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/
Printing under Cygwin on W2K
According to the documentation, the following should print on the default printer: bash$ cat myfile.txt PRN What I find is that a new file is created named PRN. Also according to the documentation, cygwin understands the double-slash form used in Windows. Thus the following should work: bash$ cat myfile.txt //Dc1irv/laser1 This returns: bash: //Dc1irv/laser1: No such host or network path So, what is the proper method for printing under cygwin? BTW: uname -a returns: CYGWIN_NT-5.0 jackal 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin Thanks in advance. Chris Carlson iStor Networks, 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: Printing under Cygwin on W2K
Thanks for the quick response! Chris Carlson iStor Networks, Inc. -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 10:39 AM To: Chris Carlson Cc: [EMAIL PROTECTED] Subject: Re: Printing under Cygwin on W2K On Thu, 3 Jun 2004, Chris Carlson wrote: According to the documentation, the following should print on the default printer: bash$ cat myfile.txt PRN What I find is that a new file is created named PRN. Known problem. There's a patch pending for this -- once it's checked in, this functionality should be available again. Until then, use lpr from the cygutils package... Also according to the documentation, cygwin understands the double-slash form used in Windows. Thus the following should work: bash$ cat myfile.txt //Dc1irv/laser1 This returns: bash: //Dc1irv/laser1: No such host or network path Nope, that shouldn't work. I don't think you can redirect output to a printer name even from the Windows console, much less from Cygwin. In any case, Cygwin doesn't treat printer shares as devices. So, what is the proper method for printing under cygwin? Either lpr or, if you want to get fancier, a2ps or enscript. Igor BTW: uname -a returns: CYGWIN_NT-5.0 jackal 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin Thanks in advance. Chris Carlson iStor Networks, Inc. -- 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! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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: Printing under Cygwin on W2K
Redface Okay, I was using a script that I'd written a few months ago that worked at the time but doesn't anymore. I forgot we lost our Dc1irv server and moved the printers to another Windows system. Yes, the //Dc2irv/laser1 successfully references our Windows printer. Thanks for the time. It made me dig a bit deeper into the problem. Chris Carlson iStor Networks, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hannu E K Nevalainen Sent: Thursday, June 03, 2004 1:00 PM To: [EMAIL PROTECTED] Subject: RE: Printing under Cygwin on W2K From: Igor Pechtchanski Sent: Thursday, June 03, 2004 7:39 PM On Thu, 3 Jun 2004, Chris Carlson wrote: According to the documentation, the following should print on the default printer: bash$ cat myfile.txt PRN What I find is that a new file is created named PRN. Known problem. There's a patch pending for this -- once it's checked in, this functionality should be available again. Until then, use lpr from the cygutils package... Also according to the documentation, cygwin understands the double-slash form used in Windows. Thus the following should work: bash$ cat myfile.txt //Dc1irv/laser1 This returns: bash: //Dc1irv/laser1: No such host or network path According to: $ lpr --help this should work. Do you have this printer visible when you use Explorer \\Dc1irv ? Nope, that shouldn't work. I don't think you can redirect output to a printer name even from the Windows console, much less from Cygwin. In any case, Cygwin doesn't treat printer shares as devices. Ehrm? =) I've proven this to be wrong... below. So, what is the proper method for printing under cygwin? Either lpr or, if you want to get fancier, a2ps or enscript. Igor The last two assumes you have a PS printer - I believe... Below: $p is a plain old 'HP Laser Jet 6' shared on 'f1' $ p=//f1/f1_lj6; \ u2d ~/.bash_logout; \ cat ~/.bash_logout $p; \ d2u ~/.bash_logout; \ echo -en $p \r\n\f # The printer produces a paper w the text in courier. # yet another way... $ lpr -d //f1/f1_lj6 ~/.bash_logout $ echo -en //f1/f1_lj6 \r\n\f NOTE: The last echo is _necessary_ in both cases. BTW: uname -a returns: CYGWIN_NT-5.0 jackal 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin $ uname -a CYGWIN_NT-5.0 P450 1.5.10s(0.115/4/2) 20040519 13:51:37 i686 unknown unknown Cygwin Hmm... I have a few days earlier version of the dll (a snapshot). If the above doesn't help; check http://cygwin.com/snapshots/ - unpack one of the cygwin1-* things w bunzip, and move it in place while _no cygwin tasks_ are running. Hmm... proofreading? Nah, that's for cowards! ;-) /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E --76-- ** on a mailing list; please keep replies on that particular list ** -- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); -- --END OF MESSAGE-- -- 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/ -- 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: PATH and HOME in cygwin
Interesting reference (bash scripting guide). I want to take more time to read it. I found it took me a while (20 some-odd years ago) to completely understand the man structure and format. I found some ATT documents on man and, after much reading, came to understand the sections, the subsections and the overall concept of man pages. Now it's easy for me, and I can usually find exactly what I need in a man page quickly. Unfortunately, Linux seems to be leaning toward keeping things in info format. More up-to-date documentation can be found there, so I've learned how to use Emacs to peruse info manuals. Because of the efforts I went through to learn how to read documentation in Unix, I understand a newbie struggling with it. Then there's the question of how up-to-date documents are. When an application was enhanced, were the man pages updated? Are there features that aren't documented that I want to use? I try to be understanding with questions. If they're totally ignorant and lazy, I might kindly tell them where to look, but if it appears like they've made a little effort, I'll try and answer them. Chris Carlson iStor Networks, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hannu E K Nevalainen Sent: Thursday, June 03, 2004 1:00 PM To: [EMAIL PROTECTED] Subject: RE: PATH and HOME in cygwin From: Chris Carlson Sent: Thursday, June 03, 2004 6:29 PM SNIP I'm just suggesting that we show a little patience to people who may not be as well versed in Unix as you are. It is the impatient, condescending tone that gives new Linux users a bad taste for the OS. I want Linux to crush M$ (at least to the point that they are on equal footing in the market). Chasing off new users is not going to encourage that. Ahh... I'm glad to hear that there are more people like me reading this list. I consider myself beeing well versed in how computers work in general terms, I learn fast - as I've been at it for years - still I have problems grasping some of the stuff; though I most of the time know how things usually are set up. I find the man pages very terse, not useful until you know about it already. Other resources often feels either disorganized, using a complex language or a complex - hard to google - setup or organization. And if nothing else of the above fits; the text describes in terms of assumed prior knowledge - where often _one single additional sentence_ picks up the person being less knowledgable to join the ride. The last thing shouldn't be so very hard to change - thus enabling more people to join the gang: Make open/free software be truly free and open! And last: A feature that hasn't been documented (well) could just as well be unimplemented - when it comes to how usable it is. Source is a language that slants in different ways depending on the writers knowledge, coding and commenting style - to begin with. This never has the potential of feeding any user with apropriate input. This one link might be a golden-oldie: $ cat abs-guide.url [InternetShortcut] URL=http://www.cs.unibo.it/~montreso/doc/bash/abs-guide.pdf ... I've yet to check it out thoroughly. Seems a bit aged. /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E --76-- ** on a mailing list; please keep replies on that particular list ** -- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); -- --END OF MESSAGE-- -- 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/ -- 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: PATH and HOME in cygwin
Mr. Kampe: I understand your frustration, but your experience is not everyone's. So far, I've installed cygwin on 7 different machines. One Windows 98, two Windows XP and at least 4 Windows 2000 systems. Of the seven, all were installed from the Internet, all were done at different points in Cygwin's development, all were clean installs (no previous version of Cygwin existed) and NONE of them have an /etc/profile file. All have an /etc/profile.d directory. None have gone through the postinstall scripts without at least one of them hanging. Only after some time have I gotten man to work. It is clear the Mr. Fay doesn't understand bash well. He obviously doesn't know the purpose of /etc/skel. He may not understand man. If he's just doing a man command, there's a lot of information that gets scrolled by. It takes a dozen or more readings before you understand it all, presuming you've never used a Unix shell before. I had to set PATH and HOME in my Windows environment to get them to be set properly in Cygwin. I would think telling Mr. Fay that he needs to set them in the Windows environment would have been a much more useful reply. Suggesting the reading of a book on shells wouldn't be quite useful either, since Cygwin does things just a little differently. A pointer to the Cygwin document might have helped. I'm still looking for it. Chris Carlson iStor Networks, Inc. -Original Message- From: Thorsten Kampe [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 02, 2004 10:21 AM To: [EMAIL PROTECTED] Subject: Re: PATH and HOME in cygwin * David Fay (2004-06-02 13:50 +0100) I am trying to set my PATH and HOME in cygwin. Why? Didn't you have these yet? Didn't you like them? Under the /etc/profile file it says to change the bashrc.bash file and I have amended this but still no change. You didn't read a few lines more in /etc/profile until it says Here is how HOME is set, in order of priority, when starting from Windows, did you? I also see there is a .bash_profile file in both the /etc/defaults/etc/skel and /etc/skel. I originally thought that this is the file I would amend but I expected this to be in my home directory. Any suggestions? Please read the fscking bash manual - especially the FILES section at the bottom. Otherwise nice people will start telling you things in a way you'll surely won't like. Hint: the manual doesn't mention /etc/bashrc - so it's up to YOU to make sure it gets sourced. Thorsten -- 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/ -- 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: New install of 1.5.10 replacing 1.5.6: many things not working
Actually, I've had numerous problems installing cygwin. I have two machines at home running Windows XP and also my office computer running Windows 2000 Pro. Installing a clean system (no cygwin installed before) installed on my two home machines but hung in the postinstall scripts. I finally had to kill the script and run the remaining ones by hand. That was a few months ago, so I didn't bother to tell anyone. This time, I tried to upgrade my cygwin at the office since the one I have at home is so much better. They had 1.3.10 installed. Fortunately, I zipped the entire c:/cygwin directory before doing it. Everything was so corrupt, I finally deleted the entire cygwin tree and unzipped what I had saved. Here are some of the things I tried: 1 - I left the setup.exe showing Default and installed from sigunix.cwru.edu. It failed for some reason, I didn't bother to check the logs. 2 - I tried mirrors.kernel.org and took the trouble to try and add a few things that I installed at home and liked. It also failed in the middle for some reason, I didn't bother to check the logs. [If I only had the time to investigate all this stuff, but we're working long hours.] 3 - Finally, I renamed c:/cygwin to c:/cygwin1 and tried to perform a clean install. I used sources-redhat.mirror.redwire.net and selected Install instead of Default since that's supposed to install everything. 4 - This morning (I had left it to install overnight), I had an error popup window telling me: The dynamic link library cygintl-1.dll could not be found in the specified path (path is listed here and it includes c:\cygwin\bin) It seems that this error was generated from one of the postinstall scripts when it ran grep.exe. After clearing the error (pressing the OK button), I got about two dozen more of these errors from other calls to grep and one from a call to find in various postinstall scripts. I did a search on c:\cygwin from a Windows Explorer window and there is no file named cygintl-1.dll anywhere in the tree. I also searched under c:\WINNT, although I didn't expect it to be there. Oh, well, I tried running bash. It comes up in /cygwin/bin, as Joe indicated, and I can't run cat or more to look at the passwd file. Seems cat isn't in any of the bin directories, and more can't find cygncurses6.dll. So, what have I done wrong? What can I do to fix it? Thanks for any assistance you can provide. Chris Carlson iStor Networks, Inc. -Original Message- From: Brian Ford [mailto:[EMAIL PROTECTED] Sent: Friday, May 28, 2004 9:10 AM To: Joe Landman Cc: [EMAIL PROTECTED] Subject: Re: New install of 1.5.10 replacing 1.5.6: many things not working On Fri, 28 May 2004, Joe Landman wrote: Hi folks: I have multiple machines with 1.5.6 installed. I wanted to upgrade to 1.5.10 (bug fixes, speed, etc). Stuff worked (for the most part) in 1.5.6. I was/am looking to using it for application development on windows. Are you trying to upgrade just the Cygwin package, or all Cygwin packages? With 1.5.10 install, I get error messages about find.exe being given bad arguments. This usually means you have a PATH problem and are getting the Windows version of find rather than the Cygwin one. Many of the post-install scripts die with problems with grep (more in a moment). When I open the cygbash shell, it puts me into /usr/bin by default, Check you /etc/passwd file and make sure your user home directory is set correctly. and the moment I cd out of there, I lose any ability to run basic commands such as ls. Sounds like . is in your PATH, but /usr/bin isn't. Anything that tries to use grep is rewarded with an error message about /bin/grep not existing. Quick ls'ing around (find does not work... sigh) does not locate a grep. Ok, I may be thick, but I think that there might be a problem here. The machines with problems: 1) Windows XP Home laptop. SP1 installed. 512 MB ram 2) Windows 2000 desktop. SP_something_or_other installed. 768 MB ram Both had similar working copies of 1.5.6 installed. Starting up the cygbash shell resulted in being in the /home/landman directory (where I thought I should be). Everything properly pathed out in the older version. Any thoughts? I don't have to re-install the OS... (I hope :( ). Try a Cygwin reinstall after checking out your PATH issues. Please read this: Problem reports: http://cygwin.com/problems.html and attach cygcheck output. Maybe then someone will have a better idea. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports
RE: New install of 1.5.10 replacing 1.5.6: many things not working
Attached is the cygcheck output file. This was generated prior to my
changes below.
I have managed to get my cygwin up and working. I had to append the old
cygwin.old/bin and cygwin.old/usr/bin to my path. It appears that a new
library cygintl-2.dll was generated but many of the executables still
expect cygintl-1.dll.
Just appending the two directories caused problems in that cat noticed
there were two versions of cygwin1.dll, so I just deleted the one in
cygwin.old/bin.
I created a /etc/profile which contains:
PATH=/bin:${PATH}:/cygdrive/c/cygwin.old/bin:/cygdrive/c/cygwin.old/usr/
bin
export PATH
if [ -r $HOME/.bashrc ]
then
. $HOME/.bashrc
if [ $PWD != $HOME ]
then
cd $HOME
fi
fi
With minimal testing, this seems to fix all my problems for now.
Chris Carlson
iStor Networks, Inc.
-Original Message-
From: Chris Carlson
Sent: Friday, May 28, 2004 10:08 AM
To: [EMAIL PROTECTED]
Subject: RE: New install of 1.5.10 replacing 1.5.6: many things not
working
Actually, I've had numerous problems installing cygwin. I have two
machines at home running Windows XP and also my office computer running
Windows 2000 Pro.
Installing a clean system (no cygwin installed before) installed on my
two home machines but hung in the postinstall scripts. I finally had to
kill the script and run the remaining ones by hand. That was a few
months ago, so I didn't bother to tell anyone.
This time, I tried to upgrade my cygwin at the office since the one I
have at home is so much better. They had 1.3.10 installed.
Fortunately, I zipped the entire c:/cygwin directory before doing it.
Everything was so corrupt, I finally deleted the entire cygwin tree and
unzipped what I had saved.
Here are some of the things I tried:
1 - I left the setup.exe showing Default and installed from
sigunix.cwru.edu. It failed for some reason, I didn't bother to check
the logs.
2 - I tried mirrors.kernel.org and took the trouble to try and add a few
things that I installed at home and liked. It also failed in the middle
for some reason, I didn't bother to check the logs. [If I only had the
time to investigate all this stuff, but we're working long hours.]
3 - Finally, I renamed c:/cygwin to c:/cygwin1 and tried to perform a
clean install. I used sources-redhat.mirror.redwire.net and selected
Install instead of Default since that's supposed to install
everything.
4 - This morning (I had left it to install overnight), I had an error
popup window telling me:
The dynamic link library cygintl-1.dll could not be found in the
specified path (path is listed here and it includes c:\cygwin\bin)
It seems that this error was generated from one of the postinstall
scripts when it ran grep.exe.
After clearing the error (pressing the OK button), I got about two dozen
more of these errors from other calls to grep and one from a call to
find in various postinstall scripts.
I did a search on c:\cygwin from a Windows Explorer window and there is
no file named cygintl-1.dll anywhere in the tree. I also searched under
c:\WINNT, although I didn't expect it to be there.
Oh, well, I tried running bash. It comes up in /cygwin/bin, as Joe
indicated, and I can't run cat or more to look at the passwd file.
Seems cat isn't in any of the bin directories, and more can't find
cygncurses6.dll.
So, what have I done wrong? What can I do to fix it?
Thanks for any assistance you can provide.
Chris Carlson
iStor Networks, Inc.
-Original Message-
From: Brian Ford [mailto:[EMAIL PROTECTED]
Sent: Friday, May 28, 2004 9:10 AM
To: Joe Landman
Cc: [EMAIL PROTECTED]
Subject: Re: New install of 1.5.10 replacing 1.5.6: many things not
working
On Fri, 28 May 2004, Joe Landman wrote:
Hi folks:
I have multiple machines with 1.5.6 installed. I wanted to upgrade
to
1.5.10 (bug fixes, speed, etc). Stuff worked (for the most part) in
1.5.6. I was/am looking to using it for application development on
windows.
Are you trying to upgrade just the Cygwin package, or all Cygwin
packages?
With 1.5.10 install, I get error messages about find.exe being given
bad arguments.
This usually means you have a PATH problem and are getting the Windows
version of find rather than the Cygwin one.
Many of the post-install scripts die with problems with grep (more in
a
moment). When I open the cygbash shell, it puts me into /usr/bin by
default,
Check you /etc/passwd file and make sure your user home directory is set
correctly.
and the moment I cd out of there, I lose any ability to run
basic commands such as ls.
Sounds like . is in your PATH, but /usr/bin isn't.
Anything that tries to use grep is rewarded with an error message
about
/bin/grep not existing. Quick ls'ing around (find does not work...
sigh) does not locate a grep.
Ok, I may be thick, but I think that there might be a problem here.
The machines with problems:
1) Windows XP Home laptop. SP1 installed. 512 MB ram
2) Windows 2000 desktop
