Hi Michael, We not-infrequently get this error when compiling with nesC in Cygwin. We suspect it has something to do with nesC tickling a bad interaction between Cygwin and Windows, causing Windows to run out of handles (process handles, file handles, etc), causing the dreaded Cygwin "failed to fork" error, which we think nesC catches and translates into the mysterious "failed to preprocess" error with no indication of what otherwise failed. This error should not be confused with the non-mysterious form of the "failed to preprocess" error when nesC indicates a syntax error in a header file, for instance. The mysterious form of the error is inconsistent, so attempting to rebuild the application may cause the build to succeed, or for the error to appear in some other file. Sometimes, the failures are so frequent that only a reboot helps.
Best regards, Moteiv Support PS: Please forward this to TinyOS Help if you feel it is relevant. On 10/11/07, Michael Schippling <[EMAIL PROTECTED]> wrote: > > I'm struggling with getting tmote sky to work after years of banging > my head on mica/TOS. Using the CD I got from Moteiv a couple months ago, > labeled "boomerang Tmote Tools CD v2.0.5" I loaded the entire system from > scratch and managed to get the Delta demo to compile and run, finally, > on a fairly fresh Win2k install. > > Then I took a stab at Oscilloscope which compiled fine. Things were > going along swimmingly until I came up with an actual application idea > which required that I get a simple program running on my own... > > Just to temp fate, I tried to compile Count/CountUart as a beginning, > and here's what I got: > > In file included from > /opt/moteiv/tos/platform/msp430/MainUartPacketC.nc:17, > from /opt/moteiv/tos/lib/sp/SPC.nc:73, > from /opt/moteiv/tos/lib/sp/GenericComm.nc:33, > from CountUartC.nc:26: > In component `UARTFramedPacket': > /opt/moteiv/tinyos-1.x/tos/system/UARTFramedPacket.nc:47: > failed to preprocess > /opt/moteiv/tinyos-1.x/tos/interfaces/BareSendMsg.nc > make: *** [exe0] Error 1 > > Now O'scope uses BareSendMsg just dandy, with what appears to be > the same (or a very similar) set of includes, and according to the > -v output, the same/similar file order. Please note that there > is no indication of WHAT or WHY we failed to preprocess. I went > and put an error in the BSM.nc file (commented the "include AM" > line) and got some more explicable failure, so I'm looking at > the right file. > > Now, to makes things more interesting: > I extracted the ncc command line from the make output and ran it > as a bash script from the same shell where the make failed > ...and... > It Works. > > So, what am I missing this time? > thx > MS > > -- Best, Moteiv Support
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
