Solved!!!

deb http://tinyos.stanford.edu/tinyos/dists/ubuntu/pool/main/a/avr-libc-tinyos/ 
natty main 
contains all libs as you said. Many thanks for checking it.

For some reason, just updating the toolchain didn't work.
I removed all avr tinyos related and reinstalled and all work like a charm now.

András, Janos, many thanks for your help, I really appreciated. I was about to 
give up...

BR,

Davide

p.s.
I would strongly advise updating the tutorial: 
http://docs.tinyos.net/tinywiki/index.php/Installing_TinyOS_2.1.1
in there is suggested to use the hinrg.cs.jhu.edu/tinyos repository for karmic



On 27 Apr 2012, at 10:20, András Bíró wrote:

> If you install with dpkg: The new packages with the 2011 in the
> version number will only work on ubuntu 10.04 or newer. (and debian
> 6.0 or newer)
> 
> Andris
> 
> On Fri, Apr 27, 2012 at 2:23 AM, Janos Sallai
> <[email protected]> wrote:
>> The avr-libc packages in the stanford repository do contain these
>> files -- I have just verified it:
>> 
>> http://tinyos.stanford.edu/tinyos/dists/ubuntu/pool/main/a/avr-libc-tinyos/
>> 
>> Why don't you download the deb package directly and install it with "dpkg 
>> -i"?
>> 
>> Janos
>> 
>> 
>> 2012/4/26 [email protected] <[email protected]>:
>>> The tutorial still recommends the hinrg karmic. That's the only reason why 
>>> I stick on it.
>>> 
>>> Anyway, no luck with both repositories (hinrg and stanford):
>>> I removed and reinstalled all related avr tinyos, including the 
>>> avr-libc-tinyos.
>>> 
>>> The inttype.h together with the /usr/avr/include folder is missing.
>>> 
>>> I also tried something more rude. I autoremoved and purged tinyos then 
>>> reinstalled. Still no luck, same missing files of course...
>>> 
>>> I cannot really get it.
>>> 
>>> Any idea why?
>>> 
>>> What if i just copy the /usr/avr folder from a working system?
>>> 
>>> Thanks
>>> 
>>> Davide
>>> 
>>> 
>>> On 26 Apr 2012, at 20:01, András Bíró wrote:
>>> 
>>>> Hi,
>>>> 
>>>> On Thu, Apr 26, 2012 at 6:59 PM, [email protected]
>>>> <[email protected]> wrote:
>>>>> Hi,
>>>>> 
>>>>> Thanks for your input
>>>>> 
>>>>> avr-gcc-tinyos v4.1.2
>>>>> avr-libc-tinyos v1.4.7
>>>>> avr-binutils-tinyos v2.17
>>>>> 
>>>>> They all come from the http://hinrg.cs.jhu.edu/tinyos repository for 
>>>>> karmic.
>>>>> Anything wrong here?
>>>> 
>>>> When I last tried, the hinrg repo had an incorrectly compiled avr
>>>> toolchain. As János said, use the stanford repo instead
>>>> (http://tinyos.stanford.edu/tinyos/dists/ubuntu/). Also keep in mind,
>>>> that karmic is unsupported by canonical, and unsupported by the newest
>>>> tinyos avr toolchain (with avr-libc 1.6.7). You can still use the old
>>>> toolchain (from the stanford repo), but some new platform won't work.
>>>> 
>>>>> 
>>>>> I've double checked all tools in the toolchain with those in the 
>>>>> installing
>>>>> tutorial (
>>>>> http://docs.tinyos.net/tinywiki/index.php/Installing_TinyOS_2.1.1 ). They
>>>>> all match...
>>>> 
>>>> Yeah, someone should really update the wiki or the repo...
>>>> 
>>>>> 
>>>>> Btw, compiling for TelosB and similars work like a charm.
>>>>> 
>>>>> Any other suggestion?
>>>>> 
>>>>> Btw2, I had a look inside the /usr/avr and it looks quite empty to me. The
>>>>> inttypes.h is not there. Beside, there is an inttypes.h inside the
>>>> 
>>>> So, the hinrg repo still has incorrectly compiled avr toolchain (I
>>>> guess avr-libc was compiled without avr-gcc, and it couldn't detect
>>>> any supported target, so it's basicly an empty package).
>>>> 
>>>> Long story short: use the stanford repo.
>>>> 
>>>> Andris
>>>> 
>>>>> /usr/msp430/include/sys
>>>>> 
>>>>> Will you be so kind to post an ls -luaR of both your /usr/avr and
>>>>> /usr/msp430 ?
>>>>> I'd like to see what difference can meld find before mess with a reinstall
>>>>> of the toolchain
>>>>> 
>>>>> Follow mine
>>>>> 
>>>>> Many thanks
>>>>> 
>>>>> Davide
>>>>> 


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

Reply via email to