dev-manual: Updated path in cross-GDB package example.

Fixes YOCTO #2827

Replaced the path where one findes the binary for the meta-
toolchain to a more recent example that was built from
the beagleboard and using arm.

(From yocto-docs rev: 020a7fcd7f99c50d32e831b8d51150e8db8ab4e9)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 1abc91431da49aa4ba388ab85946695953b18acc..dee72060189d312a1243b9df19b2cf8628a500ae 100644 (file)
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3166,9 +3166,10 @@
                     A suitable GDB cross-binary is required that runs on your host computer but
                     also knows about the the ABI of the remote target.
                     You can get this binary from the meta-toolchain.
-                    Here is an example:
+                    Here is an example where the toolchain resides in the
+                    default directory <filename>/opt/poky/1.4/sysroots</filename>:
                     <literallayout class='monospaced'>
-     /usr/local/poky/eabi-glibc/arm/bin/arm-poky-linux-gnueabi-gdb
+     /opt/poky/1.4/sysroots/i686-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/arm-poky-linux-gnueabi-gdb
                     </literallayout>
                     where <filename>arm</filename> is the target architecture and
                     <filename>linux-gnueabi</filename> the target ABI.