Sorry to intrude into your mailboxes .
I did a fresh install of tinyos2.0 beta on my linux box running FC5.
I followed the "fresh" tinyos-2.0beta installation instructiosn to a T, and at the end of the installation set all the environment variables, by including lines of the form :
export TOSROOT="/opt/tinyos-2.x"
in my .bashrc file.
I am getting the following error(in blue below), when i try to make the tinyos-2.x/apps/Blink application for "micaz":
<--------------------------SNIPPET------------------------------->
[EMAIL PROTECTED] apps]$ pwd
/opt/tinyos-2.x/apps
[EMAIL PROTECTED] apps]$ cd Blink/
[EMAIL PROTECTED] Blink]$ ls -alp
total 28
drwxr-xr-x 3 spiff root 4096 Jul 11 18:50 ./
drwxr-xr-x 13 spiff root 4096 Jul 11 15:25 ../
-rw-r--r-- 1 spiff root 2125 Feb 4 06:20 BlinkAppC.nc
-rw-r--r-- 1 spiff root 2387 Feb 16 22:18 BlinkC.nc
drwxrwxr-x 3 spiff spiff 4096 Jul 11 18:50 build/
-rw-r--r-- 1 spiff root 42 Jan 30 02:00 Makefile
-rw-r--r-- 1 spiff root 682 Jan 30 02:00 README.txt
[EMAIL PROTECTED] Blink]$ make micaz
mkdir -p build/micaz
compiling BlinkAppC to a micaz binary
ncc -o build/micaz/main.exe -Os -finline-limit=100000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, components)' -fnesc-dumpfile=build/micaz/wiring- check.xml BlinkAppC.nc -lm
In file included from /opt/tinyos-2.x /tos/system/TinySchedulerC.nc:41:
In component `McuSleepC':
/opt/tinyos-2.x/tos/chips/atm128/McuSleepC.nc: In function `McuSleep.sleep':
/opt/tinyos-2.x/tos/chips/atm128/McuSleepC.nc:112: implicit declaration of function `pgm_read_byte'
make: *** [exe0] Error 1
[EMAIL PROTECTED] Blink]$ uname -a
Linux spaceman-spiff 2.6.16-1.2111_FC5smp #1 SMP Thu May 4 21:35:09 EDT 2006 i686 i686 i386 GNU/Linux
<--------------------------SNIPPET------------------------------->
I tried making it for a different platform, mica2, but i am still getting the same error
Can you guys help me fix/diagnose the error ?
Any suggestions/ideas/workarounds/hacks welcome
I am pretty confident that it is not a tinyos-2.x install/setup issue.
Thanks a ton
cheers
ashish makani
[EMAIL PROTECTED]
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
