Mail Archives: cygwin/2004/12/14/03:34:22
"Dave Korn" <dave DOT korn AT artimi DOT com>
2004-12-13 04:54 PM
To: Jurgen Defurne/BRG/CE/PHILIPS AT PHILIPS
<cygwin AT cygwin DOT com>
cc:
Subject: RE: Command boxes popping up
Classification:
> -----Original Message-----
> From: cygwin-owner On Behalf Of jurgen.defurne
> Sent: 13 December 2004 15:39
> Hi Dave,
>
> No, I have no problems with graphical applications.
Cool, it would have _really_ confused me if you did!
> My scripts run a variety of commands, mostly cygwin,
> but some applications run in a DOS shell.
>
> To elaborate, I run bash, and inside this shell I start
> ActiveState Perl,
> which of course knows nothing about Cygwin. The script run by
> ActiveState's Perl, then starts system or `` commands, and it is
> from there that I get command boxes.
>
> I have run a small test :
> $ /cygdrive/c/Perl/bin/perl -e "system \"dir\""
>
> and this pops up a DOS command box while the command
> executes.
>
> I did not have that before, and the only thing changed was
> the upgrade to Cygwin 1.5.11.
Nonetheless, it would seem that ActiveState Perl is the thing with the
bug in
it. Not being a cygwin program, a change to the cygwin dll could hardly
affect
ActiveState Perl's behaviour, could it?
>>>>###########################################################################
Yes, but how does that explain that I did not have the problems if I ran
the same things when Cygwin 1.5.3 was still installed ?
<<<<###########################################################################
Well, it shouldn't of course, but I can imagine one way in which it
could.
Bear in mind that running inside the bash shell - unlike if you were to
just
try your test from a cmd.exe shell - has one major difference: the $PATH
setting
includes the cygwin bin directories at the front.
>>>>###########################################################################
I will check this PATH setting, although my script fixes up the path
before
starting system calls.
<<<<###########################################################################
Now, given that cygwin includes its own distribution of Perl, which
presumably
is also called "perl.exe", we have a potential for clashes here.
>>>>###########################################################################
The subscripts explicit remove any references to any Cygwin environment,
because they know that they clash with each other.
<<<<###########################################################################
FWIW, running the example that you gave with cygwin perl doesn't produce
a DOS
box. I'm not surprised that AS perl wants to have its system commands run
in a
dos box, as that's the only system it knows about. OTOH I see Jason's
post
saying that he can't reproduce your problem. Therefore I suggest the two
of you
compare $PATH settings, in particular which order AS perl and cygwin's bin
directories occur in both your $PATHs, and that may give us some further
clues...
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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 -