Hi Urs,

Thank you very much for your prompt replay. I checked these setting, 
they are the same as before when the compilation was working. I am 
wondering if the installation of Jennic ZigBee Evaluation Kit causes the 
conflict with the previous cygwin which was installed with the tinyos, 
since there is another cygwin installed when the Jennic things were 
installed. If this is the case, how to solve it please.

Thanks very much!

Ruoshui

Urs Hunkeler wrote:
> Hi Ruoshui,
>
> This sounds like the environment variables are not set correctly. I'm 
> not sure for TinyOS 1.x, with TinyOS 2.x I would check:
> $MAKERULES (this should indicate where the TinyOS specific makefiles 
> are located)
> $TOSROOT
> $CLASSPATH
>
> When I was still using windows, I think I had a startup script in 
> /etc/profile.d for configuring the paths. You might also have set the 
> paths in your .bashrc or .profile script.
>
> Cheers,
> Urs
>
>
> Ruoshui Liu wrote:
>> Dear all,
>>
>> I have been working on the tinyos 1.1.15, and it was working all 
>> right with everything. One day, I installed the Jennic ZigBee 
>> Evaluation Kit on my computer and the installation comes with the new 
>> version of Cygwin. After the installation, my /cygwin shell/ has been 
>> replaced with the /bash-2.05b/, and user interface has been totally 
>> changed. This was solved by rerun the setup located in the 
>> \tinyos\cygwin-installationfiles\, but the worst thing is I can not 
>> compile any applications any more. The error message I have got is
>>
>> "../Makerules:26: /../apps/Makerules: No such file or directory
>> make: *** No rule to make target `/../apps/Makerules'.  Stop."
>>
>> These makefile and makerules are exactly same as before, and I didn't 
>> change anything. Could you anyone give me some hints on this please? 
>> I really appreciate any help.
>>
>> Best regards,
>> Ruoshui

_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to