I have also experienced these problems, building for linux.
V3.0 & V3.current - I had to also manually create msp1 & msp2 directories to get it to build. This problem does not appear to be related to Cygwin, the directories just don;t exist, and nothing that I can find tries to automatically create them.
V3.current - I had to manually copy the include files from cvs to the install directory between building binutils and building the compiler. The version of stdio.h that is missing is the one from the mspgcc library, which is required by the cross compiler built when building the compiler (not the stdio.h of the system compiler), so it is not a problem with the install of Cygwin. The problem is, the mspgcc library is only built after the compiler is built, and so in the normal manor, the include files are not installed. The only way i can see this working for anyone is if they do incremental builds. If you delete your target where everything gets installed before building, then it wont compile the compiler, because stdio.h wont be there from the previous build.
V3.current - building does still point to the V3.0 libraries explicitly, again if you do a clean build and install to a fresh directory, it wont work, without creating a link from V3.0 to the version you actually compiled.
I actually find GNU Make, autoconf and Configure nightmarishly over complicated, so I can understand why these problems exist. I feel sorry for the person that has to maintain these files, but these are the build problems I am currently aware of. All of them can be worked around by producing links, and manually copying files, etc. But they do make it difficult for someone to get started.
As a pointer, if anyone wants a really easy build system for their projects, check out JAM. I've been using it for a while now and there is no way i'm going back to GNU Make. It automatically deals with file dependencies, and makes your make file trivial by comparison to other systems. Freetype use it in preference to AutoMake/Autoconf: check out :- http://freetype.sourceforge.net/jam/index.html
Steven Johnson Neurizon Pty Ltd Bill Knight wrote:
Well I copied stdio.h and the sys directory frrom the include directory of a previous version of msp430 into the mspgcc build tree. That cleared the error and everything appears to have finished up just fine. It would be great if the error could be found and corrected or at least the build directions modified. They are a bit out-of-date. Also the Makefile for building the libraries needs to be edited to reflect the different gcc-lib/msp430 subdirectory. 3.0->3.2 in my case. As for Cygwin - it doesn't seem to be able to create directories automatically in some cases. I had to manually create the msp1 & msp2 directories in the library build tree. -Bill Knight R O SoftWare ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
