Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 25 May 2003 10:30:10 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: using syscall in cygwin? Message-ID: <20030525083010.GF19367@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030524123851.34720.qmail@web15307.mail.bjs.yahoo.com> <20030524175023.GA6768@redhat.com> <3ED07063.5030600@yahoo.com.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3ED07063.5030600@yahoo.com.cn> User-Agent: Mutt/1.4.1i On Sun, May 25, 2003 at 03:27:31PM +0800, Kai Liu wrote: > Thank you for your response. > I just want to write code using my own open(). > How can I implement open() without syscall() to make the system call? > Maybe I need also write my own syscall() which call glibc's open(), and > link them staticly? > Is it reasonable? No. In case of Cygwin the syscall *is* open(). Don't mess with it. N.B., there's no glibc involved at all. Cygwin doesn't use glibc but newlib as std C lib. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/