Peter Bigot wrote: > How did you build mspgcc4? The paths you have don't look like the > ones mspgcc4's build scripts use. (BTW, you should not have to add > the libexec path. The main tool driver will find the pieces it needs > from there.) > > If you add -v to the command line, do you see it trying to access the > old compiler or binutils?
Hi Peter, Thanks, I know you are busy. I got those from sourceforge, a zip labeled something like window binaries. Anyway, I bit the bullit, got all the cygwin tools installed and built it on this machine. What an adventure! :) I copied the opt/xx folder to the other computer and voila, it works fine. I didn't get the gdb tools compiled. When it got to 'checking pthread.h' my computer went into overdrive and would not respond. I had to unplug it to reboot. But using older gdb tools seem to work just fine. (gdb dated 2/18/10, proxy dated 6/19/08 ) I debug with eclipse so didn't build insight. But I will try it later just cause... Now that I have the source installed and building, I should learn more about it. Best, Dan. ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
