Mail Archives: cygwin/2006/11/28/01:44:07
Αρχικό μήνυμα από Volker Quetschke <quetschke AT scytek DOT de>:
> moka AT hol DOT gr wrote:
> > Looks like initially a path problem, plus an X-problem
> >
> > I found out that at least one of the reasons grace and gracebat would not
> run
> > from the DOS command line
> Oh! You never said anything about cmd.exe. Naturally cygwin links only
> work in a cygwin shell. bash, ash, zsh, tcsh, ... pick your poison.
>
> > was that the directory for cygX11R6.dll was not in the path. I fixed that
> and
> > also put the actual path for gracebat
> Well, using cygwin.bat would have solved that for you too. (And would
> have given you a nice bash prompt.)
>
> > . c:cygwinusrsharegracebin before c:cygwinbin, so a command would look
> Looks really funny, you lost your backslashes in the mail ;)
>
> > for the actual executables
> > before the symlinks.
> > So I run
> > c:mydir> c:cygwinusrsharegracebingracebat test.dat -hdevice JPEG
> > -printfile gtest.jpg
> > or
> > c:mydir> gracebat test.dat -hdevice JPEG -printfile gtest.jpg
> >
> > It runs instantly, but produced NO file gtest.jpg
> >
> > (Before adding the actual executable directory to the path before the bin,
> it
> > just hung there)
> >
> >
> > Also, if I try to run grace by clicking on its icon(not the symlink), it
> does
> > nothing
> > If I run
> > c:mydir> grace
> > it does nothing
> No wonder, half of it's paths are missing. Start it from a shell ...
>
> >
> > but if I do
> > c:mydir> ash
> >
> > $grace
> > I get back
> > grace>1
>
> like you did here.
>
> > If I do
> > c:mydir> xmgrace
> > I get Can't open display
> > Failed initializing GUI, exiting
> >
> > So, it looks like an X-problem. How do I go about solving it?Αρχικό μήνυμα
> από
>
> The X-problem seems to be that the X-server is not running. Try using
> startxwin.bat. (This one actually works if you "click" on it.) *shudder*
>
> Volker
>
>
> --
> PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net
> key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
>
>
So the bottom line is I should run this from a bash prompt. Here is what I am
afraid of: The script actually running and calling gracebat is a (n
Activestate) perl script
that interfaces with an Oracle database via DBI and DBD:Oracle. This
was a pain to install and is using MS-VisualC++. So with cygwin
I should go all out cygwin, i.e. use cygwin's Perl, not activestate's, hope
that cygwin's perl includes DBI and DBD-Oracle and run everything from a bash
prompt. If other windows processes run at the same time(for instance other perl
scripts), that's fine. Am I understanding this right?
--
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/
- Raw text -