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
Subject:	"parse error" in cygwin.h
To:	cygwin AT sourceware DOT cygnus DOT com
From:	John DOT Velman AT HSC DOT com
Date:	Thu, 31 Aug 2000 12:19:03 -0700
Message-ID:	<OF2E7C9215.5F56149F-ON8825694C.00676385@hughes.com>
X-MIMETrack:	Serialize by Router on MTA00/HUGHES(Release 5.0.2c |February 2, 2000) at 08/31/2000
	12:19:04 PM
MIME-Version:	1.0

In compiling GNUProlog, I encountered the following output
from make:

______________

....
make[1]: Entering directory `/home/newarchives/GNUProlog/gprolog-1.2.1/src/TopCo
mp'
make[1]: Nothing to be done for `first'.
make[1]: Leaving directory `/home/newarchives/GNUProlog/gprolog-1.2.1/src/TopCom
p'
make[1]: Entering directory `/home/newarchives/GNUProlog/gprolog-1.2.1/src/Engin
ePl'
gplc -c -C '-O3 -finline-functions -fomit-frame-pointer' machine.c
In file included from machine.c:49:
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/sys/cygwin.h:46: pars
e error before `cygwin_logon_user'
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/sys/cygwin.h:46: warn
ing: data definition has no type or storage class
compilation failedI

__________________

Personally, I can't see anything wrong with cygwin.h.    (Actually, there are
two versions  of cygwin.h, one in /usr/include/sys, and one in
/usr/i686-pc-cygwin/include/sys.  The one in question seems to
actually be the one in /usr/include/sys, since the other one doesn't
have 46 lines, and doesn't have 'cygwin_longon_user' in it.  )

/usr/include/sys/cygwin.h is dated August 3.  (The other one is dated
Feb 29.)

I swear I haven't touched the .h files.  :-).

A number of other files with #include <sys/xxx> statements did compile
successfully, and in processing machine.c, it got through a few
of these #include statements before the error occurred, so I don't
think this is a generic problem like binary vs. text.

Thanks,

John Veman
john DOT velman AT hsc DOT com
one in /usr/lib/


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -