Installed Python from dietpi-software list. That went well. Tried to install Home Assistant again. Got errors and uploaded with Bug ID - - Reference code: 0abc8101-fd91-4964-b677-d496f44adb2c
But these seems to be post install issues. homeassistant user and virtual environment is already created here.
Do I have to manually create these before I use suggested command line option in earlier post?
Install uv first? create virtual env? Where do I edit install scripts?
I did use the home assistant option from dietpi software list and tried to install. Got issues, uploaded the error log and used the bug guid in my first post. I will try again, if you prefer to see most recent issues.
The error log is not visible for everyone and automatically deleted after a couple of days. Therefore it would be helpful sot share the whole install log with us
Try hassle free home assistant from here. It is using well tested official Docker instance. I am using it for about a year, no upgrade caused any problems.
Kernel version | Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
Architecture | arm64
Hardware model | RPi 3 Model B (aarch64) (ID=3)
Power supply | (EG: RAVPower 5V 1A)
SD card | (EG: SanDisk Ultra 16 GB)
Steps to reproduce:
…
…
Expected behaviour:
…
Actual behaviour:
…
Extra details:
…
Additional logs:
Downloading Python-3.12.3.tar.xz...
-> https://www.python.org/ftp/python/3.12.3/Python-3.12.3.tar.xz
Installing Python-3.12.3...
BUILD FAILED (Debian GNU/Linux 12 using python-build 20180424)
Inspect or clean up the working tree at /tmp/python-build.20241008212340.3100
Results logged to /tmp/python-build.20241008212340.3100.log
Last 10 log lines:
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for --enable-universalsdk... no
checking for --with-universal-archs... no
checking MACHDEP... "linux"
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/tmp/python-build.20241008212340.3100/Python-3.12.3':
configure: error: C compiler cannot create executables
See `config.log' for more details
pyenv: version `3.12.3' not installed
dash: 5: pip3: not found
dash: 7: exec: pip3: not found
Did you tried to check both log files as stated? Would be good to know why executables can’t be created. Maybe there are other log files within /tmp right after the issue happen to you?
Maybe your system is running out of memory or available file system space?
root@DietPi:~# cat /tmp/python-build.20241009200058.27975.log
/tmp/python-build.20241009200058.27975 ~
/tmp/python-build.20241009200058.27975/Python-3.12.3 /tmp/python-build.20241009200058.27975 ~
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking for Python interpreter freezing... ./_bootstrap_python
checking for python3.12... no
checking for python3.12... no
checking for python3.11... python3.11
checking Python for regen version... Python 3.11.2
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for --enable-universalsdk... no
checking for --with-universal-archs... no
checking MACHDEP... "linux"
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/tmp/python-build.20241009200058.27975/Python-3.12.3':
configure: error: C compiler cannot create executables
See `config.log' for more details
root@DietPi:~#
Attaching config.log file to post config.log (18.9 KB)
If it helps, I am attaching screenshot from tmp folder
Not sure what you mean by empty system. I have been using this image for sometime and very much invested in the current state (RTL433, Syncthing, VPN…) I do have HA running on different RPI but unfortunately not able to update it to most recent version. So I used this PI’s image (16gb) restored it to 32gb card, updated dietpi with most recent version and tried HA install. So it’s definitely not empty, has running few of my apps. Doing fresh install will not help me at this point. May be I will try docker route and see it that works or not.
root@DietPi:~# gcc --version
gcc (Debian 12.2.0-14) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Ah, it was cc1 which had the segmentation faul, not gcc. That one is not made to be called manually, but it can be. Does the following throw a segmentation fault as well, or does it just not give any output (expected)?
root@DietPi:~# /usr/lib/gcc/*/12/cc1 --version
cc1: internal compiler error: Segmentation fault
0x1745fa7 internal_error(char const*, ...)
???:0
0xb169cc make_pass_profile(gcc::context*)
???:0
0xaf755b gcc::pass_manager::pass_manager(gcc::context*)
???:0
Please submit a full bug report, with preprocessed source (by using -freport-bug).
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-12/README.Bugs> for instructions.
root@DietPi:~#
