summaryrefslogtreecommitdiff
path: root/nuttx/configs
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2013-04-11 06:53:26 -0600
committerGregory Nutt <gnutt@nuttx.org>2013-04-11 06:53:26 -0600
commitacee27d02f46f30ababa67b1164707e662af574a (patch)
treeec1530110dbe9525a9155363f1ff4758d2635b43 /nuttx/configs
parenta8dd3379dc6a4543a94831d470488d9cced645cb (diff)
downloadpx4-nuttx-acee27d02f46f30ababa67b1164707e662af574a.tar.gz
px4-nuttx-acee27d02f46f30ababa67b1164707e662af574a.tar.bz2
px4-nuttx-acee27d02f46f30ababa67b1164707e662af574a.zip
Updated to documentation and README files
Diffstat (limited to 'nuttx/configs')
-rw-r--r--nuttx/configs/qemu-i486/README.txt14
1 files changed, 12 insertions, 2 deletions
diff --git a/nuttx/configs/qemu-i486/README.txt b/nuttx/configs/qemu-i486/README.txt
index 254f8a131..d505bd55c 100644
--- a/nuttx/configs/qemu-i486/README.txt
+++ b/nuttx/configs/qemu-i486/README.txt
@@ -90,8 +90,18 @@ Toolchains
not produce ELF final binaries but, rather, DOS MZ executables (i.e., .exe
files). Those cannot be used with QEMU.
- The file */setenv.sh should be modified to point to the correct path to the
- GCC toolchain (if different from the default in your PATH variable).
+ NOTE: It has also been reported to me that with a certain Ubuntu virtual
+ installation, the native x86 did not build correct i486 code. Other
+ installations of the same vintage do not have such issues. However,
+ there is always a possibility that any GCC release will be incompatible
+ with i486. That fallback used by this person in this particular case
+ was to use the Buildroot i486 cross-development tool described below. I
+ suspect that this was not necessary, but it was a simple work-around
+ that allowed that person to build a work-able system.
+
+ In any event, the file */setenv.sh should be modified to point to the correct
+ path to the GCC toolchain (if different from the default in your PATH
+ variable).
Cygwin Buildroot Toolchain
--------------------------