svn commit: branches/uClibc-nptl/docs
carmelo at uclibc.org
carmelo at uclibc.org
Sun Mar 16 07:34:25 UTC 2008
Author: carmelo
Date: 2008-03-16 00:34:24 -0700 (Sun, 16 Mar 2008)
New Revision: 21331
Log:
Merge nptl branch tree with trunk.
Step 3: remove uclibc.org folder and merges docs
Signed-off-by: Carmelo Amoroso <carmelo.amoroso at st.com>
Removed:
branches/uClibc-nptl/docs/uclibc.org/
Modified:
branches/uClibc-nptl/docs/PORTING
Changeset:
Modified: branches/uClibc-nptl/docs/PORTING
===================================================================
--- branches/uClibc-nptl/docs/PORTING 2008-03-15 05:07:26 UTC (rev 21330)
+++ branches/uClibc-nptl/docs/PORTING 2008-03-16 07:34:24 UTC (rev 21331)
@@ -65,6 +65,11 @@
====================
=== ldso sysdeps ===
====================
+- elf.h - presumably you've already taught binutils all about the random ELF
+ relocations your arch needs, so now you need to make sure the defines exist
+ for uClibc. make sure the EM_### define exists and all of the R_###_###
+ reloc defines.
+
- enable ldso/shared options in your extra/Configs/Config.ARCH file
- you will need to create the following files in ldso/ldso/ARCH/
dl-debug.h dl-startup.h dl-syscalls.h dl-sysdep.h elfinterp.c resolve.S
@@ -115,3 +120,19 @@
- clean up after call
- jump to function address now stored in PLT
glibc stores this function in libc/sysdeps/ARCH/dl-trampoline.S
+
+- utils/ldd.c - if you want support for ldso cache files (spoiler: you do),
+ then you'll need to teach ldd a little. generally, the fallback code
+ should be smart and "just work", but you should be explicit. just pop
+ it open and add an appropriate ifdef for your arch and set MATCH_MACHINE()
+ and ELFCLASSM. there are plenty examples and you're (hopefully) smart.
+
+====================
+=== Misc Cruft ===
+====================
+- utils/readelf.c - not really needed generally speaking, but might as well
+ add your arch to the giant EM_* list (describe_elf_hdr)
+
+- MAINTAINERS - presumably you're going to submit this code back to mainline
+ and since you're the only one who cares about this arch (right now), you
+ should add yourself to the toplevel MAINTAINERS file. do it.
More information about the uClibc-cvs
mailing list