X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <4786B436.5030702@upb.de>
Date: Fri, 11 Jan 2008 01:11:34 +0100
From: =?ISO-8859-1?Q?Sven_K=F6hler?= <skoehler AT upb DOT de>
User-Agent: Thunderbird 1.5.0.14 (Windows/20071210)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [BUG?] run.exe and pdflatex
References: <fm5sat$o04$1 AT ger DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0801101505510 DOT 8742 AT access1 DOT cims DOT nyu DOT edu> <fm62p7$frr$1 AT ger DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0801101700480 DOT 8742 AT access1 DOT cims DOT nyu DOT edu> <4786AC35 DOT 4030608 AT upb DOT de> <Pine DOT GSO DOT 4 DOT 63 DOT 0801101841210 DOT 13638 AT access1 DOT cims DOT nyu DOT edu>
In-Reply-To: <Pine.GSO.4.63.0801101841210.13638@access1.cims.nyu.edu>
Content-Type: multipart/signed; micalg=pgp-sha1;  protocol="application/pgp-signature";  boundary="------------enig402E00AB7815DF8E8DDEAEE4"
X-Virus-Status: Clean
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
Note-from-DJ: This may be spam

--------------enig402E00AB7815DF8E8DDEAEE4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> Now, in Cygwin 1.7.x (a.k.a. CVS HEAD), this is no longer the case (since
> revision 1.243 of spawn.cc).  The comment simply says "Drop
> pty_needs_alloc_console check" -- maybe Corinna can explain why it was
> dropped.  So your program will not work as expected in the snapshots.

OK, thanks for the explanation.

But ... wouldn't that mean that any command executed would open a
console window?



In your other responses, you said, that using the shell is the most
preferrable way. Unfortunatly, i cannot use the shell. The method is
well understood. I could easily execute cygwin stuff by using:

bash -c "exec \"\$0\" \"\$@\"" program param1 param2 ...

The program from which i want to execute pdflatex/pslatex/etc. (which is
Texlipse, a Latex plugin for Eclipse) doesn't allow me to do so.


But aside from that: is the shell really the preferred way of doing
this? Doesn't the shell simply call execve again?
Following what you said, it should be best to call bash.exe from run.exe
to solve all the issues. So the question is: who does all the checks
(shebang, etc.)?
- the execve implementation? (which is cygwin, right?)
- the shell?
- both?


--------------enig402E00AB7815DF8E8DDEAEE4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHhrQ27Ww7FjRBE4ARAjaCAKDH0FHkp+9HSfSLO6k65ne314mU8wCgmsWc
DBW27wslckNdneLR08/Ekuc=
=IVQl
-----END PGP SIGNATURE-----

--------------enig402E00AB7815DF8E8DDEAEE4--