Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <5.1.0.14.1.20020101205143.026680c8@postoffice.brown.edu> X-Sender: John_Mertus AT postoffice DOT brown DOT edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 01 Jan 2002 21:00:32 -0500 To: cygwin AT cygwin DOT com From: John Mertus Subject: inetd and stdout for Borland CBuilder Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Here is a problem. I am using windows 2000, and the latest version of inetd dowloaded last week. I set up inetd in the standard way to run the program #include main() { printf("Hello World\n"); } If I compile this program under gcc, then do a telnet I receive the return Hello World If I compile the program under Borland CPPBuilder, then do a telnet I get NOTHING, although I checked that the program is being run (by modifying the program so it creates a file) Thus the standard output of Borland is NOT being treated as standard output that cygwin needs. The question is what do I have to do to get Borland stdout and stdin to work with stdout and stdin? Does anyone know? Please, no compile under gcc, the program used libraries that are borland compatiable and I do not have the source code to recompile. Plus gcc lack a 64 bit integer ostringstream. Thank you for any answers. -John_Mertus AT Brown DOT EDU -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/