Provide correct path to toolchain

The cross compiler toolchain used by Asuswrt has its own headers and
libraries, which represent the headers and libraries of the target
system. The path was hard coded /opt/brcm/hndtools-mipsel-uclibc-4.2.4
when the toolchain was built. However, the current directory tree does
not create this path, which causes it to fallback on the system compiler
directories. This fallback is a bad idea, but unfortunately, the
toolchain does it anyway.

While the fallback is done for both libraries and headers, the inherit
incompatibility of MIPS and x86 will always result in build failures
when the two are mixed. This forced Asus to design the firmware's build
system to always rely upon the MIPS binaries. Unfortunately, the same is
not true for headers. Asus worked around the problem by using software
in their firmware that is at least semi-compatible with the Ubuntu
development packages.

That avoided build failures on Ubuntu. However, the massive hack that
Asus employed had three additional consequences:

1. 	Compiler warnings

2.	Runtime failures whenever assumptions about bit fields are
	broken by the host system's headers.

3. 	Build failures whenever required headers are either absent or
	incompatible on the host system.

We can resolve #1, #2 and most instances of #3 simply by
installing the proper symlink. Full resolution of #3 relies on
ensuring that the proper headers are available at all times. We can
accomplish this in any of two ways on a case-by-case basis:

1.	Install header files into the toolchain's include directory.
	This is basically what Asus did, with the caveat that we would
	no longer be relying on the host system's include directory.

2.	Modify the individual build systems to pass the proper paths to
	dependent headers. This is how Asus avoided mixing libraries.

The former requires developers emulate a package manager while the
former is fairly easy to do without one, so it should make the most
sense to do the latter in additional patches. This would eliminate the
need for people building the firmware to install -devel packages for
various headers and also ensure that any GNU/Linux distribution can run
the same build process. If some work is done to document how the cross
compiler can be built, then it would become rather easy to build the
firmware on any UNIX-compatible system, such as *BSD, Cygwin, Mac OS X,
Solaris and others.

Signed-off-by: Richard Yao <ryao@cs.stonybrook.edu>