From: Peter J. <pwj...@ya...> - 2008-12-15 10:51:12
|
Hi Bernard, Yes I would agree compiling msp430-gcc is complex, there are quite a few pieces that all need to hang together to make it work, and many of the tools are changing also. A lot of the problem is the support for the ever increasing number of devices in all parts of the tool chain (binutils, gcc, msp430-libc, gdb and gdbproxy are all affected by new devices). I did also find that the patches for binutils 2.18 didn't work for 2.19, although I think I have a working build for 2.19 now. The windows build is done using the makefiles and scrips in the packaging directory, this way the source for the tools is controlled and its a package we know works. Yes there is a problem with binutils-2.18 and a modern compiler because its header files specify that the return value should be checked, I found that this had been fixed in bintuils-2.19. Attached is a patch that fixes this problem for binutils-2.18 Looks like we have to roll some of this into the packaging directory, and get patches working for 2.19. I had to use make MAKEINFO=/usr/bin/makeinfo to get binutils-2.18 to find makeinfo on ubuntu Hope that helps, Peter ________________________________ From: Bernard Mentink <bme...@gm...> To: pwj...@ya...; GCC for MSP430 - http://mspgcc.sf.net <msp...@li...> Sent: Monday, 15 December, 2008 8:32:31 AM Subject: Re: [Mspgcc-users] msp430-libc compile problems. Hi Peter, Compiling the tools is becoming a real pain. I have never had trouble like this compiling mspgcc in the past ( a year or two ago..). I have applied the patches fine to a fresh get of binutils-2.18 (these patches would not work for 2.19). However when I tried to compile 2.18 I now get this error. ---------------------------------- error ------------------------------------------ gcc -DHAVE_CONFIG_H -I. -I.././binutils -I. -D_GNU_SOURCE -I. -I.././binutils -I ../bfd -I.././binutils/../bfd -I.././binutils/../include -DLOCALEDIR="\"/usr/loc al/msp430/share/locale\"" -Dbin_dummy_emulation=bin_vanilla_emulation -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c .././binutils/objdu mp.c cc1: warnings being treated as errors .././binutils/objdump.c: In function â?~print_lineâ?T: .././binutils/objdump.c:1143: error: ignoring return value of â?~fwriteâ?T, decl ared with attribute warn_unused_result make[4]: *** [objdump.o] Error 1 make[4]: Leaving directory `/home/bmentink/mspgcc/temp/binutils-2.18/binutils' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/bmentink/mspgcc/temp/binutils-2.18/binutils' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/bmentink/mspgcc/temp/binutils-2.18/binutils' make[1]: *** [all-binutils] Error 2 make[1]: Leaving directory `/home/bmentink/mspgcc/temp/binutils-2.18' make: *** [all] Error 2 -------------------------------------------------------------------------------------------------------------------------------- Any further ideas? Do I also have to patch the msp430-gcc compiler with the appropriate files from the packages/patches directory? It seems pretty bad to me that you can't build the tools with "released" versions because of the "released" msp430-libc !!.. Cheers, Bernie bmentink@laptop:~/mspgcc/temp/binutils-2.18$ -------------------------------------------------------------------------------------------------------------------------- On Sat, Dec 13, 2008 at 5:03 PM, Peter Jansen <pwj...@ya...> wrote: Hi Bernard, > ... <snip> > I have built the latest 3.4 version of msp-gcc as the > devices supported by > by 3.3 were even more limited. > I had a look in the makefile of msp430-libc and there are > heaps of devices there that are not in the compiler list. Ok If you use binutils 2.18 (or 2.19) then you need to apply the patches in http://mspgcc.cvs.sourceforge.net/viewvc/mspgcc/packaging/patches to get support for the 2001 device. You get get these files from cvs by, cvs -z3 -d:pserver:ano...@ms...:/cvsroot/mspgcc co packaging apply these to the binutils tree, eg cd binutils-2.18 export PATCHES=../packaging/patches patch -p1 < $(PATCHES)/binutils-2.18-14x1-20x1-20x2-20x3-22x4-42x-42x0-461x.patch patch -p1 < $(PATCHES)/binutils-2.18-msp430x24x-msp430x26x.patch patch -p1 < $(PATCHES)/binutils-ld_scripts.patch patch -p1 < $(PATCHES)/binutils-2.18-430X.patch > What is the story here, do I need an even later version of > the compiler? I have tried to compile the 4.1.1 version of msp-gcc but > I am getting compile errors ... looks like it is not quite > ready yet. The version of gcc to use is 3.2.3 (as on the web page), gcc-4.x does not work, 3.2.3 is the only choice and is the one that the latest devices have been added too. Peter Jansen Start your day with Yahoo!7 and win a Sony Bravia TV. Enter now http://au.docs.yahoo.com/homepageset/?p1=other&p2=au&p3=tagline ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Mspgcc-users mailing list Msp...@li... https://lists.sourceforge.net/lists/listinfo/mspgcc-users Start your day with Yahoo!7 and win a Sony Bravia TV. Enter now http://au.docs.yahoo.com/homepageset/?p1=other&p2=au&p3=tagline |