You are not logged in.
I've been working out virtual-box arch-linux guest for the past few months and now I'm trying to make a live iso of my OS with a python application I wrote. I'm following the wiki closely for the archlive/releng profile:
I added these packages to the provided packages.x86_64:
vim-minimal --> vim
python
python-gobject
gtk3
python-pip
xorg
xfce4
lightdm (no greeter necessary with autologin)
none of the above packages requires llvm-libs, however I do run my virtual box with mesa which depends on llvm-libs.
./builds.sh doesn't get past installing packages:
(175/341) installing llvm-libs [###########################] 100%
error: could not extract /root/archlive/releng/work/x86_64/airootfs/usr/lib/libLLVM-8.so (Write failed)
error: could not extract /root/archlive/releng/work/x86_64/airootfs/usr/lib/libLTO.so.8 (Write failed)
error: could not extract /root/archlive/releng/work/x86_64/airootfs/usr/share/licenses/llvm-libs/ (Can't create '/root/archlive/releng/work/x86_64/airootfs/usr/share/licenses/llvm-libs')
warning: warning given when extracting /root/archlive/releng/work/x86_64/airootfs/usr/share/licenses/llvm-libs/LICENSE (Failed to create dir '/root/archlive/releng/work/x86_64/airootfs/usr/share/licenses/llvm-libs')
error: problem occurred while installing llvm-libs
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.
==> ERROR: Failed to install packages to new rootI have several questions:
Are llvm-libs and mesa part of pacstrap base? Pacman -Qi llvm-libs states llvm-libs is installed as a dependency
From the above output it appears as though llvm-libs is looking for libraries to configure/build itself? Any suggestions for finding out what is actually going on? Can pacman/pacstrap be redirected at this step to my system libraries in build.sh somehow?
Thanks for your time
Last edited by bellacoeur (2019-09-26 14:44:48)
Offline
Are llvm-libs and mesa part of pacstrap base?
nope, both are from extra repository and not needed for a basic console setup.
The "write failed" makes me wonder.
/root is located on the / partition, is there enough space available on it ?
post lsblk -f & df output if unsure.
Last edited by Lone_Wolf (2019-09-26 10:36:32)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
You are correct, Lone_Wolf, the root partition is full. I'm glad I asked the question because that wasn't even on my radar of possible reasons. Thank you. I will mark solved if I can get it to build on a larger file system ![]()
Offline