source: rtems/c/README.DOS @ 3d3a3590

4.104.114.84.95
Last change on this file since 3d3a3590 was 3d3a3590, checked in by Joel Sherrill <joel.sherrill@…>, on Jul 26, 1995 at 3:15:30 PM

updates for msdos/go32 from Bryce Cogswell

  • Property mode set to 100644
File size: 2.6 KB
Line 
1#
2#   $Id$
3#
4
5tools
6-----
7The RTEMS build procedure was designed with the capabilitiies of a
8typical UNIX computer in mind.  Making this procedure work under MS-DOS
9is not that difficult but requires that MS-DOS versions of a number
10of UNIX utilities be acquired and installed.  For time being, the
11best advice which can be offered is:
12
13    "This is a nasty question, since when I first set up the DOS machine
14     (long before I acquired RTEMS) I ftp'd a bunch of different tool
15     sets (all from SimTel), and then picked individual tools from each
16     set that worked best for me.  The djgpp tools are probably a good
17     starting point, especially to get a working sed.  Next the gnu tools
18     in SimTel/msdos/gnuish, and then others.  Sorry I can't give you more
19     specific names.  The only real requirement for the tools is that
20     they *must* accept redirection of command line arguments from a file
21     using the '@' notation (i.e., "mkdir @/tmp/args" reads the argument
22     list from file /tmp/args)."
23
24There is a special version (source and executable) of GNU make 3.71 for
25MS-DOS which minimizes the amount of memory used by recursive makes
26available on lancelot.gcs.redstone.army.mil in the directory: ... XXX
27
28go32
29----
30go32 dumps the stack when a program seg-faults, and if this happens while
31on an alternate stack an infinite loop can ensue.  Setting the environment
32variable GO32="core /tmp/core" will prevent more than 20 lines or
33so of stack information from being dumped after a crash, and the output
34will go to a file rather than the screen.
35
36The go32 debuggers get confused by the relocated stacks used by tasks,
37and tend to crash when variables are inspected.
38
39djgcc include files
40-------------------
41In general, we use RTEMS include files because these contain the proper
42declarations for the libc, and in particular, the stdio functions.
43When calling go32-specific functions it is necessary to include some
44djgpp include files, as well.  Unfortunately, there are some disagreements
45between RTEMS and djgpp as to how certain functions and types are
46declared.  In these cases, the RTEMS source have been modified to
47special-case the differences.
48
49other
50-----
51* Pressing F12 will immediately abort the program.
52See lib/libbsp/i386/go32/console/inch.c.
53
54* lib/libbsp/i386/go32/timer uses the on-board timer chip by default,
55which has a resolution of about 1 microsecond.  However, if executing
56on a Pentium processor you can use the on-chip 64-bit cycle counter,
57which counts at whatever clock rate your processor runs at.  To enable
58this, set RTEMS_CPU_MODEL=pentium in make/custom/go32.cfg.
59
Note: See TracBrowser for help on using the repository browser.