blob: 969adb88e593db18e1e454107b1bc737d404bb62 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, let's see. The user is reporting an FTBFS (Fails To Build From Source) issue with LibreOffice 3.5.7 on armhf in Launchpad's build environment. They suspect QEMU is involved.
The error code mentioned is 132, which they break down as 128 + 4. From what I remember, Unix-like systems use exit codes where 128 is the base for signals. Adding 4 would make it 132, which corresponds to signal 4. Signal 4 is SIGILL, which stands for illegal instruction. That suggests that the process received an illegal instruction error.
Looking at the context, they think it's related to QEMU. QEMU is an emulator, and when running binaries for a different architecture (like armhf), it emulates the CPU. An illegal instruction error here could mean that QEMU is encountering an instruction it can't emulate.
The categories given are instruction, syscall, or runtime. Since the error is about an illegal instruction (SIGILL), which is a specific type of faulty instruction, the category should be "instruction". The problem seems to stem from QEMU not handling a particular ARM instruction correctly during the build process. So the classification here is "instruction".
</think>
instruction
|