Skip to content
Snippets Groups Projects
Commit c62d1b72 authored by Jason Hiser's avatar Jason Hiser :tractor:
Browse files

Typo fixes and clarifications

parent cd859152
No related branches found
No related tags found
No related merge requests found
Pipeline #26358 passed
...@@ -92,7 +92,7 @@ $ scons ...@@ -92,7 +92,7 @@ $ scons
The `$PSZ` script uses IDA Pro by default if it is setup properly. You'll see the `meds-static` step replace the `rida` step. The `$PSZ` script uses IDA Pro by default if it is setup properly. You'll see the `meds-static` step replace the `rida` step.
If this step fails, make sure that IDA Pro is installed properly, and that you have started IDA Pro's GUI to accept the license agreement. If this step fails, make sure that IDA Pro is installed properly, and that you have started IDA Pro's GUI to accept the license agreement.
The cookbook and other tools may use `pszr` to invoke zipr. This command means "invoke Zipr with Rida" as the front end, or `$PSZ -c rida`. If you've using `pszr` and wish to change The cookbook and other tools may use `pszr` to invoke Zipr. This command means "invoke Zipr with Rida" as the front end, or `$PSZ -c rida`. If you've using `pszr` and wish to change
to IDA, just switch to `$PSZ`. to IDA, just switch to `$PSZ`.
...@@ -103,13 +103,13 @@ However, Zipr has at least some support for ARM32/64, MIPS32/64 and X86 32/64. ...@@ -103,13 +103,13 @@ However, Zipr has at least some support for ARM32/64, MIPS32/64 and X86 32/64.
Zipr _can_ run on ARM box, but has never been tested/built on a MIPS box. Zipr _can_ run on ARM box, but has never been tested/built on a MIPS box.
To make Zipr work on non-x86 binaries, you'll need to have completed these steps: To make Zipr run on an X86 machine with non-x86 binaries, you'll need to have completed these steps:
* Built Zipr with IDA Pro support (ensure IDAROOT and IDASDK are set when running zipr). * Build Zipr with IDA Pro support (ensure IDAROOT and IDASDK are set when running Zipr).
* Install core-utils and gcc for cross compilation. For arm32 and arm64, you can use `sudo apt install binutils-aarch64-linux-gnu gcc-aarch64-linux-gnu` * Install core-utils and gcc for cross compilation. For arm32 and arm64, you can use `sudo apt install binutils-aarch64-linux-gnu gcc-aarch64-linux-gnu`.
* Set the environment variables to specify that Zipr should use the cross-compilation tools. In particular, set `PS_OBJDUMP`, `PS_READELF`, `PS_GCC`, `PS_OBJCOPY`, `PS_NM`, `PS_STRIP`. * Set the environment variables to specify that Zipr should use the cross-compilation tools. In particular, set `PS_OBJDUMP`, `PS_READELF`, `PS_GCC`, `PS_OBJCOPY`, `PS_NM`, `PS_STRIP`.
For example, to use Zipr for the ARM architecture (32 or 64-bit) set `export PS_GCC=aarch64-linux-gnu-gcc` (and the other environment variables). For example, to use Zipr for the ARM architecture (32 or 64-bit), run `export PS_GCC=aarch64-linux-gnu-gcc` (and the other environment variables).
This can be simplified with the `set-cross.sh` script by invoking it like so: `source set-cross.sh arm32` (or, substitute arm64, mips32,or mips64.) This can be simplified with the `set-cross.sh` script by invoking it like so: `source set-cross.sh arm32` (or substitute, for e.g., arm64.)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment