public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'David Kauschke' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Using Isar SDK on Ubuntu 24.04 with GCC 12 Causes Segmentation Fault
Date: Tue, 18 Mar 2025 07:46:05 -0700 (PDT)	[thread overview]
Message-ID: <d9612d53-112b-4e21-b8b0-966e34c9de00n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2688 bytes --]

### Description

When using the Isar SDK on Ubuntu 24.04 with GCC 12 to cross-compile a 
simple application, the compiler crashes with a segmentation fault.
The same process works correctly with the SDK GCC 12 on Ubuntu 22.04.
The same process works correctly when using the Ubuntu 24.04 cross compiler 
installed by `sudo apt-get install gcc-12-aarch64-linux-gnu`

### Build Environment
- **Kernel:** Linux 6.8.0
- **Architecture:** x86_64
- **OS:** Ubuntu 24.04.2 LTS

### Isar Version
- **Commit:** 
[95ec8a229afd6a42ed9990f4700becf635fa2ae3](https://github.com/ilbers/isar/commit/95ec8a229afd6a42ed9990f4700becf635fa2ae3)

### Steps to Reproduce

#### 1. Build the SDK for ARM64
```sh
bitbake -c do_populate_sdk mc:rpi-arm64-v8-bookworm:isar-image-base -vDDD
```

#### 2. Setup the SDK
```sh
mkdir isar-image-base-sdk-raspios-bookworm-rpi-arm64-v8
sudo tar --strip-components=1 -xf 
isar-image-base-sdk-raspios-bookworm-rpi-arm64-v8.tar.xz 
isar-image-base-sdk-raspios-bookworm-rpi-arm64-v8
sudo isar-image-base-sdk-raspios-bookworm-rpi-arm64-v8/relocate-sdk.sh
```

#### 3. Cross-compile a Simple Hello World Application

```sh
echo 'int main() { printf("Hello\n"); }' | \
  
./isar-image-base-sdk-raspios-bookworm-rpi-arm64-v8/usr/bin/aarch64-linux-gnu-gcc-12 
-xc - -o helloworld
```

#### 4. Compiler Crash Output

```
aarch64-linux-gnu-gcc-12.bin: internal compiler error: Segmentation fault 
signal terminated program cc1
Please submit a full bug report, with preprocessed source (by using 
-freport-bug).
See <file:///usr/share/doc/gcc-12/README.Bugs> for instructions.
```

### Expected Behavior

The compiler should successfully build the `helloworld` executable without 
crashing.

### Observed Behavior

GCC 12 crashes with a segmentation fault during compilation.

### Additional Information

- This issue occurs on **Ubuntu 24.04**.
- The same process works fine on **Ubuntu 22.04**.

## Questions

Any insights or workarounds to resolve this issue would be greatly 
appreciated.

1)) Has anyone else encountered similar problems when using Isar SDK on 
Ubuntu 24.04?
2)) Has anyone an idea what the issue could be when using the GCC from the 
SDK instead from Ubuntu 24.04?
    - Maybe some distribution clashes between the Debian Isar SDK and the 
host Ubuntu machine?

Thank you in advance!

Best regards,
David

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/d9612d53-112b-4e21-b8b0-966e34c9de00n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3297 bytes --]

                 reply	other threads:[~2025-03-18 14:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9612d53-112b-4e21-b8b0-966e34c9de00n@googlegroups.com \
    --to=isar-users@googlegroups.com \
    --cc=d.kauschke154@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox