diff options
| author | A. Wilcox <AWilcox@Wilcox-Tech.com> | 2019-04-28 23:24:58 -0500 |
|---|---|---|
| committer | A. Wilcox <AWilcox@Wilcox-Tech.com> | 2019-04-28 23:24:58 -0500 |
| commit | a0f8a201077296b87ec76e2d1c6f9678dab78492 (patch) | |
| tree | ea09691bb612ddef756b66f3ae51a4d499bb050b | |
| parent | 50484015cfc355fba5acff5effb83a10820ec099 (diff) | |
| download | gcompat-a0f8a201077296b87ec76e2d1c6f9678dab78492.tar.gz gcompat-a0f8a201077296b87ec76e2d1c6f9678dab78492.tar.bz2 gcompat-a0f8a201077296b87ec76e2d1c6f9678dab78492.tar.xz gcompat-a0f8a201077296b87ec76e2d1c6f9678dab78492.zip | |
README: syntax fixes
| -rw-r--r-- | README.rst | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -173,24 +173,24 @@ Usage ===== Running binaries linked against glibc -------------------------------------- +````````````````````````````````````` If the values specified during build were correct, programs built for glibc should run normally on your musl host. If they are not working, check the program's ELF interpreter entry, using scanelf(8) like so: -`` -$ scanelf -i ~/glibcfile - TYPE INTERP FILE -ET_EXEC /lib64/ld-linux-x86-64.so.2 /home/kaniini/glibcfile -`` +:: + + $ scanelf -i ~/glibcfile + TYPE INTERP FILE + ET_EXEC /lib64/ld-linux-x86-64.so.2 /home/kaniini/glibcfile If the interpreter path is different than expected, use PatchELF or install a symlink from ``LOADER_PATH`` to the specified interpreter. Using glibc binaries via dlopen(3) from a musl program ------------------------------------------------------- +`````````````````````````````````````````````````````` There are two ways to accomplish this: @@ -201,7 +201,7 @@ There are two ways to accomplish this: * Alternatively, you can link the musl binary against libgcompat. Environment variables ---------------------- +````````````````````` * ``GLIBC_FAKE_VERSION`` |