https://forge.codesys.com/tol/wharfie/tickets/You searched for assigned_to:"ingo"enSun, 07 Apr 2019 18:56:32 -0000https://forge.codesys.com/tol/wharfie/tickets/15/gcc for cross compilation is included in toolchain, but g++ is missing. erichspitzwegSun, 07 Apr 2019 18:56:32 -0000https://forge.codesys.com/tol/wharfie/tickets/15/https://forge.codesys.com/tol/wharfie/tickets/13/CXX=$${COMPILE_PREFIX}cpp in wharfie.mk should be CXX=$${COMPILE_PREFIX}g++erichspitzwegWed, 03 Apr 2019 06:40:15 -0000https://forge.codesys.com/tol/wharfie/tickets/13/https://forge.codesys.com/tol/wharfie/tickets/11/*Originally created by:* labi Currently we are facing the problem with stretch, that debootstrap doesn't want to build. Most likely its because of this error: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838388AnonymousFri, 05 Apr 2019 11:39:39 -0000https://forge.codesys.com/tol/wharfie/tickets/11/https://forge.codesys.com/tol/wharfie/tickets/3/*Originally created by:* labi *Originally owned by:* labi Currently the SSH key is created during installation. So it is the same for all targets where the created root filesystem will be rolled out.AnonymousFri, 05 Apr 2019 11:40:41 -0000https://forge.codesys.com/tol/wharfie/tickets/3/https://forge.codesys.com/tol/wharfie/tickets/1/*Originally created by:* labi *Originally owned by:* labi Allow building as non-root user. Currently we need root, as we are using chroot. After switching to fakechroot, we have the problem of non-native target systems. Then we are using qemu through binfmt, which simply doesn't work in combination with chroot. The way how fakechroot works is preloading a wrapper library through LD_PRELOAD. So the following scenerio sounds valid: ~~~ fakechroot chroot rootfs/ /bin/bash ~~~ /bin/bash is a target binary, executed through binfmt. chroot itself is still a host binary. fakechroot will fixly preload it's wrapper. We would need a few things: * When building a base system with debootstrap, we always need to corresponding libfakechroot.so fo the target. * In my opinion this library can be stored globally in a similar manner as debian_version.mk * When issuing the chroot, we need to switch LD_PRELOAD to the new folder Note: We need to check if the permissions on the files will remain the same after we switched from the host to the target library. Because the command is in fact a bit more complex: ~~~ fakechroot bash -c "cd ...; tar -xf ...; chroot . ./.trg.sh; ..." ~~~ So we have the files created with the host version of libchfakeroot.so and then we execute the target binaries with the target version. Not sure if we can guarantee, that they are seeing the same file permissions, as I don't know where this information is stored.AnonymousFri, 09 Mar 2018 15:40:55 -0000https://forge.codesys.com/tol/wharfie/tickets/1/