rtems - RTEMS Kernel, file-systems, drivers, BSPs, samples, and testsuite.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fixes from Eric Norum. C++ support added in previous version was broken:	Joel Sherrill	1997-12-22	1	-24/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Update from Eric Norum to include C++ support.	Joel Sherrill	1997-12-20	1	-0/+14
\|
*	Added ka9q tcpip stack and network driver for the gen68360. This effort	Joel Sherrill	1997-04-09	1	-12/+51
\| \| \| \| \| \| \| \| \| \| \| \| \|	was done based on the 3.6.0 release and had to be autoconf'ed locally. It is turned on is the bsp enables it and it is not explicitly disabled via the configure option --disable-tcpip. As many warnings as possible were removed locally after the code was merged. Only the gen68360 and mvme136 bsps were compiled this way. The ka9q port and network driver were submitted by Eric Norum (eric@skatter.USask.Ca). The network demo programs are not included in the tree at this point.
*	Updates from Eric Norum.	Joel Sherrill	1996-05-01	1	-0/+111