12 | | 1. Secondary architecture libraries and add-ons must live in respective <secondary_arch> subdirectory, where the runtime loader will only look when loading a secondary architecture executable. |
13 | | 2. Secondary architecture development libraries and headers must live in <secondary_arch> subdirectory, where only the secondary architecture compiler will look for them. |
14 | | 3. Secondary architecture executables must live in a <secondary_arch> subdirectory, which by default isn't in PATH. The executables can be symlinked to the primary architecture bin/ directory, using a symlink name that doesn't clash with the primary architecture executable's name (e.g. by appending to the name the secondary architecture name ("grep-x86") or the version, if that version isn't available on the primary architecture ("gcc-4")). |
15 | | 4. Application directories should live in a <secondary_arch> subdirectory, unless the application can't be built for the primary architecture. |
| 12 | 1. Secondary architecture libraries and add-ons must live in respective "<secondary_arch>" subdirectory, where the runtime loader will only look when loading a secondary architecture executable. |
| 13 | 2. Secondary architecture development libraries and headers must live in "<secondary_arch>" subdirectory, where only the secondary architecture compiler will look for them. |
| 14 | 3. Secondary architecture executables must live in a "<secondary_arch>" subdirectory, which by default isn't in PATH. The executables can be symlinked to the primary architecture "bin" directory, using a symlink name that doesn't clash with the primary architecture executable's name (by appending to the name the secondary architecture name, e.g. "grep-x86"). If there isn't a corresponding package for the primary architecture, the executables may also live directly in the "bin" directory. |
| 15 | 4. Application directories should live in a "<secondary_arch>" subdirectory, unless there isn't a corresponding package for the primary architecture. |