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