Hello All:
I've taken msp430-libc from that dir in the CVS. I've build myself
binutils-2.18 and gcc-3.2.3 for msp430. Now it's libc turn.
I'm building/packaging libc for msp430 and I have some questions about the
build process:
· Why is libc/libm/libfp build for both msp1(-mmcu=msp1) and msp
(-mmcu=msp2) and/or not any other? e.g.: why not building only for msp1 or
also for msp430xG4616
· Why is msp1 lib* installed in {prefix}/lib/? why not msp2? I wonder if
that file should be there, and again I don't know why the duplication for
msp1 and msp2.
· Suggestion: msp1 and msp2 dirs are not created by the build system. Find
attached a (ugly)patch to solve that.
· Not strictly libc related, but I guess the msp430-libc4 status depends
on the gcc-4.x port for msp430 toolchain. Since I haven't heard anything
about it on the list, I should consider it is still outstanding. Any news?
How usable is that? Latest information I got comes from "problems building
gcc-4.1.1" thread by Chris Liechti on 2006, 23rd Nov.
Regards,
--
Raúl Sánchez Siles
Index: msp430-libc/src/Makefile
===================================================================
RCS file: /cvsroot/mspgcc/msp430-libc/src/Makefile,v
retrieving revision 1.45
diff -u -r1.45 Makefile
--- msp430-libc/src/Makefile 23 Apr 2006 16:37:22 -0000 1.45
+++ msp430-libc/src/Makefile 14 May 2008 11:39:52 -0000
@@ -143,7 +143,10 @@
libc_msp430_objs_2 = ${libc_msp430_c_objs_2}
-build-libc: ${libc_libs}
+build-libc: mspdirs ${libc_libs}
+
+mspdirs:
+ mkdir msp1 msp2
${libc_msp430_objs_1}: msp1/%.o: stdlib/%.c
${CC} -c ${CPPFLAGS} ${ALL_CFLAGS} -mmcu=msp1 -c $(ABSPATH)$< -o $@
