Date: Fri, 12 May 2006 00:00:59 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 698 ************************************************** Thursday 11 May 2006 Number 698 ************************************************** Subjects for today 1 Re: error in mount.h : Dave Yeo" **= Email 1 ==========================** Date: Wed, 10 May 2006 07:47:47 -0800 From: "Dave Yeo" Subject: Re: error in mount.h On Wed, 10 May 2006 09:30:28 +0100, Dave Bamford wrote: >>You need sys/types.h included. Try adding it to sys/mount.h, maybe around line 56 eg >>#include . >>You could also file a bug report with whatever you are building. >>Dave >>ps you should really mention what compiler and libc you are using >> >> >> >Hi > >I added the include as above and the type erros have gone but I still >get the parse >error as follows > >| #include >configure.:12326: result: no >configure.:12284: checking for sys/mount.h >configure.:12306: g++ -c -g -O2 conftest.cc >&5 >In file included from configure:12349: >D:/USR/include/sys/mount.h:58: error: parse error before `[' token >configure.:12309: $? = 1 >configure.: failed program was: >| #line 12289 "configure" >| /* confdefs.h. */ > >I am using gcc 3.3.5 (bird) and libc 0.6 (I think) is there a definitive >way of >checking your environment. It would be really nice to have some standard >to check that I am not including and headers or libraries that I >shouldn't and >that I have everything in place that I should. The environment is getting >out of control as I also use this PC for general use and don't have the >luxury >of a dedicated system for porting. >The original ucx bootstrap command file was really good but I guess thats >way out of date now. Parse errors can be a bitch as they don't say much, usually a misisng include or something. One way to tell what version of libc you have is to look at usr\doc\ReleaseNotes.os2 at the top. Dave