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 X-Authentication-Warning: smtp3.cern.ch: Host pb-d-128-141-36-121.cern.ch [128.141.36.121] claimed to be lxcms60.cern.ch Message-ID: <3E801ED4.9030408@cern.ch> Date: Tue, 25 Mar 2003 10:18:12 +0100 From: "Lassi A. Tuura" Organization: Northeastern University, Boston, USA User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20030129 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Problems interpreting errno References: In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Passing errno values across systems isn't portable. You need to define your own error codes and map errno to those. There is nothing else you can do if you want to be portable. These problems pop up in various networked file systems every once in a while. The most recent one I saw was on AFS which passed server errors to client directly; the linux client didn't do much intelligent with Solaris or AIX errno values (I forget which one was a problem). You are not alone :-) //lat -- Judge a man by his questions rather than by his answers. --Voltaire -- 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/