diff options
| author | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2009-11-30 17:47:54 +0000 |
|---|---|---|
| committer | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2009-11-30 17:47:54 +0000 |
| commit | 3945cfc8fefbbf42d19d08a4d55009b17ac0aab7 (patch) | |
| tree | de61f8d203e80865da2778f721b92034d60dc446 /misc | |
| parent | 0d2ea2ab429d8205c520ce866ca13d020336ebad (diff) | |
| download | nuttx-3945cfc8fefbbf42d19d08a4d55009b17ac0aab7.tar.gz nuttx-3945cfc8fefbbf42d19d08a4d55009b17ac0aab7.tar.bz2 nuttx-3945cfc8fefbbf42d19d08a4d55009b17ac0aab7.zip | |
Update Cygwin build instructions
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2292 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'misc')
| -rw-r--r-- | misc/buildroot/configs/README.txt | 18 |
1 files changed, 15 insertions, 3 deletions
diff --git a/misc/buildroot/configs/README.txt b/misc/buildroot/configs/README.txt index 3bcf6c45b..82ddeda9d 100644 --- a/misc/buildroot/configs/README.txt +++ b/misc/buildroot/configs/README.txt @@ -143,7 +143,7 @@ GENERAL BUILD STEPS Cygwin GCC BUILD NOTES ^^^^^^^^^^^^^^^^^^^^^^ - Cygwin normally creates a /home directory with your Windows user name. Unfortunately, + o Cygwin normally creates a /home directory with your Windows user name. Unfortunately, that could very likely include spaces. In that case, the Cygwin build will have lots of problems. Here is how I worked around that: @@ -156,7 +156,7 @@ Cygwin GCC BUILD NOTES to either edit the setenv.sh file to reference this new location, or else move resulting build diectory. - On Cygwin, the buildroot 'make' command will fail with an error like: + o On Cygwin, the buildroot 'make' command will fail with an error like: "... build/genchecksum cc1-dummy > cc1-checksum.c @@ -193,4 +193,16 @@ Cygwin GCC BUILD NOTES cd - # Back to the buildroot make directory make # Restart the build - + + o Once I had problems building the toolchain on Cygwin. In this case, I + would occasioinally get "Permission denied" errors will trying to configure + the toolchain. My hunch is that this error was caused because of failures + to remove some temporary files (like conftest.c). Perhaps there errors + occurred because some other application opened those files too??? Perhaps + a virus scanner. + + Sometimes when this occurs, the build continues to execute. If that is + the case, it could end-up making a bad toolchain??? In this case, you need + to hit Control-C to stop the build. Normally, however, the "Permission + denied" error causes the configure script to stop. In either case, if you + just restart the make, the build will continue past the failure point.
\ No newline at end of file |