9 Commits

Author SHA1 Message Date
Chris Johns
6c4218becf Fix the trace help. 2013-03-01 11:51:37 +11:00
Chris Johns
544de91e99 Fix managing weak symbols.
Weak symbols where not being managed correctly. The symbols table
is now a class with externals and weaks as separate symtabs so
the externals can be searched first then the weaks and if not
found an unresolved error is raised. This was found creating
a libbsdport RAP file where the drivers in the all driver table
resolved to the weak symbols and so linking in nothing.

Fixing the weak symbols as found in the libbsdport library
triggered a new resolver bug. The object files now contain the
resolver state and this is used to determine if an object file
has been resolved or is currently being resolved avoiding
rescursive loops with dependent object files.

The resolver trace output is a little easier to read.
2012-12-29 10:20:22 +11:00
Chris Johns
b5a59dd96f Use cerr for errors and not cout. 2012-12-18 20:51:41 +11:00
Chris Johns
cad8b53e6e Updated to reflect the framework changes. 2012-11-26 11:09:06 +11:00
Chris Johns
7b2762fe14 Make the entry point an unresolved symbol. 2012-11-21 13:36:32 +11:00
Chris Johns
c46980ee88 Add entry point support. 2012-11-21 13:04:47 +11:00
Chris Johns
eb34811206 Output application format files.
Added support for an RTEMS RAP format application file. The format is:

 <header>
 <LZ77>
  <Application Script>
  <[1..n] ELF Object files>
 </LZ77>

Where the header is a text string of fields delimited by ',' and terminated
with a line feed (\n). It is variable length:

  RTEMS-APP,0000000,01.00.00,LZ77,00000000\n\0

  where:
   RTEMS-APP     : file tag for quick acceptance and rejection
   Length        : the length of the application in bytes including the
                 : header
   Version       : Version of the application format.
   Compress      : The compression format.
   Checksum      : CCITT CRC32 checksum.

Following the header is a nul ('\0') character then an LZ77 container
with the application loader script followed by the ELF object files.

Note, the script format will be documented else where.

Note, the final version may add a 32bit length field before each part
in the compressed container to delimit the size of the file to be
read. This is currently not in this version.
2012-11-21 11:07:12 +11:00
Chris Johns
9b66527beb Only look for standard library paths if standard libraries and enabled. 2012-11-19 13:13:52 +11:00
Chris Johns
977c3de534 Refactor the ELF support to allow ELF write suppport.
The refactoring allows better reuse of the ELF support and cleans up
some hacks from the generic file and archive handling improving the
separation of the file handling from the file format, ie ELF. The
handling of ELF object files and ELF object files inside archives
is cleaner.

The refactor cleaned up the symbol handling where the symbols now
reside in the ELF file object and references are take in symbol
pointer containers and symbol table containers.

The main purpose of the refactor is to allow support for creating
and writing ELF files.

Also added an rtems-syms command where special symbol support
can be added.
2012-11-17 17:34:33 +11:00