forked from Imagelibrary/rtems
1) In my haste to add C++ constructor/destructors to the 68360 linkcmds scripts I managed to break all existing 68360 programs. Linker scripts which actually produce a working executable are contained below. The problem was that the constructor/destructors weren't included before the etext symbol. On top of that Eric and I appear to have problems with attachments: 2) In deciphering the above problem I think I stumbled across the reason you've had with patches mailed from me. I noticed that the linkcmds (and linkcmds.bootp) scripts in the latest distribution have a control-M (carriage return) at the end of each line. Could you check the files below before installing them in the distribution and see that there aren't returns in the files? Maybe if I send everything as a tar attatchment things will work better.
#
# $Id$
#
This is the top level of the RTEMS directory structure. The following
is a description of the files and directories in this directory:
Makefile.in
The top-level Make command file used to build the C implementation
of RTEMS. [RTEMS assumes the use of GNU make.]
README
This file.
REQUIRES
A list of the other tools which are assumed to be installed
before RTEMS is built.
SUPPORT
Information on third-party support for RTEMS.
build-tools
This directory contains the source for various utilities
needed to build RTEMS.
make
Make command files "included" from those in the source distribution.
[RTEMS assumes the use of GNU make.]
patches
This directory contains patches for this release of RTEMS.
src
This directory contains the source code for the C
implementation of RTEMS as well as the test suites, sample
applications, Board Support Packages, Device Drivers, and
support libraries.