Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: xfce4 - xffm
Date: Thu, 10 Jun 2004 18:36:32 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.GSO.4.58.0406101245420.2424@slinky.cs.nyu.edu>
Message-ID: <NUTMEGdiixjnzi95Hfq000002bf@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 10 Jun 2004 17:36:32.0484 (UTC) FILETIME=[78512A40:01C44F11]

> -----Original Message-----
> From: Igor Pechtchanski 
> Sent: 10 June 2004 17:48


> IMO, this is a bug in <mntent.h>.  There's no reason not to 
> include all
> the prerequisites, as include guards will take care of 
> multiple includes.
> It shouldn't require the users to include other headers before it...
> 
> Yes, I know, I know, PTC...

  Don't think that this one should need an assign!

--- mntent.old.h	2004-06-10 18:33:11.485938400 +0100
+++ mntent.new.h	2004-06-10 18:35:13.501071300 +0100
@@ -11,6 +11,10 @@ details. */
 #ifndef _MNTENT_H
 #define _MNTENT_H
 
+#ifndef _STDIO_H_
+#include <stdio.h> /* For FILE type. */
+#endif
+
 #ifdef __cplusplus
 extern "C" {
 #endif
@@ -25,6 +29,7 @@ struct mntent
   int mnt_passno;
 };
 
+
 #ifndef _NOMNTENT_FUNCS
 FILE *setmntent (const char *__filep, const char *__type);
 struct mntent *getmntent (FILE *__filep);


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....
 



--
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/