**** BEGIN LOGGING AT Thu Sep 15 02:59:58 2016 Sep 15 07:33:01 good morning Sep 15 08:59:36 hi Sep 15 08:59:43 morning everyone Sep 15 09:03:01 i am building a distro with systemd, and /etc/init.d/networking (from init-ifupifdown) is not started... any idea ? i thought the systemd-sysv-generator would handle it but apparently it is blind to that init script... Sep 15 09:06:20 does it need networkd ? Sep 15 09:49:44 afournier: networking is disabled as special case because it shouldn't be needed, see systemd-compat-units.bb Sep 15 09:50:55 the service file should still be created I think Sep 15 09:55:02 ok Sep 15 09:55:24 i bbappend'ed systemd-compat-units.bb and it works now :( Sep 15 09:55:48 why it should not be needed ? Sep 15 10:14:35 afournier: truth be told I thought we had networkd on by default but apparently not. Still, I'd expect the correct "ip" calls to be able to do what "networking start/stop" does -- not completely sure about this though Sep 15 10:18:10 afournier: take a look in networking.service in ifupdown -- should that not do the same thing? Sep 15 10:24:26 oops sorry, we don't actually ship that file , my apologies Sep 15 10:27:24 oh Sep 15 10:27:40 it looks like i made you find a bug Sep 15 10:27:42 sorry for this :) Sep 15 10:28:11 i was too lazy to check if ifupdown was shipping a network.service... my bad Sep 15 14:52:26 I have a cmake module that tests building code without libatomic and if it fails, `list(APPEND CMAKE_REQUIRED_LIBRARIES "atomic")`; however, while the test sample works after this, the atomic lib is not being added to the link command for the actual build project. Any ideas? Sep 16 00:15:56 Hi all, I am trying to generate a gnuradio bitbake image following the steps on https://files.ettus.com/manual/page_usrp_e3x0.html#e3x0_sdk_usage. The "bitbake -c populate_sdk gnuradio-dev-image" step finishes with a number of warnings like the one below. Can someone please advise if this means that the packages were succesfully downloaded from a mirror (would there be an error otherwise)? Thanks! Sep 16 00:16:02 WARNING: Failed to fetch URL ftp://ftp.debian.org/debian/pool/main/d/dpkg/dpkg_1.17.21.tar.xz, attempting MIRRORS if available Sep 16 00:16:06 NOTE: Tasks Summary: Attempted 4555 tasks of which 698 didn't need to be rerun and all succeeded. Sep 16 00:58:47 mmichael: I expect that you did get a download. try: find downloads -name dpkg_1.17.21.tar.xz ? Sep 16 00:59:26 if you are not building the master branch, I'm pretty sure the download works, I vaguely recall a bug about downloads on master... Sep 16 02:10:00 mmichael: the warnings alone aren't anything to be concerned about - you'd see an error if the file wasn't able to be fetched from a mirror subsequently Sep 16 02:10:34 they're really a warning to the recipe authors suggesting that unless it's a transient error, the recipe may need to be updated to point to a working URL Sep 16 02:11:28 our mirrors protect us from upstreams moving/removing their downloads, which unfortunately happens all too frequently :/ Sep 16 02:52:24 bluelightning: what are few main differences between SDK and extended-SDK Sep 16 02:53:06 availability of devtool Sep 16 02:53:15 size (standard SDK is smaller) Sep 16 02:53:44 eSDK mostly constructed using sstate rather than packages Sep 16 02:54:18 Do we have a section in manual describing using it ? Sep 16 02:54:30 one that may be a bit more subtle: because we're using the build system within the eSDK there is a managed sysroot to share libs and other files Sep 16 02:55:03 we have an SDK manual as of krogoth: www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html Sep 16 02:55:42 sorry that should be http://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html Sep 16 02:55:47 (thank you firefox) Sep 16 02:55:52 ah Sep 16 02:56:45 perfect Sep 16 02:59:09 esdk can build and install sdk packages after the fact, right? rather than only at build time when building the sdk? **** ENDING LOGGING AT Fri Sep 16 02:59:59 2016