diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2022-09-30 16:22:20 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@xry111.site> | 2022-09-30 16:24:55 +0800 |
| commit | 77b46db0a84285c86a4963c6fea9f3ec1b45d8f4 (patch) | |
| tree | 7dc50bcc0153369ab90f460858264e6ebe97089f | |
| parent | e18ba697ebe7861e70b00dfb1480273f7ea9b40c (diff) | |
toolchaintechnotes: highlight why the example (ubuntu vs android) needs "os" field
| -rw-r--r-- | part3intro/toolchaintechnotes.xml | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml index 7a8058424..a6206bb91 100644 --- a/part3intro/toolchaintechnotes.xml +++ b/part3intro/toolchaintechnotes.xml @@ -158,8 +158,10 @@ two systems can share the same kernel but still be too different to use a same triplet for them. For example, an Android running on a mobile phone is completely different from Ubuntu running on an ARM64 - server. Without an emulation layer, you cannot run an executable for - the server on the mobile phone or vice versa. So the + server, despite they are running on the same type of CPU (ARM64) and + using the same kernel (Linux). + Without an emulation layer, you cannot run an + executable for the server on the mobile phone or vice versa. So the <quote>system</quote> field is separated into kernel and os fields to designate these systems unambiguously. For our example, the Android system is designated <literal>aarch64-unknown-linux-android</literal>, |