Hello Razvan ME :
thank you for your reply !!
it is right that i am using an older tools package . when i put the
tinyos-2.x tree (.git version) in the directory of opt/ and go to
tinyos-2.x/tools .
./Bootstrap
the reslut is : (*there are some warning , i don't know why* )
+ aclocal
+ autoconf
+ [ -d config-aux ]
+ automake -a -c
+ set -x
+ cd platforms/mica/uisp
+ ./bootstrap
autoheader: WARNING: Using auxiliary files such as `acconfig.h',
`config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `
config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows to define a template
without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see
the
autoheader: WARNING: documentation.
+ rm -f config.cache src/config.cache
then ./configure , the result is :
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ranlib... ranlib
checking for perl... /usr/bin/perl
checking for python... /usr/local/bin/python
checking for nescc... /usr/bin/nescc
configure: Default ncc build target is mica
configure: ...but using a tos/.default-platform file is a better choice
configure: TinyOS directory is /opt/tinyos-2.x/tos
checking for cygwin... yes
checking for JDK location... /cygdrive/d/Program Files/Java/jdk1.5.0_01
configure: creating ./config.status
config.status: creating Makefile
*config.status: error: cannot find input file: Makefile
.in
*
*there is an error , so it jump out , what is the reason , Razvan ME?*
i also download the cvs version(2008.4.28) , and copy the tools folder to
the tinyos-2.x/opt/ of .git verion and use the command of ./Bootstarp
./configure , there is no error , and then i go to tinyos/misc, use the
command make , make install , there is no error too. i don't know whether it
is suitable to copy the folder tools from cvs version to git version .
i also test the application of tests/deluge/Blink , it is all right *except
that the mote(micaz) does not blink the yellow led (the red led blink
quickly)and i can ping the mote , there is no response* , what is reason ,
Razvan ME ?
*about the mica2 platform :*
because i only have one micaz mote , and have many mica2 motes , so i want
to modify the deluge and make it support the mica2 platform , how should i
do ,Razvan ME? can you help me ? thank you very much !!
2008/5/14 Razvan Musaloiu-E. <[EMAIL PROTECTED]>:
> Hi!
>
> On Wed, 14 May 2008, jiwen zhang wrote:
>
> Hello :
>> I am researching deluge and have some problems when i use the version
>> of tinyos-2.x.git from http://hinrg.cs.jhu.edu/git/ on the day of
>> 2008-5-4.
>> 1. when i put the tinyos-2.x-git tree in two different computers , i
>> find the compile choices are different. for exaple , when i compile the
>> application of Blink in the directory of
>> /opt/tinyos-2.x/apps/tests/deluge/Blink and the compile choice in one
>> computer is that "-D*IDENT_PROGRAM_NAME*=\"BlinkAppC\"
>> -*DIDENT_USER_ID*=\"Administrator\"
>> -*DIDENT_HOSTNAME*=\"zjw\" -*DIDENT_USER_HASH*=0x2567b0c3L -*
>> DIDENT_UNIX_TIME*=0x482a65deL -*DIDENT_UID_HASH*=0xad6bbf5dL" and the
>> other
>> is "-D*IDENT_APPNAME*=\"BlinkAppC\" -D*IDENT_USERNAME*=\"zhangjiwen\" -D*
>> IDENT_HOSTNAME*=\"zjw\" -D*IDENT_USERHASH*=0x0eac215cL
>> -D*IDENT_TIMESTAMP*=0x482a64abL
>> -D*IDENT_UIDHASH*=0x9bde9ac6L" . i use *the same Tinyos tree* , why are
>> the
>> compile choices different ? * where* are these macroes such as
>> IDENT_USERNAME , IDENT_TIMESTAMP defined ?
>>
>
> Those flags are generated by tos-ident-flags. The file is part of the tools
> package and the source of it is in:
> tinyos-2.x/tools/tinyos/misc
> The flags are suppose to be different because their purpose is to uniquely
> identify an image.
>
> 2. some files in the directroy of tos/lib/deluge/ contains the macroes
>> for example , in the file DelugeP.nc , there is a macro named
>> IDENT_UIDHASH,
>> in the file FlashVolumeManagerP.nc , there are macroes named
>> IDENT_APPNAME,IDENT_TIMESTAMP,IDENT_UIDHASH and so on . so when i compile
>> the application of Blink in in the directory of
>> /opt/tinyos-2.x/apps/tests/deluge/Blink on one of the two computers, it
>> will give errors like "IDENT_APPNAME not defined" , the reason is obvious
>> ,
>> should i modify all the names which the errors tell me not defined ? i
>> think
>> there should be a easy way , because the deluge should be cross-PC(-:)) .
>>
>
> You are probably using an older tools package. Can you install the tools
> from sources (from tinyos-2.x/tools)?
>
> 3 . If i want to repot deluge to the platform of mica2 , which files
>> should i modity ? and how ?
>>
>
> What is 'repot'? :P I don't have any mica2 motes but the code works fine on
> micaz.
>
> --
> Razvan ME
>
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
