Commit feaf3891 authored by simonmar's avatar simonmar
Browse files

[project @ 2003-09-19 09:12:22 by simonmar]

Be a bit more honest about how easy it is to port the linker.
parent 04793e4a
...@@ -4093,10 +4093,13 @@ Hello World! ...@@ -4093,10 +4093,13 @@ Hello World!
<para>To support GHCi, you need to port the dynamic linker <para>To support GHCi, you need to port the dynamic linker
(<filename>fptools/ghc/rts/Linker.c</filename>). The linker (<filename>fptools/ghc/rts/Linker.c</filename>). The linker
currently supports the ELF and PEi386 object file formats - if currently supports the ELF and PEi386 object file formats - if
your platform uses one of these then you probably don't have your platform uses one of these then things will be
to do anything except fiddle with the significantly easier. The majority of Unix platforms use the
<literal>#ifdef</literal>s at the top of ELF format these days. Even so, there are some
<filename>Linker.c</filename> to tell it about your OS.</para> machine-specific parts of the ELF linker: for example, the
code for resolving particular relocation types is
machine-specific, so some porting of this code to your
architecture will probaly be necessary.</para>
<para>If your system uses a different object file format, then <para>If your system uses a different object file format, then
you have to write a linker &mdash; good luck!</para> you have to write a linker &mdash; good luck!</para>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment