Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com> List-Archive: <http://sources.redhat.com/ml/cygwin/> List-Post: <mailto:cygwin AT sources DOT redhat DOT com> List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 10 Oct 2001 13:12:29 +0200 From: Corinna Vinschen <cygwin AT cygwin DOT com> To: cygwin <cygwin AT cygwin DOT com> Subject: Re: Why does fhandler_tty_slave::open call attach_tty? Message-ID: <20011010131229.L12872@cygbert.vinschen.de> Mail-Followup-To: cygwin <cygwin AT cygwin DOT com> References: <20011009090114 DOT R12872 AT cygbert DOT vinschen DOT de> <200110100118 DOT f9A1IBE22927 AT cate2-108 DOT reshall DOT ou DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110100118.f9A1IBE22927@cate2-108.reshall.ou.edu>; from jcast@ou.edu on Tue, Oct 09, 2001 at 08:18:10PM -0500 On Tue, Oct 09, 2001 at 08:18:10PM -0500, Jon Cast wrote: > > Corinna Vinschen <cygwin AT cygwin DOT com> wrote on Tue, 09 Oct 2001 09:01:14 +0200: > > > Did you have a look into the openpty() implementation in the > > inetutils package? It doesn't need any of the internals. > > Actually, I didn't know there was an openpty implementation in Cygwin. > Otherwise, I wouldn't have bothered, since openpty is all I really > want. > > Is there any reason inetutils doesn't install libinetutil.a? Hmm, I assume it's treated as an internal library, just used for building the inetutils package. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/