<vd>
Can you append a recipe task from a distro conf?
<vd>
like do_something:pn-some-recipe:append () { } in a distro conf?
vd has quit [Quit: Client closed]
vd has joined #yocto
prabhakarlad has quit [Quit: Client closed]
dev1990 has quit [Quit: Konversation terminated!]
<JPEW>
vd: no. No "code" is allowed in a conf file
vd has quit [Quit: Client closed]
vd has joined #yocto
xmn has quit [Quit: ZZZzzz…]
<sveinse>
Under honister custom conversion types can be specified with CONVERSION_CMD:something. However, CONVERSION_DEPENDS_something = is still required. It is not using the new semicolon syntax. Bug or as indended? Not throwing stones, but I'd argue inconsistent at least. :D
<paulg>
something in my basic command line only build triggered a "need" for rust-llvm-native..... which was unexpected. And has brought eeverything else in the build to a stand-still.
* paulg
scowls at vmeson
georgem has quit [Ping timeout: 256 seconds]
pgowda_ has joined #yocto
georgem has joined #yocto
<JosefHolzmayrThe>
yo dudX
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
troth has quit [Ping timeout: 256 seconds]
rhadye has quit [Ping timeout: 256 seconds]
paulbarker has quit [Ping timeout: 256 seconds]
jonmason has quit [Ping timeout: 256 seconds]
paulbarker has joined #yocto
rhadye has joined #yocto
jonmason has joined #yocto
paulg has quit [Ping timeout: 265 seconds]
paulg has joined #yocto
<RP>
rburton: that patch in bitbake master-next seems to cause breakage :/
Schlumpf has joined #yocto
troth has joined #yocto
leon-anavi has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 268 seconds]
camus1 is now known as camus
sstiller has joined #yocto
troth has quit [Ping timeout: 264 seconds]
adrian_ has joined #yocto
tgamblin_ has joined #yocto
rob_w has joined #yocto
tgamblin has quit [Ping timeout: 264 seconds]
troth has joined #yocto
<khem>
RP: I was looking into using devupstream class for glibc but it seems to be not easy due to all stashing going on for associated recipes like glibc-locale etc
<khem>
they dont have SRC_URI and thats the issue where it starts I fixed it in devupstream class but then SRCPV can not be calculated ☹️ since it needs a git repo I guess
<khem>
so I guess recipes without proper SRC_URI are not going to work as it is
justas1 has joined #yocto
<justas1>
hello, does anyone else have any problems with git fetcher with honister release?
<justas1>
the error is "do_fetch: Fetcher failure: Fetch command ... --progress failed with exit code 128, no output"
<justas1>
In the log file I see "Resolving sources.openembedded.org (sources.openembedded.org)... 198.145.29.27
<justas1>
Connecting to sources.openembedded.org (sources.openembedded.org)|198.145.29.27|:80... connected.
<justas1>
HTTP request sent, awaiting response... 404 Not Found
<justas1>
2021-11-17 07:38:43 ERROR 404: Not Found."
<justas1>
Also in the release migration guide I see "Certificates are now properly checked when bitbake fetches sources over HTTPS. If you receive errors as a result for your custom recipes, you will need to use a mirror or address the issue with the operators of the server in question." However, in my recipe the protocol is ssh...
rfuentess has joined #yocto
fleg has joined #yocto
adrian_ has quit [Ping timeout: 250 seconds]
adrian_ has joined #yocto
zpfvo has joined #yocto
tre has joined #yocto
justas1 has quit [Quit: Ping timeout (120 seconds)]
Justas has joined #yocto
Justas has quit [Write error: Broken pipe]
leon-anavi has quit [Remote host closed the connection]
rob_w has quit [Ping timeout: 265 seconds]
zpfvo has quit [Ping timeout: 250 seconds]
leon-anavi has joined #yocto
zpfvo has joined #yocto
troth has quit [Ping timeout: 250 seconds]
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
rob_w has joined #yocto
mckoan|away is now known as mckoan
troth has joined #yocto
zpfvo has quit [Ping timeout: 250 seconds]
zpfvo has joined #yocto
manuel1985 has joined #yocto
manuel1985 has quit [Client Quit]
prabhakarlad has joined #yocto
Guest7755 has joined #yocto
<Guest7755>
hi there
<Guest7755>
I have question about yocto but i'm not sure here is the right place..
<JosefHolzmayrThe>
Guest7755: just give it try. ;-)
<Guest7755>
Make shows warning below when I run the testsuite. How to set the datetime automatically without accessing network.
<Guest7755>
`make: Warning: File 'Makefile' has modification time 84879 s in the future`
<JosefHolzmayrThe>
how do you construct the testcase? what is the context of running it?
<mckoan>
Guest7755: why you consider this a Yocto question ?
<Guest7755>
testcase is in ptest image generated by `bitbake core-image-ptest-all`.
goliath has joined #yocto
<Guest7755>
mckoan, sorry, that's why I'm not sure, where should I go for asking beginner questions?
<JosefHolzmayrThe>
Guest7755: which release is this on? I'd guess this comes from the image itself being built with reproducibility enabled, hence the defined timestamps, and the testcase leaking in the current time.
<Guest7755>
honister
<mckoan>
Guest7755: no worries, describe the context in mode detail
<JosefHolzmayrThe>
Guest7755: i think thats a legit problem. actually, the perect way would be if you can provide a minimal reproducing example for testsuite and recipe
<JosefHolzmayrThe>
*perfect, even
pgowda_ has quit [Quit: Connection closed for inactivity]
<Guest7755>
context? You mean the machine i use?
zpfvo has quit [Ping timeout: 265 seconds]
<JosefHolzmayrThe>
Guest7755: assuming this comes from a recipe/package that you created/maintain
zpfvo has joined #yocto
Guest7766 has joined #yocto
<qschulz>
halstead: good morning (well, in a few hours :) ), some people told us earlier that sources.openembedded.org mirrors are down. I too cannot connect to it. Is this domain name under your responsibility or is there someone else we need to contact to make them aware of this issue?
<Guest7766>
JosefHolzmayrThe It's a qemu riscv64 machine built by meta-riscv
zpfvo has quit [Ping timeout: 268 seconds]
Guest7755 has quit [Ping timeout: 256 seconds]
<JosefHolzmayrThe>
Guest7766: no custom layer on top? just poky+meta-riscv, setting the machine and then building the image?
zpfvo has joined #yocto
<qschulz>
halstead: seems like wget can connect to :80 but the index.html file is sent after ~43s
<Guest7766>
yes
<halstead>
qschulz: that domain is pointed at a server I control. I probably will need to look into it tomorrow
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
florian has joined #yocto
<qschulz>
halstead: hopefully it's not gone by tomorrow :p g'night!
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
<JosefHolzmayrThe>
Guest7766: ok, ii'll try to reproduce it but it will take some time.
<qschulz>
JosefHolzmayrThe: aren't you the guy with an overkill ThreadRipper setup :p ?
jamestperk has quit [Read error: Connection reset by peer]
jamestperk has joined #yocto
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
mckoan has quit [Read error: Connection reset by peer]
<jaskij[m]>
Is there a way to generate multi-target SDKs?
alessioigor has joined #yocto
manuel1985 has joined #yocto
florian_kc has joined #yocto
alessioigor has quit [Client Quit]
zpfvo has quit [Ping timeout: 250 seconds]
pgowda_ has joined #yocto
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 250 seconds]
zpfvo has joined #yocto
hpsy has joined #yocto
<jsandman>
Hi, does anybody know whether there is a way I can keep two meta-<bsp> layers in my Yocto project? Could I have the same bblayers.conf for the entire project and select the meta-<bsp> depending on what MACHINE I select?
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
alvaropg[m] has joined #yocto
CosmicPenguin has quit [Ping timeout: 256 seconds]
awafaa has quit [Ping timeout: 256 seconds]
xtopher_ has quit [Ping timeout: 256 seconds]
Tartarus has quit [Ping timeout: 256 seconds]
moto-timo has quit [Ping timeout: 268 seconds]
smurray has quit [Ping timeout: 264 seconds]
CosmicPenguin has joined #yocto
awafaa has joined #yocto
Tartarus has joined #yocto
xtopher_ has joined #yocto
drewfustini has quit [Ping timeout: 268 seconds]
<JosefHolzmayrThe>
jsandman: you're close! a well-behaved meta-bsp should only affect the build if the MACHINE it targets is selected. this means that if the bsps are compliant, you can have an arbitrary number of those in your build/bblayers.conf
drewfustini has joined #yocto
moto-timo has joined #yocto
smurray has joined #yocto
mckoan has joined #yocto
rob_w has quit [Ping timeout: 260 seconds]
fancer has quit [Ping timeout: 256 seconds]
lucaceresoli has joined #yocto
jmiehe has joined #yocto
fancer has joined #yocto
rob_w has joined #yocto
<jsandman>
I think I have something wrong in my layer.conf for these bsps layers then. I'll review them given this should work having both layers in defined in teh bblayers.conf
creich_ has joined #yocto
creich has quit [Ping timeout: 250 seconds]
sakoman has quit [Quit: Leaving.]
vladest has quit [Quit: vladest]
vladest has joined #yocto
<JosefHolzmayrThe>
jsandman: maye look at meta-ti and meta-intel. they should adhere to best practises there.
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
creich_ is now known as creich
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
leon-anavi has quit [Quit: Leaving]
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
hpsy has quit [Ping timeout: 250 seconds]
hpsy has joined #yocto
michalkotyla has joined #yocto
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 265 seconds]
GNUmoon has quit [Ping timeout: 276 seconds]
zpfvo has joined #yocto
GNUmoon has joined #yocto
tgamblin_ has quit [Remote host closed the connection]
tgamblin_ has joined #yocto
<jaskij[m]>
what happens if I have multiple `git://` entries in `SRC_URI`?
<jaskij[m]>
outside of needing to specify multiple `SRCREV:name`, that is
<qschulz>
jaskij[m]: if you know about "name" already you probably have a more precise question in mind?
<jaskij[m]>
Name came from looking at BB docs. Mostly I'm interested in how the two will interact, will they be just mashed into one directory or be put in different subdirs based on `name`?
<qschulz>
jaskij[m]: I don't know and it seems to be missing info in the docs so whatever the answer is, wtch the docs :)
<qschulz>
we need to patch*
Guest81 has joined #yocto
<jaskij[m]>
I already have enough of a Yocto backlog for the next few weekends (that dep script, extra CMake toolchain files, CMake section in using SDK docs)
<michalkotyla>
qschulz: my recipe only fetch sources from git with patches
<qschulz>
I guess that you did a bbappend on linux-yocto and then replaced the whole SRC_URI, removing the git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.10;destsuffix=${KMETA} line from it
<qschulz>
it is not mandatory to inherit kernel-yocto nor require linux-yocto.inc FYI, you can have a kernel recipe only by inheriting the kernel bbclass
tangofoxtrot has quit [Remote host closed the connection]
<michalkotyla>
qschulz: oh, thanks - that may be that. I do not have that line in SRC_URI - i will try that
<jsandman>
Thanks JosefHolzmayrThe! I'll take a look at those metas for reference
Tyaku has joined #yocto
sakoman has joined #yocto
tangofoxtrot has joined #yocto
<jaskij[m]>
michalkotyla: if the SoC you're using has a vendor BSP layer (TI and NXP for sure, maybe others), do take a look at the kernel recipes in their layers.
<jaskij[m]>
I'm using NXP, so I'm not using linux-yocto, but rather linux-fslc-imx
<jaskij[m]>
(now that I check, linux-fslc-imx does inherit kernel-yocto)
JavierPeces[m] has joined #yocto
tgamblin_ has quit [Quit: Leaving]
tgamblin has joined #yocto
Guest7766 has quit [Ping timeout: 256 seconds]
Tyaku has quit [Ping timeout: 268 seconds]
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
<michalkotyla>
jaskij[m]: thaks, i will look at that, but now i need to fix this in existing envrioment
<jaskij[m]>
you are doing a clean build, right?
zyga-mbp has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Tyaku has joined #yocto
<michalkotyla>
no, i have a lot of custom layer which work on "thud" version
<qschulz>
rburton: I think it'd make sense to add this to SRC_URI "name" example in the variables glossary
zpfvo has joined #yocto
<qschulz>
I see there's a subdir option for the unpack "task" but also "destsuffix" for the git repo, does anyone know from memory if they are different in behavior or are duplicates?
<qschulz>
s/git repo/git fetcher/
<paulg>
Well, this is clearly unacceptable. You can't build frigging vim w/o the dependency chain spidering out to suck in all of rust?!? Which then builds for ARM on an x86-64 target build. Which then segfaults after an hour.
<rburton>
paulg: if you even look at gtk then you can't avoid it without effort
<rburton>
(icons are svg source, so librsvg used to render, which is rust)
<paulg>
there must be a version of librsvg that is pre-rust. Guess I'll just pin to that?
<rburton>
its about 3 years old now
dgriego has quit [Ping timeout: 260 seconds]
<qschulz>
paulg: you'll have to embrace rust at one point anyway, just bite the bullet now :p
ar__ has joined #yocto
<paulg>
yay borg. resistance is futile; you will be assimilated.
dgriego has joined #yocto
codavi has quit [Ping timeout: 250 seconds]
rsalveti has joined #yocto
ar__ is now known as akica
<JPEW>
rburton: Given you're employeer, I'm not sure you can complain about forks of llvm :)
<rburton>
ha burn!
<rburton>
i discovered a new fork of clang last month
<JPEW>
rburton: We use `armclang` for our bare-metal builds.... it's.... fun?
<rburton>
i'm still angry there's no arm64 binary of it
<JosefHolzmayrThe>
ärmcläng!
<JosefHolzmayrThe>
you have to use more döts!
<JosefHolzmayrThe>
JPEW: armcc is "fun". armclang actually gets stuff done.
leon-anavi has joined #yocto
<JPEW>
JosefHolzmayrThe: This is true... I still remember debugging a RVCT 3.1 (or 4.1... I forget), where the compiler decided that inline functions were not synchonization points, so it was perfectly happy to move the code that toggled a GPIO _outside_ the block that disabled interrupts to make it atomic.... that was _fun_
<JosefHolzmayrThe>
+1
sstiller has quit [Quit: Leaving]
<kanavin>
I don't want C in my builds if you ask me, 70s relic that needs to die.
<kanavin>
and c++ can jump off a cliff right now
<kanavin>
the automotive industry doesn't know yet how deeply it's screwed over having standardized on the latter
<neverpanic>
kanavin: WORD
<neverpanic>
oops, had capslock on. probably still appropriate, thuogh :D
kiran has joined #yocto
<kanavin>
carpet bombing the oe-core list since 2015
<jaskij[m]>
kanavin: I *like* C++, but it's too complicated a language for mostly anything.
<jaskij[m]>
as much as it pains, personally I'll probably move forward with Rust
<jaskij[m]>
Meanwhile, I'm looking at sdbus-c++ and welp... they build-time download google test, and Google removed the `master` branch from their repo.
<paulg>
would be nice if rust would actually build. And not build ARM stuff for an x86 target build... https://paste.debian.net/1219844/
<fray>
For the test harness, is there some sort of 'autologin' procedure (where the boot goes to a prompt), or does it has some login process it does before each test case?
<rburton>
paulg: the arm/x86 thing is odd as the AB tests that case
<jaskij[m]>
paulg: I'm not sure if this changed after pulling Rust into core, but at least the meta-rust README for Hardknott has the following note:
<jaskij[m]>
> TARGET_SYS must be different from BUILD_SYS. This is due to the way Rust configuration options are tracked for different targets. This is the reason we use the Yocto triples instead of the native Rust triples. See rust-lang/cargo#3349.
<rburton>
paulg: thats a segfault in the compiler, not sure that's actually a rust problem
<paulg>
jaskij[m], okay, well I *guess* that explains the ARM part. Still sure looks odd when one sees it.
Tyaku has joined #yocto
<jaskij[m]>
Although a fix to the linked issue has supposedly been merged in upstream, so maybe it works in current versions of cargo?
zpfvo has quit [Ping timeout: 265 seconds]
<paulg>
rburton, yeah - I'm moving to another machine just to rule out flakey hardware - but it consistently fails right at that point - not at random - which is what one would expect for sketchy RAM/machine.
<rburton>
the AB literally builds x86-for-x86 so i'm not convinced that SYS thing is a problem still
<rburton>
paulg: yeah, llvm builds are not exactly trivial
<paulg>
I haven't built this rootfs for probably 6mo or more, and never on this particular machine before, so anything is possible.
florian has quit [Quit: Ex-Chat]
<RP>
paulg: FWIW I think llvm builds one compiler for all targets which is why there is ARM stuff there
florian_kc has quit [Ping timeout: 264 seconds]
<paulg>
rust llvm sure is a good way to unconditionally blow out build times to "unacceptable" on previously marginally acceptable older machines....
davidinux has joined #yocto
tperrot has quit [Quit: leaving]
<RP>
paulg: it is pretty bad :(
tprrt has joined #yocto
zpfvo has quit [Ping timeout: 265 seconds]
tprrt is now known as tperrot
zpfvo has joined #yocto
<paulg>
RP, yeah - as someone who likes to tinker at the trailing edge and rescue e-waste for a couple more years of use, it makes me sad.
<RP>
paulg: well, I was dragged into accepting rust into core and am trying not to say anything that will upset people ;-)
<paulg>
Fortunately I don't have that problem - the latter 1/2 of your sentence. B-)
zpfvo has quit [Ping timeout: 250 seconds]
Tyaku has quit [Quit: Lost terminal]
zpfvo has joined #yocto
tre has quit [Remote host closed the connection]
<jaskij[m]>
OE-Core in bugzilla is meta-openembedded, right?
<rburton>
no, it's openembedded-core
<rburton>
meta-oe doesn't use bugzilla
<jaskij[m]>
also, why the heck would people download deps in CMake...
<rburton>
because people who use cmake are TWISTED
<jaskij[m]>
eh, I like CMake
<jaskij[m]>
but I also like C++
<rburton>
i'll repeat, TWISTED
* jaskij[m]
is currently working on fixing sdbus-c++
<jaskij[m]>
(I misfiled a bug)
* paulbarker
just tabbed over here whilst fighting cmake
<jaskij[m]>
I *think* I have a fix for that too. Seems like current master checks for googletest's presence before downloading from upstream
<jaskij[m]>
rburton: Modern CMake is actually decently sane. But a lot of documentation and tutorials out there still go back to bad old days of pre-3.0. and because CMake still mostly supports those bad old practices...
<paulbarker>
jaskij[m]: You're spot on with my experience. Outdated tutorials, bad answers on stackoverflow, etc that all seem to work at first but then tie you in knots
<paulbarker>
Then you find someone saying "oh, we all know those ways are wrong and stupid. Use these new ways...."
<jaskij[m]>
I'm actually ill, was supposed to come in today, quickly test some hardware and go home to run away from AC. This sdbus thing completely run Ned my day.
<jaskij[m]>
*ruined
<jaskij[m]>
paulbarker: most C++ IDEs pushing people into CMake doesn't help things
<paulbarker>
jaskij[m]: I'm working with code that already uses cmake so the choice has already been made
<paulbarker>
At least it's not maven
<jaskij[m]>
I meant that more as a general thing. Oh, you want a C++ IDE? Use CMake, otherwise your choices are Eclipse and MS Visual Studio
<kanavin>
phoronix should look at meta-java if they want 'rough'
Guest81 has quit [Quit: Client closed]
otavio has quit [Remote host closed the connection]
<jaskij[m]>
khem: I've got a patch for sdbus-c++ failing because of googletest download, but can't submit it right now as I'm at work. Will submit later.
<jaskij[m]>
*later today
lucaceresoli has quit [Remote host closed the connection]
zpfvo has quit [Quit: Leaving.]
chep has quit [Ping timeout: 268 seconds]
chep has joined #yocto
mckoan is now known as mckoan|away
pgowda_ has quit [Quit: Connection closed for inactivity]
justas1 has joined #yocto
<justas1>
Hello, how should I debug git fetcher issues? Particularly "do_fetch: Fetcher failure ... failed with exit code 128, no output"
florian_kc has joined #yocto
justas14 has joined #yocto
justas1 has quit [Quit: Client closed]
justas14 has quit [Client Quit]
The_Pacifist has joined #yocto
vd has joined #yocto
<paulg>
it should point you at the fetch log for more details - something like tmp/work/<procfam-distro>/<pkgname>/<version>/temp/log.do_fetch
<paulg>
if it is a git repo, you can try running the command manually ; if it is a tarball fetch, you can try running the "wget" comand in the fetch log manually.
<paulg>
if you are behind a company firewall - make sure you are able to run those protocols over their normally assigned ports.
<kanavin>
paulg, too late :)
<paulg>
ah - I've masked join/leave msgs. Clearly wasn't to keen for help if they fled in less than 20m.
<kanavin>
maybe they misunderstand how irc works
<kanavin>
it's not a forum posting :)
kanavin has quit [Quit: Leaving]
florian_kc has quit [Ping timeout: 250 seconds]
kanavin has joined #yocto
chep has quit [Ping timeout: 268 seconds]
chep has joined #yocto
hpsy has quit [Ping timeout: 250 seconds]
rfuentess has quit [Quit: CHELAS!!!!!!!!!!!!!!!!!!!!!!!!!]
florian_kc has joined #yocto
chep has quit [Ping timeout: 265 seconds]
chep has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<paulg>
so, the vim ---> gtk ---> rust thing: Looking at "vim --version" on ubuntu and fedora, it looks lika there is no gtk, and even all the x11 options are prefixed with a minus sign.
<paulg>
which begs the question - if desktop distros aren't turning that on, then why, with a predominately embedded audience, are we turning all that boat load of crazy on?
<paulg>
Figured I'd try and save everybody the pain before I take my marbles and hide in the corner with my own bbappend that stops the crazy.
vd has quit [Quit: Client closed]
<paulg>
of course if you build gtk for some other reason, you'll still get a bucket of rust flakes.
vd has joined #yocto
<neverpanic>
paulg: distros usually provide multiple versions of vim under different names, vim-tiny, vim-nox, vim-...
<neverpanic>
but I agree
otavio has joined #yocto
<paulg>
now that you mention it, I do recall the variants, but I don't think I have *ever* even once ran anything but whatever the alternatives symlink points at.... Then again I've also been accused of being a dinosaur.
florian_kc has quit [Ping timeout: 250 seconds]
<paulg>
pretty sure I've cursed a blue streak at busybox vi and similar at least 100 times though...
<jaskij[m]>
paulg: looking at Hardknott recipe, it enables the GTK version if x11 is in `DISTRO_FEATURES`
<paulg>
jaskij[m], right - but I guess I'm looking for a compelling reason as to *why* ; given the impact it triggers, and given that even desktop distros don't for their default vim binary.
eloi1 has joined #yocto
<jaskij[m]>
the assumption here probably was that if you're running X11, you'll be pulling in GTK regardless
<paulg>
perhaps, but if you are building a bank machine, or some kind of other appliance, it is a safe bet that vim isn't going to be a part of the UI you expose to the world.
<jaskij[m]>
fair enough
<jaskij[m]>
but if you're already using GTK, the build shouldn't change much if Vim also uses it
<jaskij[m]>
so rather, it's the false assumption that X11 -> having GTK
<jaskij[m]>
not sure if I expressed myself clearly
<paulg>
yeah - I think so -- I've not explored further as to whether this rootfs pkglist depends on gtk via some other path. Maybe I'll get to that this evening.
<smurray>
paulg: seems like commit 7b48bd2 in meta-oe added that to make Gvim work in sato, I could see dropping it if that's not an issue (or no one cares)
<paulg>
smurray, thanks for the pointer - I'll add it to my "to look at" list for later.
<paulg>
need to go vandalize some kernel related stuff now.
<smurray>
heh
chep has quit [Ping timeout: 256 seconds]
florian_kc has joined #yocto
chep has joined #yocto
prabhakarlad has joined #yocto
<kanavin>
paulg, so why not drop x11 from your DISTRO_FEATURES? do you need it for something?
<paulg>
kanavin, https://github.com/OverC/meta-overc -- has cube-builder, and cube-graphical-builder (think yocto build appliance kind of) - so there are both x11 and non-x11 variants.
bradfa has quit []
prabhakarlad has quit [Quit: Client closed]
amitk_ has joined #yocto
vd has quit [Quit: Client closed]
vd has joined #yocto
amitk has quit [Ping timeout: 264 seconds]
chep has quit [Ping timeout: 265 seconds]
zyga-mbp has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
chep has joined #yocto
zyga-mbp has joined #yocto
florian_kc has quit [Ping timeout: 250 seconds]
leon-anavi has quit [Quit: Leaving]
chep has quit [Ping timeout: 268 seconds]
rfried8 has joined #yocto
rfried has quit [Read error: Connection reset by peer]