**** BEGIN LOGGING AT Wed Mar 13 02:59:57 2019 Mar 13 03:03:46 Tartarus:dropping a fragment is not a bad idea Mar 13 03:03:59 something into /etc/sudoers.d/... Mar 13 09:32:02 hey! im on poky version jethro and trying to build on Ubuntu 18. I know it Mar 13 09:34:23 hey! im on poky version jethro and trying to build on Ubuntu 18. I know it's not a supported distro, but seems like automake-native fails when help2man tries to create a manpage. Its weird though, because both automake and help2man are from the OE tree, so there should be nothing from my host system in use. The error I get is https://pastebin.com/Qx8DLfuT .. any clues why this happens on ubuntu 18? Mar 13 09:35:31 i found this patch, http://lists.openembedded.org/pipermail/openembedded-core/2018-July/153346.html, which I don't think my tree has. But I tried running my build with -j1 and no parallell tasks. Still get the error... (after a clean sstate) Mar 13 09:44:25 BlastuR: Can you find the automake binary in the build directory there and try to run it with the '--help' argument manually? Mar 13 09:45:06 help2man is running via perl but automake is a native binary. You might be seeing native binaries built in OE failing to execute Mar 13 10:06:50 paulbarker: hmm, when i run bin/automake --help from within the devshell, it fails with this error: https://pastebin.com/6ebmv8qN Mar 13 10:07:05 .. and it looks like bin/automake is actually a Perl script, not a native binary Mar 13 10:11:01 if i could skip man page generation, that'd probably work too Mar 13 10:12:04 If the automake script won't run you'll just hit problems on the next recipe which tries to use it. Not sure what's wrong there though Mar 13 10:13:00 With a yocto project version as old as jethro you're probably better trying to build in an older version of Ubuntu Mar 13 10:43:46 paulbarker: right. i was afraid you'd say that :) Mar 13 10:44:36 BlastuR: its not as complicated as it sounds. just prepare a container for that use case. Mar 13 10:48:22 yeah, but then it'll be all messy with the ownership of files coming out of the container etc Mar 13 10:48:36 i know its totally doable, but i'd much rather get a native build going Mar 13 10:49:21 BlastuR: ownership only becomes complicated if its more than one user Mar 13 10:49:29 I did some work for a client getting daisy (don't ask) to build under Ubuntu 16.04 and that was painful enough. Moving to 18.04 was a dead end due to glibc changes. jethro isn't that old but still likely has issues Mar 13 10:51:17 Create a container using LXC so you have a full system you can install packages in. Create a user with the same name inside the container to run builds and you should be fine Mar 13 10:51:47 *LXD even. LXC is the older version. The command line tool is still `lxc` to keep things confusing though Mar 13 10:52:08 paulbarker: we use a similar setup in docker so it resets to clean slate on each build, but basically thats the trick, yes. Mar 13 10:52:43 docker makes me cry Mar 13 10:52:49 paulbarker: i know, i know Mar 13 10:53:04 don't take it personal :) Mar 13 10:53:39 Trying to debug weird container networking issues when your container image is missing 'ping' is fun Mar 13 10:54:01 paulbarker: one ping only, vasili. Mar 13 16:32:45 hi, so it's not possible to have tmpdir and deploy on different partition with thud ? Exception: subprocess.CalledProcessError: Command 'cp -afl --preserve=xattr ./* /deploy/ipk' returned non-zero exit status 1. Mar 13 16:33:10 cp: cannot create hard link Mar 13 16:44:56 should probably be fixed to fall back to copy if hard linking isn't viable **** ENDING LOGGING AT Thu Mar 14 02:59:57 2019