[Tinyos-devel] Fwd: Safe TinyOS tools

[Vlado Handziski]

On Sun, Jun 22, 2008 at 21:10, John Regehr <regehr at cs.utah.edu> wrote:

> Sorry for the late reply I've been traveling...
>
>  Are the instructions at
>> http://www.cs.utah.edu/~coop/safetinyos/install/still<http://www.cs.utah.edu/%7Ecoop/safetinyos/install/still>current? Isn't
>> there going to be a proper tools package supporting
>> safe TinyOS?
>>
>> The deputy RPM package on that page seems to support cygwin only...
>>
>
> In addition to the rpm for Cygwin there is a deb for Ubuntu on our site,
> which has been tested on Feisty and Hardy.  Are there other platforms that
> you would like to see?
>

Traditionally we have supported RedHat/Fedora. I can build a package for F8
if you send me the spec file.


>  Also, what is this story about patching include files in the msp430 and
>> avr
>> toolchains. Why is this not handled with shadowing + undef somewhere in
>> the
>> tinyos headers, like we do in msp430hardware.h?
>>
>
> I couldn't make this work without shadowing everything-- the patch needs to
> be seen by other AVR header files.  Perhaps there is some trick that I
> missed.
>
> Anyway the necessary changes are in the latest versions of Kevin's avr-gcc
> package (but not msp430-gcc, I'll check what's up with that).


I am still very concerned with this approach. I think we should try to limit
the customization of the toolchains, with the final aim of using "generic"
packages of a given supported release.

If the modification needs to be seen only by header files that are used in
the normal nesc/gcc compilation flow, then putting the redefines in a header
file that is included early (lilke the msp430hardware.h) should work I
think.

Vlado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20080622/21b93b2f/attachment.htm