Bug #803
closed
Extraneous /home/<user>/.../sysroot/... directory is being populated on install
100%
Description
This shows up in the buildroot/output/target tree. I'm not sure where its coming from but the contents are
mjhammel/
mjhammel/src
mjhammel/src/ximba
mjhammel/src/ximba/raspberrypi4
mjhammel/src/ximba/raspberrypi4/bld
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libatomic.so.1.2.0
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/librt-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libnsl-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libstdc++.so.6.0.24
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libnss_dns-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libresolv-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libpthread-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libnss_files-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libdl-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libutil-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libcrypt-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libc-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libanl-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/libm-2.29.so
mjhammel/src/ximba/raspberrypi4/bld/buildroot-2020.02.4.bld/staging/arm-buildroot-linux-gnueabihf/sysroot/lib/ld-2.29.so
Files
Updated by Hammel almost 4 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
Rebuilding dev platform in rpi3 to test if this is an artifact of my testing or of the actual build.
Updated by Hammel almost 4 years ago
New build issues with firmware:
### 2021-02-02 07:53:00 PM Copying rt3090.bin from Linux firmware repo cp: cannot stat '/home/mjhammel/src/ximba/raspberrypi3/src/../archive/kernel/linux-firmware/rt3090.bin': No such file or directory ### 2021-02-02 07:53:00 PM Copying rt2870.bin from Linux firmware repo ### 2021-02-02 07:53:00 PM Copying rt3070.bin from Linux firmware repo cp: cannot stat '/home/mjhammel/src/ximba/raspberrypi3/src/../archive/kernel/linux-firmware/rt3070.bin': No such file or directory ### 2021-02-02 07:53:00 PM Copying rt3071.bin from Linux firmware repo ### 2021-02-02 07:53:00 PM Copying rtlwifi/rtl8192cufw.bin from Linux firmware repo ### 2021-02-02 07:53:00 PM Copying brcm/brcmfmac43430-sdio.bin from Linux firmware repo cp: cannot stat '/home/mjhammel/src/ximba/raspberrypi3/src/../archive/kernel/linux-firmware/brcm/brcmfmac43430-sdio.bin': No such file or directory
Updated by Hammel almost 4 years ago
- % Done changed from 10 to 20
Build problems with firmware were fixed. The brcm drivers are now retrieved from the same upstream location - previously I got one from that location and one from RPi kernel firmware. The rt drivers have been rolled into a single rt2800 driver so the others are no longer needed.
libjpeg's upstream may be compromised (SHAs don't match anymore) so I copied the last known supported release to the muse archive.
The build completes now. The rootfs definitely contains the sysroot tree under /home/mjhammel. The customize tree does not include this. So it's coming from somewhere else.
Updated by Hammel almost 4 years ago
There was no easy way to force a reproduce of this problem after a build had already been done. Also, it's not clear from inspection of the .mk files or the buildroot postbuild.sh why this is happening.
So I wrote a shell script to build each component (and package it) one at a time, testing for the existence of those directories under the buildroot target tree (which is where the come from in the squashfs). This should narrow down where I need to search.
The test is running now.
Updated by Hammel almost 4 years ago
- % Done changed from 20 to 50
I wrote a shell script for testing where this might happen. The best I can find is that it happens somewhere in the Buildroot build. I used the same script to split that build into pieces but it didn't find where it happened.
I can't find where this is happening (other than somewhere in the Buildroot build), but to get around it I added cleanup code to the postbuild.sh script for buildroot.
Testing now.
Updated by Hammel almost 4 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
That works. Change to postbuild.sh tested, committed and pushed.
Closing issue.