BLIP: update ipv6 short addr expansion

According to RFC 6282 Header compression for 6LoWPAN,generating IP
Address from short address should be of the form fe80::00ff:fe00::xxxx
where xxxx is our 16-bit address,but in the current stack it is
generating as fe80::panid:00ff:fe00:xxxx Changing this will make it
compatible with linux 6lowpan stack .If we use the current stack for
communicating with the linux 6lowpan stack we will receive checksum
error because the checksum generated using the address by the BLIP Stack
will differ with the checksum generated with the address by the linux
stack and hence packet get discarded.
BLIP: don't wait for ack on multicast fragments

One more problem present in the current BLIP Stack is sending the
multicast packets more than the MTU. If we try to send a packet more
than its MTU,it will be fragmented and BLIP stack sends the first
fragment only once the acknowledgement is received he sends the
subsequent fragments,but if we are sending a multicast fragment we are
not going to receive a acknowledgement so BLIP stack will discard the
remaining fragments , so while sending we have to check whether we are
sending an multicast packet or unicast packet.
Merge branch 'md-jamal-blip-rfc6282'
packaging: clean up

o INSTALLDIR had an extraneous '/' at the end.  remove.
  (functions-build.sh)

o remove extraneous 'cd ${BUILD_ROOT}'s from build.sh.  fixed
  installto so no longer needed.
packaging/tinyos-tools-15: add 1.5.0 for dev trunk

tinyos-tools-1.5.0 (tinyos-tools-15) supports the development trunk
after 6dc714b and prior to bringing in issue #190.  This is the
changes that rippled from .platform changing to platfom.

closes #291
tinyos-tools-stable now compiles the current stable (1.4.2) version. Fixes #294
some fix for cygwin
removed generated files
packaging/tinyos-tools: update comments about how tinyos-tools is built.

In particular what kind of dependencies tinyos-tools has.
packaging/tinyos-tools: make tinyos-tools-15 (devel) package version use SHA

Development trunk builds get packaged using the SHA of the tip of the current
branch as the package version.   Makes it abundently clear that the package
is dependent on the current state of the trunk.
added more comment about the disable_cross_compiler patch
updated to 6.0.1 and removed deb support
added patch for gcc bug 60486
Removed improper files from the repository.

- Removed all old .cvsignore files.
- Removed tunit.extra. (references toscontrib)
  This extra relies on having toscontrib, so it should be in toscontrib.
  By setting the TINYOS_ROOT_DIR_ADDITIONAL variable this should be easy.
- Removing eval-crash.diff
  This seems to be an errantly commited file.
Updated .gitignore

Added all of the various make output
Removed assumed environment variables

Many places in /tools (and in READMEs) code or documentation assumes
that there are environment variables set. In order to remove the
requirement that environment variables need be set, this commit changes
structure to work without the environment variables. Generally, this
means adding an argument so that callers of scripts can pass in the
information the environment variable used to provide.

A major consequence of this is that ncc --print-tosdir no longer works.
Any instance of this is now removed.
Set TINYOS_ROOT_DIR in Makefile, change var names

This removes the non-desireable requirement that a user must set
environment variables in order to build TinyOS. The $TOSROOT variable
then trickles through the makefiles and in makerules $TOSDIR is set.

The overhead to do this is small (1 line in each application makefile)
but it should really help make tinyos more user friendly.

TOSROOT is set with "?=" meaning that it won't override TOSROOT if it is
already set by an environment variable.

Makefile.include in the root sets TOSDIR and MAKERULES before including
$(MAKERULES). This allows the current env variables to override the
derived settings.

Changing TinyOS Make system variable names:

