Manel wrote:
The OS that I use is Ubuntu. The mistake is the following:
[EMAIL PROTECTED]:~/Software/Test$make telosb
mkdir -p build/telosb
compiling mota to a telosb binary
ncc -o build/telosb/main.exe -O -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d
-Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board=
-I%T/lib/Deluge
-Wl,--section-start=.text=0x4800,--defsym=_reset_vector__=0x4000
-DIDENT_PROGRAM_NAME=\"mota\" -DIDENT_USER_ID=\"manel\"
-DIDENT_HOSTNAME=\"manel-desktop\" -DIDENT_USER_HASH=0xd2deb863L
-DIDENT_UNIX_TIME=0x456d5298L -DIDENT_UID_HASH=0xfec66479L
-mdisable-hwmul -I/opt/tinyos-1.x/tos/lib/CC2420Radio mota.nc -lm
motaM.nc:368:24: warning: no newline at end of file
nesc1: cval.c:206: cval_knownbool: Assertion `0' failed.
nesC: Internal error. Please send a bug report to the nesC bug mailing list
at [EMAIL PROTECTED]
make: *** [exe0] Error 1
A bug report needs to have the necessary information for me to reproduce
it, or it's nearly useless. That means:
- nesC version
- a description of your environment (Linux vs Windows is the most
important bit)
- source code that causes the problem (*)
- command(s) used to compile the source code
*: Source code from TinyOS itself can be omitted as long as you specify
which (exact) version of TinyOS you are using. If you don't want to send
out your own source code for any reason, you'll need to create something
that reproduces the problem that you are happy to send out.
David Gay
PS: All of this is standard procedure for bug reports for compiler-style
tools...
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
