From feaf38913aefbc81cfe991a622820931f186e02d Mon Sep 17 00:00:00 2001 From: simonmar Date: Fri, 19 Sep 2003 09:12:22 +0000 Subject: [PATCH] [project @ 2003-09-19 09:12:22 by simonmar] Be a bit more honest about how easy it is to port the linker. --- docs/building/building.sgml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/building/building.sgml b/docs/building/building.sgml index df51688..1fa1656 100644 --- a/docs/building/building.sgml +++ b/docs/building/building.sgml @@ -4093,10 +4093,13 @@ Hello World! To support GHCi, you need to port the dynamic linker (fptools/ghc/rts/Linker.c). The linker currently supports the ELF and PEi386 object file formats - if - your platform uses one of these then you probably don't have - to do anything except fiddle with the - #ifdefs at the top of - Linker.c to tell it about your OS. + your platform uses one of these then things will be + significantly easier. The majority of Unix platforms use the + ELF format these days. Even so, there are some + 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. If your system uses a different object file format, then you have to write a linker — good luck! -- 1.7.10.4