**** BEGIN LOGGING AT Fri Jul 01 02:59:58 2016 Jul 01 08:23:50 which poky package do I have to use to add gdbserver to my yocto image? Jul 01 08:29:15 CoLa|work: gdbserver Jul 01 08:30:57 hmm tried, but I get an error that nothing rprovides gdbserver Jul 01 08:48:58 CoLa|work: in poky, it's the gdb recipe that provides it Jul 01 08:49:39 the gdb recipe provides the gdb and the gdbserver packages; you can install only gdbserver to your target Jul 01 08:50:16 http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/gdb/gdb.inc#n9 Jul 01 08:51:08 thanks found it, seems the meta/recipes-support layer is not correctly included and hence the recipe was not found Jul 01 08:51:32 recipes-support isn't a layer, it's just a directory Jul 01 08:51:43 meta is a layer (it's otherwise known as OE-Core) Jul 01 08:52:11 hmm, then it's weird, I see poky/meta in "bitbake-layers show-layers" Jul 01 08:54:18 then it should be finding the gdb recipe. do "bitbake gdb" to verify it builds OK. put something like IMAGE_INSTALL_append = " gdbserver" to add it to your image Jul 01 08:54:40 or maybe I'm missing something Jul 01 08:55:46 I am getting this two line errors, not sure what the trigger error is: ERROR: Nothing PROVIDES 'gdb' \n ERROR: gdb was skipped: incompatible with license GPLv2 & GPLv3 & LGPLv2 & LGPLv3 Jul 01 09:00:05 sounds very fishy. but maybe, look at the features section in local.conf? i meant, there should be something like debug-tools or such that is meant to trigger gdb Jul 01 09:01:52 that would be tools-debug in EXTRA_IMAGE_FEATURES, it will also trigger gdb but I don't see how it affects the license stuff Jul 01 09:04:41 ack Jul 01 09:04:56 well mabye something else breaks stuff. additional layers, appends, etc. Jul 01 09:05:09 sounds like you've set incompatible license and so the gdb recipe isn't being included Jul 01 09:06:02 possibly, will check if GPLv3 licenses (this one?) are excluded somwhere Jul 01 09:06:49 INCOMPATIBLE_LICENSE is the variable Jul 01 09:46:03 indeed, INCOMPATIBLE_LICENSE was set and caused the problem, thanks Jul 01 10:02:25 CoLa|work: thanks for letting us know Jul 01 12:33:46 hy Jul 01 12:34:14 yocto is failing to build the toolchain for arm on fedora 24. what should I do? Jul 01 12:34:50 what is the error ? Jul 01 12:35:13 cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)' redeclared inline with 'gnu_inline' attribute Jul 01 12:36:12 full log: http://pastebin.com/sEsw3La9 Jul 01 12:38:35 cdleonard1: gcc6 apparently doesn't build some gcc5 versions: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69959 Jul 01 12:38:36 Bug 69959: was not found. Jul 01 12:39:26 yocti: thanks, but I don't mean your bug tracker Jul 01 12:39:27 fredcadete: Error: "thanks," is not a valid command. Jul 01 12:40:02 rude bot Jul 01 12:44:59 it looks like the yocto gcc recipe could be patched for this? Jul 01 13:23:03 who did break rpi build? Jul 01 13:23:58 7925e8942f654a3d084aa25eee439497619f9f01 Jul 01 13:40:45 http://paste.ubuntu.com/18234863/ Jul 01 13:40:49 this is the failure Jul 01 13:51:11 ok, I git bisected it Jul 01 13:51:15 31351ce146bf9c61d779456cd68ff7c2c9d4c8a8 Jul 01 13:51:25 this is the problematic commit Jul 01 13:52:04 "ARMPKGSFX_FPU = "${@ ('-%s' % d.getVar('TUNE_CCARGS_MFPU', True).split()[-1].replace('-', '')) if (d.getVar('TUNE_CCARGS_MFPU', True) != '') else ''}"" Jul 01 13:52:13 this is obviously breaking stuff Jul 01 13:52:30 cortexa7thf-neon-vfpv4 Jul 01 13:52:33 becomes cortexa7thf-neonvfpv4 Jul 01 13:52:35 otavio, ^^^ Jul 01 13:52:43 how can I get a revert? Jul 01 13:53:56 LocutusOfBorg: ? Jul 01 13:59:08 otavio, http://paste.ubuntu.com/18234863/ Jul 01 13:59:19 meta-raspberrypi is broken because of commit 31351ce146bf9c61d779456cd68ff7c2c9d4c8a8 Jul 01 13:59:32 there is a replace, removing the "-" from the variable Jul 01 13:59:38 so, the sanity check fails Jul 01 13:59:51 I did a git pull and my rpi2 project didn't build anymore Jul 01 14:00:27 LocutusOfBorg: ok but maybe rpi2 bsp is broken and needs fix Jul 01 14:01:13 how can it be broken? Jul 01 14:03:32 https://github.com/agherzan/meta-raspberrypi/blob/master/conf/machine/raspberrypi2.conf Jul 01 14:05:39 https://github.com/agherzan/meta-raspberrypi/issues/21 Jul 01 14:05:44 reported upstream lets see Jul 01 15:45:24 Hi all. Is there any reason the environment-setup file of a SDK is generated in such way, that flags are directly appended to e.g. CXX instead of having just the compiler in CXX and the flags in CXX_FLAGS? Jul 01 15:45:42 Or is this due to wrong usage of yocto? Jul 01 15:46:12 because i do have CFLAGS, CXXFLAGS, etc. in that setup file aswell Jul 01 17:02:09 the flags appended to CC and CXX are required flags without them cross compiler would not function Jul 01 17:02:26 its not wrong usage Jul 01 17:32:56 ... sadly, Anticom left before that answer showed up. IRC is very difficult for people. Jul 01 17:56:33 Good things come to those who wait :) **** ENDING LOGGING AT Sat Jul 02 02:59:57 2016