URL
https://opencores.org/ocsvn/or1k_old/or1k_old/trunk
Go to most recent revision |
Details |
Compare with Previous |
View Log
Line No. |
Rev |
Author |
Line |
1 |
158 |
chris |
#
|
2 |
208 |
chris |
# $Id: README,v 1.2 2001-09-27 12:02:52 chris Exp $
|
3 |
158 |
chris |
#
|
4 |
|
|
|
5 |
|
|
This directory contains the scripts used to build RPMS for GNAT/RTEMS.
|
6 |
|
|
|
7 |
|
|
The scripts are close but do not work completely right yet. I have
|
8 |
|
|
commented out the info related items in gnatnewlib.in to get the
|
9 |
|
|
RPMS to build.
|
10 |
|
|
|
11 |
|
|
The binutils directory should be ignored for now. In order to
|
12 |
|
|
build the toolset at all, I had to merge building binutils
|
13 |
|
|
into the build of gcc, gnat, and newlib. gdb is still built separately.
|
14 |
|
|
When gnat is based off a more recent gcc version, we can go
|
15 |
|
|
to the more proper method of building binutils first and
|
16 |
|
|
separately.
|
17 |
|
|
|
18 |
|
|
There is the more general issue that the gcc 2.8.1 RTEMS targets
|
19 |
|
|
were not always the same object format that the gcc 2.95.x ones
|
20 |
|
|
are. Thus some BSPs (m68k and i386 in particular) are now ELF
|
21 |
|
|
based and assume crti.o/crtn.o is installed. The gcc 2.8.1
|
22 |
|
|
configurations were not ELF and thus it is likely that programs
|
23 |
|
|
will not link on certain configurations.
|
24 |
|
|
|
25 |
|
|
Another more general issue is that GNAT gdb support is at
|
26 |
|
|
4.17 while remote debugging of RTEMS applications via
|
27 |
|
|
TCP/IP is in 4.18.
|
28 |
|
|
|
© copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.