From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Problem during building of samba on arm builder Date: Wed, 10 Jul 2024 19:19:13 +0100 Message-ID: <7930976B-09CA-4E63-A1FA-F23609051735@ipfire.org> In-Reply-To: <922920a8-a65c-4240-b151-794ad8842a39@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3348667101138279972==" List-Id: --===============3348667101138279972== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 10 Jul 2024, at 17:53, Adolf Belka wrote: >=20 > Hi Michael, >=20 > On 10/07/2024 16:24, Michael Tremer wrote: >> Hello, >>> On 10 Jul 2024, at 14:21, Adolf Belka wrote: >>>=20 >>> Hi Michael, >>>=20 >>> On 10/07/2024 15:05, Adolf Belka wrote: >>>> Hi Michael, >>>>=20 >>>> On 10/07/2024 14:59, Adolf Belka wrote: >>>>> Hi Michael, >>>>>=20 >>>>> On 10/07/2024 12:33, Adolf Belka wrote: >>>>>> Hi Michael, >>>>>>=20 >>>>>> On 10/07/2024 11:57, Michael Tremer wrote: >>>>>>> Hello again, >>>>>>>=20 >>>>>>> I managed to (finally) build the toolchain with the updated system. S= o hopefully there should not be any more outstanding problems that I know of = so far. >>>>>>=20 >>>>>> I just did a git pull on your repo to my clone. >>>>>>=20 >>>>>> Ran ./make.sh gettoolchain and it successfully downloaded the toolchai= n. >>>>>>=20 >>>>>> Ran ./make.sh downloadsrc and it successfully tested everything. >>>>>>=20 >>>>>> Ran ./make.sh clean and build and log directories were cleared out and= removed. As far as I can tell it was successful. >>>>>>=20 >>>>>> Currently running ./make.sh build. So up to this point everything goin= g well. Will let you know how it goes. >>>>>>=20 >>>>> It has got to building popt. In the normal build system this takes arou= nd 3 secs. Currently in the new build it is at nearly 2 hours. Even with an e= mpty cache, that seems a long build time for popt, unless I am being too opti= mistic. >>>>>=20 >>>>> I will let it keep going. >>>>>=20 >>>> I just had a look at the log file and it looks like it completed popt bu= t then is stuck on trying to leave the directory /usr/src/lfs. Here is the ou= tput from the log, nothing new is getting written to the log. >>>>=20 >>>> make[3]: Leaving directory '/usr/src/popt-1.19/po' >>>> Making install in tests >>>> make[3]: Entering directory '/usr/src/popt-1.19/tests' >>>> make[4]: Entering directory '/usr/src/popt-1.19/tests' >>>> make[4]: Nothing to be done for 'install-exec-am'. >>>> make[4]: Nothing to be done for 'install-data-am'. >>>> make[4]: Leaving directory '/usr/src/popt-1.19/tests' >>>> make[3]: Leaving directory '/usr/src/popt-1.19/tests' >>>> make[3]: Entering directory '/usr/src/popt-1.19' >>>> make[4]: Entering directory '/usr/src/popt-1.19' >>>> make[4]: Nothing to be done for 'install-exec-am'. >>>> /bin/mkdir -p '/usr/share/man/man3' >>>> /usr/bin/install -c -m 644 popt.3 '/usr/share/man/man3' >>>> /bin/mkdir -p '/usr/lib/pkgconfig' >>>> /usr/bin/install -c -m 644 popt.pc '/usr/lib/pkgconfig' >>>> make[4]: Leaving directory '/usr/src/popt-1.19' >>>> make[3]: Leaving directory '/usr/src/popt-1.19' >>>> make[2]: Leaving directory '/usr/src/popt-1.19' >>>> make[1]: Leaving directory '/usr/src/popt-1.19' >>>> Updating linker cache... >>>> Install done; saving file list to /usr/src/log/popt-1.19 ... >>>>=20 >>>> make: Leaving directory '/usr/src/lfs' >>>>=20 >>>>=20 >>> I stopped the build with Ctrl-C and then ran ./make.sh build again withou= t doing a clean. It got to popt and went straight to libedit, the next packag= e, and started to build it. >>>=20 >>> Something must have just put the build into a loop of some sort. It was n= ot writing anything to the log file. >> The log file says that popt was done. It might be that you interrupted the= build just after it has finished, but the root file was not created, yet. Th= at should however not directly be a problem=E2=80=A6 > 2 hours had already gone by when I checked the log for that message. I then= left the system running for a further 20 minutes with no new info in the log= file and that is when I interrupted the build. Oh, that. Yes, I think I have seen this too, but I am not sure why yet. It looks like the wait call misses that the process has already been gone her= e: https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dblob;f=3Dmake.sh;h= =3D69e1fd7e45b42657f8b4c9352089cc430740b6c4;hb=3Drefs/heads/unshare#l810 >=20 >> If this is however the only problem that you are seeing now than I would b= e happy :) >=20 > I have found another problem when it got to the flash-images section. >=20 > The flash-images log stops with the following:- >=20 > # Insert the UUID because grub-mkconfig often fails to > # detect that correctly > sed -i /tmp/harddisk/boot/grub/grub.cfg \ > -e "s/root=3D[A-Za-z0-9\/=3D-]*/root=3DUUID=3D$(blkid -o value -s UUID /dev= /mapper/loop0p3)/g" > # Install GRUB > grub-install --force --recheck --no-floppy --target=3Di386-pc \ > --root-directory=3D/tmp/harddisk /dev/loop0 > Installing for i386-pc platform. > Installation finished. No error reported. > # Install GRUB for EFI > grub-install --target=3Dx86_64-efi --removable --no-nvram \ > --boot-directory=3D/tmp/harddisk/boot --efi-directory=3D/tmp/harddisk/boot/= efi > Installing for x86_64-efi platform. > Installation finished. No error reported. > # restore orginal defaults > mv -f /tmp/harddisk/etc/default/grub.backup /tmp/harddisk/etc/default/grub > rm -f /tmp/harddisk/etc/grub.d/11_linux_scon > # Set ramdisk mode to automatic > echo RAMDISK_MODE=3D2 > /tmp/harddisk/etc/sysconfig/ramdisk > # Automatically resize the root partition to its maximum size at first boot > touch /tmp/harddisk/.partresize > # Unmount > umount /tmp/harddisk/proc > umount /tmp/harddisk/sys > umount /tmp/harddisk/dev > umount /tmp/harddisk/boot/efi > umount /tmp/harddisk/boot > umount /tmp/harddisk > # zerofree the ext2 images to get better compression > zerofree /dev/mapper/loop0p1 > fsck.ext2 -f -y /dev/mapper/loop0p1 > e2fsck 1.47.0 (5-Feb-2023) > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > /dev/mapper/loop0p1: 631/130048 files (22.2% non-contiguous), 124148/520192= blocks > fsck.ext2 -f -y /dev/mapper/loop0p1 > e2fsck 1.47.0 (5-Feb-2023) > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > /dev/mapper/loop0p1: 631/130048 files (22.2% non-contiguous), 124148/520192= blocks > zerofree /dev/mapper/loop0p3 > fsck.ext4 -f -y /dev/mapper/loop0p3 > e2fsck 1.47.0 (5-Feb-2023) > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > /dev/mapper/loop0p3: 25477/118080 files (0.1% non-contiguous), 418098/47166= 1 blocks > fsck.ext4 -f -y /dev/mapper/loop0p3 > e2fsck 1.47.0 (5-Feb-2023) > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > /dev/mapper/loop0p3: 25477/118080 files (0.1% non-contiguous), 418098/47166= 1 blocks > kpartx -d -v /dev/loop0 > del devmap : loop0p1 > del devmap : loop0p2 > del devmap : loop0p3 > losetup -d /dev/loop0 > # Add padding at the end of the image (to fix alignment issues if the image= is > # not copied to a block device) > dd if=3D/dev/zero bs=3D1M count=3D100 >> /tmp/image.img > 100+0 records in > 100+0 records out > 104857600 bytes (105 MB, 100 MiB) copied, 0.0387438 s, 2.7 GB/s > # Compress Image > xz -T0 -8 < /tmp/image.img > /usr/src/images/ipfire-2.29-core187-x86_64.img= .xz > xz: Reduced the number of threads from 16 to 11 to not exceed the memory us= age limit of 7860 MiB > rm -rf /tmp/image.img /tmp/harddisk /tmp/cdrom > # Create checksum file > cd /usr/src/images && b2sum "ipfire-2.29-core187-x86_64.img.xz" > "ipfire-2= .29-core187-x86_64.img.xz".b2" > /bin/sh: -c: line 1: unexpected EOF while looking for matching `"' > make: *** [flash-images:186: /usr/src/log/flash-image] Error 2 > make: Leaving directory '/usr/src/lfs' I fixed the extra quotes: https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dcommitdiff;h=3Dd24= f7382fbe384f81e387f85af06ea19cad908c9 > In the images directory there is the iso and img files but only a b2 file f= or the iso. >=20 > Prior to the above section of the log there are about 165 entries similar s= aying:- >=20 > ERROR: ld.so: object '/tools_x86_64/lib/libpakfire_preload.so' from LD_PREL= OAD cannot be preloaded (cannot open shared object file): ignored. This comes from the commands that we run in a second, inner chroot. I will ha= ve to check whether we still need all this stuff to fake the environment. QEM= U might do most of the job for us when we are emulating a different architect= ure, and otherwise we don=E2=80=99t need this any more I believe. > Not sure that it has anything to do with the flash-images fail I am having = as all those messages say the fail was ignored. >=20 > Looking in the flash-images lfs file there looks like >=20 > # Create checksum file > cd $(IMAGES_DIR) && b2sum "$(notdir $(IMAGE_FILE))" > "$(notdir "$(IMAGE_FI= LE)").b2" >=20 > has "$(IMAGE_FILE)" for the destination while the source only has $(IMAGE_F= ILE) >=20 > So I removed the "" from the destination end and ran the build again. >=20 > This time the b2 file was created but now the flash-images failed with >=20 > make: Nothing to be done for 'download'. > make: Leaving directory '/home/ahb/sandbox/ms/ipfire-2.x/lfs' > make: Entering directory '/usr/src/lfs' > rm -rf /install/packages/package /tmp/* > mkdir -p /install/packages/package > eval $(cat /usr/src/config/rootfiles/core/187/meta) > cat: /usr/src/config/rootfiles/core/187/meta: No such file or directory > #Generate ROOTFILES from filelists > BUILD_ARCH=3Dx86_64 BUILDTARGET=3Dx86_64-pc-linux-gnu KVER=3D6.6.32 \ > /usr/src/src/scripts/archive.files \ > /usr/src/config/rootfiles/core/187/filelists \ > /usr/src/config/rootfiles/core/187/files \ > /usr/src/config/rootfiles/core/187/files.x86_64 \ > > /tmp/ROOTFILES.tmp > #remove excluded files from ROOTFILES > grep -f /usr/src/config/rootfiles/core/187/exclude -v /tmp/ROOTFILES.tmp= > /tmp/ROOTFILES > make: *** [core-updates:60: core/187] Error 1 > make: Leaving directory '/usr/src/lfs' I didn=E2=80=99t look at the packaging before, but this has also been dealt w= ith. Please pull again and re-run the build. > The above might have some relation to not doing a clean before the build. S= o I will leave the change in the flash-images lfs file and do a clean and a f= resh new build A clean build should not be needed. -Michael >=20 > Regards, >=20 > Adolf. >=20 >> -Michael >>>=20 >>> Regards, >>>=20 >>> Adolf. >>>=20 >>>=20 >>>> Regards, >>>>=20 >>>> Adolf. >>>>=20 >>>>=20 >>>>>=20 >>>>> One thing I found. I am running the new build system while I have been = running some package updates with the old system with its mount points. The t= wo have each run without any impact on the other. >>>>>=20 >>>>> Regards, >>>>>=20 >>>>> Adolf. >>>>>=20 >>>>>> Regards, >>>>>> Adolf. >>>>>>=20 >>>>>>>=20 >>>>>>> Best, >>>>>>> -Michael >>>>>>>=20 >>>>>>>> On 9 Jul 2024, at 22:29, Michael Tremer wrote: >>>>>>>>=20 >>>>>>>> Hello Adolf, >>>>>>>>=20 >>>>>>>> Thank you for testing this. >>>>>>>>=20 >>>>>>>> There have indeed been plenty of problems there=E2=80=A6 I spent a l= ot of time on this today and hopefully fixed most of them. >>>>>>>>=20 >>>>>>>> I cannot build the toolchain on my machine and I am not sure why yet= , but a build with the packaged toolchain runs through. >>>>>>>>=20 >>>>>>>> I have also spent some time on getting rid of the strip stage becaus= e it annoyed me how long it takes and creating the disk images as well as pac= kages should be significantly faster now, too. I hope I didn=E2=80=99t introd= uce too many new bugs. >>>>>>>>=20 >>>>>>>> Please let me know if you have more success now. >>>>>>>>=20 >>>>>>>> Best, >>>>>>>> -Michael >>>>>>>>=20 >>>>>>>>> On 8 Jul 2024, at 20:34, Adolf Belka wro= te: >>>>>>>>>=20 >>>>>>>>> Hi Michael, >>>>>>>>>=20 >>>>>>>>> On 08/07/2024 21:15, Adolf Belka wrote: >>>>>>>>>> Hi Michael, >>>>>>>>>>=20 >>>>>>>>>> On 08/07/2024 18:11, Michael Tremer wrote: >>>>>>>>>>> Hello, >>>>>>>>>>>=20 >>>>>>>>>>> I have been spending a lot of time on this problem, because it ha= s been bothering me for a long time. I also saw an opportunity to make more c= hanges to the build system. >>>>>>>>>>>=20 >>>>>>>>>>> Currently this is all a little bit WIP, but I hope that we can me= rge this into next as soon as the current update has been moved to master. >>>>>>>>>>>=20 >>>>>>>>>>> I am referring to this branch which is currently based on next: h= ttps://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dshortlog;h=3Drefs/hea= ds/unshare >>>>>>>>>>>=20 >>>>>>>>>>> It makes use of the unshare command which creates new namespaces = in Linux. That way, we can isolate the build system better from the host syst= em and in case something goes wrong, there is less damage. We can also enforc= e some more rules=E2=80=A6 >>>>>>>>>>>=20 >>>>>>>>>>> So, what has changed? >>>>>>>>>>>=20 >>>>>>>>>>> * The make.sh script might re-execute itself into a new mount nam= espace when it is suitable. This happens for =E2=80=9Cmake.sh build=E2=80=9D = and =E2=80=9Cmake.sh shell=E2=80=9D, but it does not happen for =E2=80=9Cmake= .sh downloadsrc=E2=80=9D for example. >>>>>>>>>>>=20 >>>>>>>>>>> https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dblob;f= =3Dmake.sh;h=3Db952627782a0d5ef4ac75f17315b689fcb3b4fe0;hb=3Drefs/heads/unsha= re#l2129 >>>>>>>>>>> https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dblob;f= =3Dmake.sh;h=3Db952627782a0d5ef4ac75f17315b689fcb3b4fe0;hb=3Drefs/heads/unsha= re#l2251 >>>>>>>>>>>=20 >>>>>>>>>>> * The new mount namespace means that we will no longer see any bi= nd-mounts in the host system and we no longer need to umount anything ourselv= es which is where we occasionally wiped the entire hard drive of the host sys= tem. When the last process exits, the namespace is being cleaned up and every= thing is being umounted. >>>>>>>>>>>=20 >>>>>>>>>>> * The function that prepares the build environment has been almos= t entirely rewritten: >>>>>>>>>>>=20 >>>>>>>>>>> https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dblob;f= =3Dmake.sh;h=3Db952627782a0d5ef4ac75f17315b689fcb3b4fe0;hb=3Drefs/heads/unsha= re#l426 >>>>>>>>>>>=20 >>>>>>>>>>> It used to mount parts of the host system into the build environm= ent which are needed to run anything. Those were /dev, /proc, /sys, etc=E2=80= =A6 >>>>>>>>>>>=20 >>>>>>>>>>> Instead, it now creates a new /dev mount point and creates a mini= mal amount of device nodes and symlinks. That way, we detach from the host sy= stem and no longer allow the build system access to the host=E2=80=99s filesy= stem and block devices. We also bind-mount the sources in read-only mode now,= so that the build system cannot change anything in the source tree. On top o= f that, cache is read-only, too. ccache and the log directory are the only pl= aces that are writable. >>>>>>>>>>>=20 >>>>>>>>>>> We mount a separate /tmp directory. >>>>>>>>>>>=20 >>>>>>>>>>> * When we then build a package, we create more namespaces for eac= h package. These isolate each build process from each other. >>>>>>>>>>>=20 >>>>>>>>>>> Mostly, this is to detach from the host system. A new UTS namespa= ce allows to change the hostname in the build system without affecting the ho= st and so on. We do the same thing with a new time namespace. >>>>>>>>>>>=20 >>>>>>>>>>> We do however create a new PID namespace which means that the bui= ld system no longer will see any processes running on the host system. That r= equires to mount a new instance of /proc with each package. This also has the= effect that if the shell that we launched terminates (because the build is d= one) any background processes will be killed immediately. >>>>>>>>>>>=20 >>>>>>>>>>> Last, we clone the mount namespace that we have created before so= that no build command can modify what we set up earlier. >>>>>>>>>>>=20 >>>>>>>>>>> * Since everything is now so decoupled, we gain a couple of new (= maybe minor?) features: >>>>>>>>>>>=20 >>>>>>>>>>> It is now possible to run =E2=80=9Cmake.sh shell=E2=80=9D whil= e a build is running. That does not happen a lot, but we can do this now :) >>>>>>>>>>>=20 >>>>>>>>>>> If the build crashes or the host system is being shut down whi= le a build is running, there is nothing to clean up afterwards. >>>>>>>>>>>=20 >>>>>>>>>>> * I have garnished this all with a lot of code cleanup and I supp= ose I might have introduced some new bugs here or there :) >>>>>>>>>>>=20 >>>>>>>>>>> * This is probably mostly around a new implementation of the time= r that updates the build time. It has been annoying me a lot that it takes a = long time to walk through all packages that have been built before to finally= get to a package that we want to rebuild. Mostly this was all help up by a c= all of =E2=80=9Csleep 0.1=E2=80=9D >>>>>>>>>>>=20 >>>>>>>>>>> Since bash does not really do any concurrency, I had to be creati= ve and replaced the busy-loop with a background process that is launched when= ever it is needed and which will =E2=80=9Cping=E2=80=9D the main make.sh scri= pt once a second. That way, we can just run as usual, but regularly get inter= rupted to update the runtime. >>>>>>>>>>>=20 >>>>>>>>>>> https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dblob;f= =3Dmake.sh;h=3Db952627782a0d5ef4ac75f17315b689fcb3b4fe0;hb=3Drefs/heads/unsha= re#l361 >>>>>>>>>>> https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dblob;f= =3Dmake.sh;h=3Db952627782a0d5ef4ac75f17315b689fcb3b4fe0;hb=3Drefs/heads/unsha= re#l834 >>>>>>>>>>>=20 >>>>>>>>>>> We now only fork one extra sub shell and we have to handle the ti= mer events which is a lot cheaper as well as more straight-forward to code. >>>>>>>>>>>=20 >>>>>>>>>>> * As there is no difference between the different stages any more= (those stages that we inherited from LFS), I have merged them all into one. >>>>>>>>>>>=20 >>>>>>>>>>> * Last but not least, I have create the option to build for multi= ple architectures on the same system. Since we can now mount the entire sourc= e tree into (many independent) build environments, we might as well=E2=80=A6 = As discussed on the last call, this might not be the best option for ARM, but= RISV-C builds at a decent speed even when emulated. >>>>>>>>>>>=20 >>>>>>>>>>> The only thing that I needed to do for this is to suffix the buil= d and log directories which are now called build_${ARCH}, i.e. build_aarch64,= build_x86_64, and so on. The packages/ directory is not changed yet, but tha= t will have to happen as well. Most likely I want to merge this with the gene= rated images, but I am not sure what to call this, yet. Happy to hear suggest= ions. result_x86_64? Just images_x86_64? >>>>>>>>>>>=20 >>>>>>>>>>> --- >>>>>>>>>>>=20 >>>>>>>>>>> I have run a build and this seems to be working just fine on my D= ebian machine. I am writing to all of you to first of all let you know what I= am up to; and secondly to ask to give this a go on your systems. I think it = should run just fine, as all the tools that I require should be available eve= rywhere. However, there might be some older kernels that might not support al= l of this, yet or any other problems I cannot think of yet. Please give me so= me feedback and send me all the bugs :) >>>>>>>>>> I gave this a go but it didn't work. >>>>>>>>>>=20 >>>>>>>>>> Not sure if I should have run the ./make.sh clean command on the o= ld version before I pulled the unshare branch into my clone of your repo. >>>>>>>>>>=20 >>>>>>>>>> Should I have started with a complete new clone of your repo? I mi= ght try that anyway just to see. >>>>>>>>>>=20 >>>>>>>>> I created a completely new clone of you ipfire-2.x repor and then c= hecked out the unshare branch to a branch called unshare in my local repo clo= ne. >>>>>>>>>=20 >>>>>>>>> gettoolchain gave the same issue, except that this time the toolcha= in directory ended up completely empty. >>>>>>>>>=20 >>>>>>>>> downloadsrc had the same result. >>>>>>>>>=20 >>>>>>>>> clean had nothing to clean up as it was a fresh clone. >>>>>>>>>=20 >>>>>>>>> build then tried to build the toolchain and came up with this error= , different from before. >>>>>>>>>=20 >>>>>>>>> ./make.sh build >>>>>>>>> chroot: failed to run command =E2=80=98env=E2=80=99: No such file o= r directory >>>>>>>>> Full toolchain compilation >>>>>>>>> stage1 [ FAIL ] >>>>>>>>>=20 >>>>>>>>> Jul 8 19:26:39: Building stage1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D Installing stage1 ... >>>>>>>>> mkdir -pv /tools_x86_64/lib >>>>>>>>> mkdir: cannot create directory '/tools_x86_64': File exists >>>>>>>>> make: *** [stage1:50: /home/ahb/sandbox/ms/ipfire-2.x/log/stage= 1] Error 1 >>>>>>>>>=20 >>>>>>>>> ERROR: Building stage1 [ FAIL ] >>>>>>>>> Check /home/ahb/sandbox/ms/ipfire-2.x/log_x86_64/_build.toolcha= in.log for errors if applicable [ FAIL ] >>>>>>>>>=20 >>>>>>>>> so it wasn't as simple as doing a fresh git clone. >>>>>>>>>=20 >>>>>>>>> Regards, >>>>>>>>>=20 >>>>>>>>> Adolf. >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>> So I ran ./make.sh gettoolchain first, as I usually would. >>>>>>>>>>=20 >>>>>>>>>> ./make.sh gettoolchain >>>>>>>>>> b2sum: cache/toolchains/ipfire-2.29-toolchain-20240521-x86_64.tar.= zst: No such file or directory >>>>>>>>>> cache/toolchains/ipfire-2.29-toolchain-20240521-x86_64.tar.zst: FA= ILED open or read >>>>>>>>>> b2sum: WARNING: 1 listed file could not be read >>>>>>>>>>=20 >>>>>>>>>> ipfire-2.29-toolchain-20240210-x86_64.tar.zst is present together = with its b2 file. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Then ran ./make.sh downloadsrc >>>>>>>>>>=20 >>>>>>>>>> Previous version ends with >>>>>>>>>>=20 >>>>>>>>>> ***Verifying BLAKE2 checksum >>>>>>>>>> all files BLAKE2 checksum match [ DONE] >>>>>>>>>>=20 >>>>>>>>>> after zstd has been checked. >>>>>>>>>>=20 >>>>>>>>>> New version stops at zstd entry. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> ./make.sh clean gave the message Cleaning Build directory... but w= as completed very quickly. >>>>>>>>>> Log and Build directories have not been cleaned out. The img and i= so files are still present. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> ./make.sh build gave message >>>>>>>>>>=20 >>>>>>>>>> chroot: failed to run command =E2=80=98env=E2=80=99: No such file = or directory >>>>>>>>>>=20 >>>>>>>>>> and then did a full toolchain compilation which failed with gcc bu= t log is >9000 lines. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Regards, >>>>>>>>>> Adolf. >>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> Thank you for listening to this brain-dump. >>>>>>>>>>>=20 >>>>>>>>>>> All the best, >>>>>>>>>>> -Michael >>>>>>>>>>>=20 >>>>>>>>>>>> On 3 Jul 2024, at 10:58, Michael Tremer wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>> Hello Adolf, >>>>>>>>>>>>=20 >>>>>>>>>>>> This happens occasionally that the buildsystem umounts /dev and = then nothing will really work any more. >>>>>>>>>>>>=20 >>>>>>>>>>>> I rebooted the machine and it is back up again. >>>>>>>>>>>>=20 >>>>>>>>>>>> -Michael >>>>>>>>>>>>=20 >>>>>>>>>>>>> On 2 Jul 2024, at 15:42, Adolf Belka = wrote: >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Hi Michael and all, >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> I ran the arm builder with the 4.20.2 version of samba to test = it out. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> The build got to building gdb and then failed. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Interestingly, the nightly build of arm was successful with the= same version of gdb. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> The build log for gdb is attached. The actual error is at line = 618. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Another thing I found is that I just tried to go back into the = arm builder. I successfully got into people.ipfire.org but then trying to scp= into the arm builder failed with the following message. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> ------------------------------------------ >>>>>>>>>>>>>=20 >>>>>>>>>>>>> ssh bonnietwin(a)arm64-01.zrh.ipfire.org >>>>>>>>>>>>> PTY allocation request failed on channel 0 >>>>>>>>>>>>> Linux arm64-01.zrh.ipfire.org 6.1.0-21-cloud-arm64 #1 SMP Debia= n 6.1.90-1 (2024-05-03) aarch64 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> The programs included with the Debian GNU/Linux system are free= software; >>>>>>>>>>>>> the exact distribution terms for each program are described in = the >>>>>>>>>>>>> individual files in /usr/share/doc/*/copyright. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the exte= nt >>>>>>>>>>>>> permitted by applicable law. >>>>>>>>>>>>> /etc/profile.d/Z99-cloud-locale-test.sh: line 14: /dev/null: Pe= rmission denied >>>>>>>>>>>>>=20 >>>>>>>>>>>>> ------------------------------------------ >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Regards, >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Adolf. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> <_build.ipfire.gdb.log> --===============3348667101138279972==--