|
1. Calling for cygwin users!
|
|
Sun Nov 21, 2004 [3:41 PM]
|
Massaria
me_add@hotmail.com
member since: Apr 17, 2004
|
Reply
|
|
I'm trying to use cygwin. Trying being the operative word here.
The thing is, the error messages keep scrolling out of the frame for me, and with the top ones being fairly important, I'm stuck. So a kind soul took pity on me and told me about the wonderous > function. And I've made files with logs over how the file extraction and compilation process went, and then I get to execute: ./swr.exe > swrlog
Only this time it prints all my errors onto the screen. It makes the file "swrlog", but it's completely empty.
How do make this work? Is there other ways that I might view those secretive top lines?
|
|
|
|
|
2. RE: Calling for cygwin users!
|
|
Sun Nov 21, 2004 [4:54 PM]
|
aeonian
Email not supplied
member since: Apr 28, 2003
|
In Reply To
Reply
|
|
Output can come from two streams; standard output and standard error. the > redirects info from standard output to a file. You'll want to use 2> to redirect info from standard error.
|
|
|
|
|
3. RE: Calling for cygwin users!
|
|
Sun Nov 21, 2004 [7:21 PM]
|
Tyche
Email not supplied
member since: Apr 4, 2000
|
In Reply To
Reply
|
|
Assuming you are using the bash shell under cygwin, take a look at the bash man pages under the section REDIRECTION.
man bash
Also doesn't this SWR have a startup script that archives logs for you like most of the mercish derivatives? If so and you had trouble executing it, it's probably a c-shell script and you might try installing tcsh from cygwin's setup.
|
|
|
|
|
4. RE: Calling for cygwin users!
|
|
Mon Nov 22, 2004 [10:32 AM]
|
Massaria
Email not supplied
member since: Apr 17, 2004
|
In Reply To
Reply
|
|
Perfection! Thanks Aeonian.
Tyche: It does have the logs, but it had one line of undeluded irrelevancy. Thanks to you too :)
|
|
|
|
|