Hi, I spent some time today figuring out why building, e. g., Blink would fail in bogus ways on a fresh installation, like
> make telosb
mkdir -p build/telosb
writing TOS image
msp430-objdump: 'build/telosb/main.exe': No such file
0 bytes in ROM
0 bytes in RAM
msp430-objdump: 'build/telosb/main.exe': No such file
Cannot open ihex file: No such file or directory
make: *** [build_tosimage] Error 2
or
> make telosb
mkdir -p build/telosb
msp430-objdump: 'build/telosb/main.exe': No such file
writing TOS image
0 bytes in ROM
0 bytes in RAM
compiling BlinkAppC to a telosb binary
ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -Wall
-Wshadow -Wnesc-all -target=telosb
-fnesc-cfile=build/telosb/app.c -board=
-DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\"
-DIDENT_USERNAME=\"andrey\" -DIDENT_HOSTNAME=\"ookami\"
-DIDENT_USERHASH=0xe1dc6621L -DIDENT_TIMESTAMP=0x4aa8e93bL
-DIDENT_UIDHASH=0x72f17a3cL BlinkAppC.nc -lm
msp430-objdump: 'build/telosb/main.exe': No such file
Cannot open ihex file: No such file or directory
make: *** [build_tosimage] Error 2
make: *** Waiting for unfinished jobs....
compiled BlinkAppC to build/telosb/main.exe
. Eventually I found out that this was due to my default make options,
"-j3", which enable building targets in parallel.
It would be nice if, say, the Getting Started tutorial contained a note
for users to disable their make's jobserver, so that no one trips on
this in the future.
--
Regards,
Andrey Vihrov <[email protected]>
signature.asc
Description: Эта часть сообщения подписана цифровой подписью
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
