X-Spam-Check-By: sourceware.org
Message-ID: <1164696228.456bdaa40a924@easymail-old.hol.gr>
Date: Tue, 28 Nov 2006 08:43:48 +0200
From: moka AT hol DOT gr
To: cygwin AT cygwin DOT com
Subject: Re: Installation problem(?) for grace: HOW DO I GET old xorgs?
References: <1164639447 DOT 456afcd7265cf AT easymail-old DOT hol DOT gr> <456B2D5D DOT 5090803 AT scytek DOT de>
In-Reply-To: <456B2D5D.5090803@scytek.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Virus-Status: Clean
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Αρχικό μήνυμα από  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/