README.m68k 1.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. README for uC-libc on the m68k[nommu] architecture
  2. James Graves <jgraves@deltamobile.com>
  3. For now (2001/1/9) support for the m68k should be considered "alpha"
  4. quality at best. It mostly works OK for some of the stuff I'm working
  5. on, but you can't fully compile other things (like the user
  6. applications for uClinux). Needs lots more testing.
  7. Only developed/tested with m68k-pic-coff-gcc 2.7.2.3-pic-060999, from
  8. Lineo.
  9. Configuration:
  10. Read and edit the Config file, carefully.
  11. TARGET_ARCH=m68k
  12. CROSS_COMPILE = m68k-pic-coff-
  13. CC = $(CROSS_COMPILE)gcc
  14. STRIPTOOL = $(CROSS_COMPILE)strip
  15. KERNEL_SOURCE=/opt/uClinux/linux
  16. HAS_MMU = false
  17. HAS_FLOATS = false
  18. MALLOC = malloc-simple
  19. INSTALL_DIR = /opt/uClinux/m68k-pic-coff
  20. The regular malloc library is broken, dunno why. Use
  21. simple-malloc.
  22. Installation:
  23. Theoretically, you should be able to install right over the
  24. existing uC-libc 0.9.1 files in
  25. /opt/uClinux/m68k-pic-coff/include, but I recommend cleaning
  26. out all the include files there.
  27. The only file in there that's not from the old uC-libc is
  28. assert.h, but I don't know why that would be the valid copy.
  29. run:
  30. make install
  31. Problems:
  32. I _may_ be able to help if you run into problems. Create a
  33. really, really short program that demonstrates the problem,
  34. and contact me.
  35. TODO:
  36. Fix vfork().
  37. Does crt0.o still need to be a separate file? Can't I just
  38. stick it in libc.a and be done with it? Is that specified in
  39. the GCC link options?