| Old Variable        | Proposed Variable Name      | Default Value                    | Purpose                                                             |
|---------------------|-----------------------------|----------------------------------|---------------------------------------------------------------------|
| TOSROOT             | TINYOS_ROOT_DIR             | relative to application Makefile | Base for all other variable defaults                                |
| TOSDIR              | TINYOS_OS_DIR               | $TINYOS_ROOT_DIR/tos             | Path to `/tos` folder containing main system source to compile with |
| TINYOS_MAKE_PATH    | TINYOS_MAKE_DIR             | $TINYOS_ROOT_DIR/support/make    | Path to `/make` that contains the targets, extras, and rules        |
| MAKERULES           | TINYOS_MAKERULES            | $TINYOS_MAKE_DIR/Makerules       | Path to main makefile                                               |
| TINYOS_MAKELOCAL    | TINYOS_MAKELOCAL            | $TINYOS_MAKE_DIR/Makelocal       | Path to optional Makelocal file                                     |
| TINYOS_MAKEDEFAULTS | TINYOS_MAKEDEFAULTS         | $TINYOS_MAKE_DIR/Makedefaults    | Path to Makedefaults                                                |
| TOSMAKE_PATH        | TINYOS_MAKE_DIR_ADDITIONAL  | unset                            | Space separated paths of additional `support/make` directories      |
Moved support code to tools/, now gets installed

In order to remove more environment variable usage, the tinyos python
code must be installed on the user's system instead of in the tinyos
tree. This commit moves all the python to tools so automake will install
it. Doing this requires one subtle change: "import tos" will no longer
work. It needs to be "from tinyos import tos" now.

I think I updated all of the relevant files.

One note: python3 is handled a bit weirdly, and therefore tos-serlook.py
may not be able to find tinyos.misc.hexdump. It seems that
/usr/local/lib/python3/dist-packages is not in the search path by
default. I fixed this by adding "tinyos.pth" containing the correct
directory to /usr/local/lib/python3.2/dist-packages.

The CoAP support code will now be built and installed with tinyos-tools.

I updated coap.extra to reflect the moved .c files.

Moved blip support to /tools directory

Will not compile the blip sdk code on cygwin as it only supports linux and mac.

Moved sf and serial_tun to /tools

I have no idea if anyone still uses this code. The configure script for
sf is out of date and does not work with newer automake (I updated it).

I also renamed some binaries so they can be installed. If the user is
installing TinyOS, they may as well _install_ tinyos. Why make them hunt
around for different binaries? If something shouldn't be installed, then
the question is why is it distributed with the main TinyOS source? It
should be some sort of optional extra somewhere, not part of the main
source. Hard drives are big, just give me all of the TinyOS tools.

Because there are 2 sf applications, the cpp version is named sf2.

Moved java to /tools; Removed env vars

Java is now compiled and installed with tinyos-tools

Moved imote2-ocd-program.py to /tools

No reason to have the makefile need to dig into tools in order to
install to the hardware.
Changed tinyos-tools version to 2.2.0
Removing ncc, nesdoc, mig, ncg

ncc is a very strange step in the build process. It is basically a
magical perl script that sets a bunch of include directories, but is
really just another opaque layer to figuring out how tinyos is getting
built. While trying to re-write it to make it a bit cleaner and smarter,
I had a realization: Why are include directories and nesc flags (which
are used to compile code) smack dab in the middle of a src folder
(tos/platforms/<platform>/platform)? Why isn't all of that contained in
the make system (where you would expect it to be? In fact, why do we
need these magic files (platform, family, sensor) at all?

This commit addresses these questions by starting to move what was in
the platform (etc.) files into the make system. In this way, X.target
files include Y.platform files, Z.sensor files, (etc.) in order to get
all of the relevant flags without needing to write perl code.

Also, tos-sub-tosdir tool makes the %T flag magical. Instead of just
being replaced with $TOSDIR, it is replaced with all of the $TOSDIR
paths that point to actual folders. This allows for first class support
for out of tree platforms, as they will be able to use the %T syntax and
have it just work. This is convienent because if the platform ever gets
moved to tinyos-main it will just work.

Removed nesdoc; Use nesdoc-archive instead

nesdoc was another ncc style script, now you just call the python
scripts directly.

Removed mig and ncg

mig and ncg are more examples of magic scripts, mostly because they use
ncc. To remove them, I replaced all instances of mig with nescc-mig and
ncg with nescc-ncg. Then I added the correct argument to make sure they
still execute correctly.

This isn't as bad as it sounds due to $(NESC_PFLAGS) being very useful.
That variable basically replaces what ncc used to do.