Use the actual executable names in documentation, based on a patch by

Pierre d'Herbemont.


git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@2411 c046a42c-6fe2-441c-8c8c-71466251a162
This commit is contained in:
ths 2007-02-10 22:14:55 +00:00
parent ea785922f4
commit dbcf5e82de
1 changed files with 7 additions and 6 deletions

View File

@ -1753,7 +1753,8 @@ qemu-i386 -L / /bin/ls
@code{-L /} tells that the x86 dynamic linker must be searched with a
@file{/} prefix.
@item Since QEMU is also a linux process, you can launch qemu with qemu (NOTE: you can only do that if you compiled QEMU from the sources):
@item Since QEMU is also a linux process, you can launch qemu with
qemu (NOTE: you can only do that if you compiled QEMU from the sources):
@example
qemu-i386 -L / qemu-i386 -L / /bin/ls
@ -1870,7 +1871,7 @@ target x86 on x86: Most apps (Cocoa and Carbon too) works. [1]
@item
target PowerPC on x86: Not working as the ppc commpage can't be mapped (yet!)
@item
target x86 on x86: Most apps (Cocoa and Carbon too) works. [1]
target PowerPC on PowerPC: Most apps (Cocoa and Carbon too) works. [1]
@item
target x86 on PowerPC: most utilities work. Cocoa and Carbon apps are not yet supported.
@end itemize
@ -1891,20 +1892,20 @@ CD or compile them by hand.
libraries:
@example
qemu-darwin-i386 /bin/ls
qemu-i386 /bin/ls
@end example
or to run the ppc version of the executable:
@example
qemu-darwin-ppc /bin/ls
qemu-ppc /bin/ls
@end example
@item On ppc, you'll have to tell qemu where your x86 libraries (and dynamic linker)
are installed:
@example
qemu-darwin-i386 -L /opt/x86_root/ /bin/ls
qemu-i386 -L /opt/x86_root/ /bin/ls
@end example
@code{-L /opt/x86_root/} tells that the dynamic linker (dyld) path is in
@ -1916,7 +1917,7 @@ qemu-darwin-i386 -L /opt/x86_root/ /bin/ls
@subsection Command line options
@example
usage: qemu-darwin-i386 [-h] [-d] [-L path] [-s size] program [arguments...]
usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]
@end example
@table @option