I think technically the code in the bsd is covered by the bsd licence and the code in gnu and stdlib is covered by the gnu licence. As I understand it, you can move bsd code to gnu but not vice versa. My suggestion would be to remove the gnu and bsd directory references from the Makefile and just use what is in stdlib.
Robert Phil Sutherland wrote: > > There's a separate problem with strtoul, but I'm not sure of the proper > way to fix it. There appear to be three version of strtoul.c in the > msp430-libc/src tree, one in each of the bsd, gnu and stdlib > directories. The one in stdlib appear to be based on the bsd version, > but with a slight change to fix a bug. However, in a normal build the > source file in the bsd directory appears to be the one used, and strtoul > remains broken - it consistently returns 0xffffffff. I fixed the problem > locally by placing the patched version of the file from stdlib back into > the bsd directory. I suspect the correct fix is to do this, but also to > remove the file (and strtol.c, and qsort.c - the other duplicated files) > from stdlib altogether and rely on the bsd or gnu files to be used > instead - this gets rid of a source of confusion. > -- View this message in context: http://old.nabble.com/430X-patch%3A-ldiv.S%2C-and-strtoul-problem-tp27293374p27396902.html Sent from the MSP430 gcc - Users mailing list archive at Nabble.com.
