<Saur[m]>
DougC: insane.bbclass looks for the string "is unsafe for cross-compilation" in the config.log file. So if you want to know what's causing it, that's where you should start looking.
Wouter01001 has joined #yocto
sakoman has quit [Quit: Leaving.]
starblue has quit [Ping timeout: 256 seconds]
starblue has joined #yocto
deuteron has quit [Quit: leaving]
agupta1 has joined #yocto
agupta1 has quit [Ping timeout: 276 seconds]
amitk has joined #yocto
seninha has quit [Quit: Leaving]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
kroon has joined #yocto
Wouter01001 has quit [Remote host closed the connection]
Wouter01001 has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
AKN has joined #yocto
<AKN>
Hi everyone, Anyone worked on brcmfmac43430 chipset?
<AKN>
<AKN> 5.649444] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/brcmf_pwrseq[1]' - status (0)
<AKN>
<AKN> I tried most of the nvram files available on internet still getting the same error.
<AKN>
<AKN> Linux bbai 5.10.120-gd5f4ca50bb #1 SMP PREEMPT Mon Jun 29 03:06:40 UTC 2020 armv7l armv7l armv7l GNU/Linux
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
thomasd13 has joined #yocto
Wouter01001 has quit [Ping timeout: 246 seconds]
xenador77 has quit [Remote host closed the connection]
xmn has quit [Ping timeout: 264 seconds]
zkrx has quit [Ping timeout: 240 seconds]
frieder has joined #yocto
Wouter01001 has joined #yocto
tre has joined #yocto
zkrx has joined #yocto
rob_w has joined #yocto
Schlumpf has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
xperia64 has quit [Ping timeout: 240 seconds]
xperia64 has joined #yocto
Ch^W has quit [Ping timeout: 240 seconds]
mvlad has joined #yocto
Schlumpf has quit [Quit: Ping timeout (120 seconds)]
Schlumpf has joined #yocto
florian has joined #yocto
leon-anavi has joined #yocto
mihai has quit [Quit: Leaving]
Ch^W has joined #yocto
peoliye has quit [Quit: Client closed]
twnqx has joined #yocto
jpuhlman has quit [Ping timeout: 240 seconds]
lexano has quit [Ping timeout: 248 seconds]
lexano has joined #yocto
agupta1 has joined #yocto
dtometzki has quit [Read error: Connection reset by peer]
dtometzki has joined #yocto
agupta1 has quit [Ping timeout: 256 seconds]
davidinux has joined #yocto
davidinux has quit [Ping timeout: 272 seconds]
davidinux has joined #yocto
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #yocto
starblue has quit [Ping timeout: 240 seconds]
starblue has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
davidinux has quit [Quit: WeeChat 3.0]
argonautx has joined #yocto
xmn has joined #yocto
Schlumpf has quit [Quit: Client closed]
ardo has quit [Read error: Connection reset by peer]
ruslan has joined #yocto
ardo has joined #yocto
prabhakarlad has quit [Quit: Client closed]
DougC has quit [Quit: Client closed]
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
hushmoney has quit [Quit: leaving]
hushmoney has joined #yocto
hushmoney has quit [Client Quit]
hushmoney has joined #yocto
agupta1 has joined #yocto
agupta1 has quit [Quit: Konversation terminated!]
kroon has quit [Quit: Leaving]
roussinm has quit [Quit: WeeChat 3.0]
roussinm has joined #yocto
rob_w has quit [Quit: Leaving]
ruslan has quit [Quit: Client closed]
prabhakarlad has joined #yocto
sakoman has joined #yocto
dgriego has joined #yocto
AKN has quit [Read error: Connection reset by peer]
<roussinm>
so in my adventure trying to have a nativesdk for developement, I'm trying to install nativesdk-libgl-mesa-dev, but it doesn't install any file inside the sdk. Looking at the packages-split I see the files, but they are not installed. I see that the directory is inside qtbase as a runtime-rprovides. Now I'm wondering it is because of the virtual-ness of the recipe that it doesn't install? Or I'm
<roussinm>
missing something that I don't understand of Yocto here.
<JPEW>
tlwoerner: Is there a "generic" link for the YPS I can use in a presentation? All I've found is the ones for specific "instances"
<DougC>
Saur[m] that message never appears in the log but i still get the QA issue
florian has quit [Quit: Ex-Chat]
lxc has joined #yocto
<lxc>
I'm trying to add liblsan to yocto sdk via TOOLCHAIN_TARGET_TASK. But only able to add gcc-sanitizers there. How to make liblsan be included as well?
<hushmoney>
i guess not because when i tried that it complained with some stacktrace in yacc.py
<Theo[m]1>
Hello all. I've been having errors with toaster when using an external DB. Is it better to seek for help here in IRC or via the toaster mailing list? (MySQL fails when running migration in a fresh db due an alter in orm.0020_models_bigautofield and PostgreSQL have issues once a build is submitted to toaster)
<landgraf>
What's the difference between append (aka +=) and :append ?
<landgraf>
nvm found the answer in the docs
mckoan is now known as mckoan|away
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
rsalveti has joined #yocto
<Saur[m]>
DougC: Are you looking at the config.log file inside the build directory? It should be somewhere inside tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git if I read your log correctly.
<DougC>
oh no. i was looking at the yocto log
<DougC>
ty
<DougC>
Saur[m] interesting. i dont see anything 'unsafe', but i do see some interesting errors that appear to be a side effect of me inheriting from autotools and letting the default do_configure do its thing
<DougC>
lots of unrecognized command line options
<DougC>
this is good. thank you for pointing that out. i have some more to chew on now
barometz has quit [Quit: No Ping reply in 180 seconds.]
barometz has joined #yocto
DougC has quit [Quit: Client closed]
prabhakarlad has quit [Quit: Client closed]
barometz has quit [Ping timeout: 246 seconds]
barometz has joined #yocto
goliath has joined #yocto
<fullstop>
This might not be the right place to ask this, but maybe someone here has run into this problem as well. I have a dunfell-based embedded system with openssh on it using systemd socket activation. It's worked wonderfully for us, but the openssh version on my desktop was upgraded and scp now uses SFTP by default.
<fullstop>
when I try to scp something to these systems, I have to use "scp -O" to use the legacy protocol or I receive the message "scp: Connection closed"
lxc has quit [Quit: Client closed]
<fullstop>
This only happens with the yocto-based setups, so it's not a new -> old openssh thing.
<twnqx>
the wonderful new defaults in openssh 9 :)
* twnqx
makes a ticket to add it for next OS release
<twnqx>
thanky ou for the reminder!
camus has quit [Read error: Connection reset by peer]
camus1 has joined #yocto
camus1 is now known as camus
goliath has quit [Quit: SIGSEGV]
seninha has joined #yocto
argonautx has quit [Quit: Leaving]
florian has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
Guest38 has joined #yocto
<Guest38>
Trying to upgrade the Yocto toolchains but one of the bootloaders is not happy about it. Is there a way to have yocto use an older toolchain just for 1 package?
<Guest38>
The meta-clang layer seems to be able to do this but that's kind of different maybe.
<Guest38>
We would still like to use GCC for this.
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<JaMa>
it might be easier to just fix the bootloader
<Guest38>
Its been weeks of working on that.
<Guest38>
The problem is we only have like 20bytes left before the compiler upgrade.
<JaMa>
yes it's painful, but it's way forward, spending weeks to build it with old toolchain will just postpone the issue
<Guest38>
There are other areas where the toolchain can't be updated because the kernel is on 2.6 and won't support past gcc5. Updating the kernel on those systems is probably not possible either.
<JaMa>
agreed, personally I don't like combo-layer to be used on regular basis (like poky is using), but it was great tool when combining multiple separate repos into one with reasonable git history
<RP>
JaMa: Just to be clear, it is horrible! It was ok at a time but has had it's day :)
<JaMa>
and the only reason why I don't like to use it on regular basis, because it's "good" for poky repo, but everybody else has to deal with multiple repos anyway, so it would be easier for everybody else if oe-core+bitbake+meta-yocto were handled the same (instead of combined already as poky)
<JaMa>
but it's true that I don't like git submodules and repo as well, so maybe it's just me getting more and more grumpy with age :)
<RP>
JaMa: if/when we get some standardised setup tool, poky will switch
<JaMa>
I wanted to write "challenge accepted", but I know how ugly that can of worms is, so I'll stay quiet :)
<JaMa>
I helped to write LGE's setup tool and I still don't like it as well
frieder has quit [Remote host closed the connection]
<RP>
JaMa: I did once write a design which I shared with a small number of people. The replies put me off touching it
<JaMa>
I was replying to some concepts on ML and for me the biggest fear is that in this case one tool cannot fit all (e.g. all our specific sauce to support doing different kinds of jenkins jobs which might fetch various layers in different versions with gerrit specific calls like fetching open reviews or overriding recipe SRC_URI/SRCREV based on review for specific component etc), either the tool would need to be
<JaMa>
super customizable (difficult) or it might be complicated to extend to cover whatever strange use-cases we already support with own setuptool
<RP>
JaMa: right, one won't suit everyone but I'd hope we could have something more standard people could start from
<JaMa>
in the end I wrote simple django app to generate the build config, which is then persited as a review in gerrit repo which then triggers various jenkins jobs which read the build config from the review
fitzsim has quit [Ping timeout: 256 seconds]
<JaMa>
I still haven't played with kas, it's still on my TODO
Guest38 has quit [Quit: Ping timeout (120 seconds)]
dacav has joined #yocto
<RP>
JaMa: I hear a lot of good things about it
* JaMa
too
fitzsim has joined #yocto
Guest5 has joined #yocto
dacav has quit [Ping timeout: 276 seconds]
starblue has quit [Ping timeout: 240 seconds]
Lemur-for-rent has joined #yocto
<Lemur-for-rent>
Hey all
Guest5 has quit [Client Quit]
<Lemur-for-rent>
Is it possible for a layer to append config content to local.conf?
<Lemur-for-rent>
i.e. I'm adding a custom layer built around a certain feature. I'd like the addition of that layer to extend local.conf with new options.
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
starblue has joined #yocto
GregStinocher[m] has joined #yocto
Minvera has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<JaMa>
Lemur-for-rent: why local.conf? You can do a lot of stuff in layer.conf, but be careful a lot of these things are considered asocial and for a good reason
<JaMa>
Lemur-for-rent: sometimes the reasonable compromise is for the layer to provide an .inc file and documenting the users are expected to include that to get all the features (or depending on some DISTRO_FEATURE to be enabled)
<JaMa>
just including a layer in bblayers.conf shouldn't cause (m)any unexpected side-effects to existing metadata
<halstead>
Hey GregStinocher[m] welcome to #yocto.
<GregStinocher[m]>
Thanks halstead:libera.chat !
halstead[m] has joined #yocto
<halstead[m]>
Pinging myself halstead sorry for the noise.
<GregStinocher[m]>
ping halstead
<GregStinocher[m]>
that looks better.
dacav has joined #yocto
halstead[m] has left #yocto [#yocto]
<GregStinocher[m]>
halstead: another ping
<halstead>
Perfect.
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
<RP>
GregStinocher[m]: welcome :)
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
<GregStinocher[m]>
Thanks RP !
<Lemur-for-rent>
JaMa: Thanks. You say `just including a layer in bblayers.conf shouldn't cause (m)any unexpected side-effects to existing metadata` but doesn't that action by default affects the active recipes (by having bbappends for those recipes)? Is that "m" in m(any)? :)
<JaMa>
Lemur-for-rent: ideally even the .bbappends should be controlled by some DISTRO_FEATURE or something, but in some cases it's more practical to break this rule (e.g. if the layer is completely useless without changing some PACKAGECONFIGs in some other recipes or enabling something in layer.conf, then I can imagine the argument that people just don't include it in bblayers.conf unless they really want all the
<JaMa>
side-effects from including it as well, but it shouldn't be taken lightly, that's why the (m)
<JaMa>
e.g. meta-security/README: DISTRO_FEATURES:append = " security" or meta-virtualization/README: DISTRO_FEATURES:append = " virtualization"
<JaMa>
this is needed to make the layer yocto-compatible, but in practise 99% users of these layers probably just include them in the bblayers.conf as well as add this DISTRO_FEATURE
<JaMa>
so it's just extra step to keep yocto-compatible script happy, but doesn't prevent the layers doing toxic stuff (not in the 2 examples I've mentioned I believe)
<Lemur-for-rent>
Oooo! I think I just might have gotten a conceptual level up on the purpose of DISTRO_FEATURES, thank you for that.
<Lemur-for-rent>
Until your post I always though having a layers bbappends appending all the recipes they want is an unavoidable fact of adding a new recipe.
<Lemur-for-rent>
Sure, one is still at the mercy of the of the layer creator, but at least there is a clear mechanism on how to prevent that behavior (if for example you just need a recipe from a layer and don't want it to affect other recipes with its bbappends)
mvlad has quit [Remote host closed the connection]
<RP>
Lemur-for-rent: adding a layer should not by default change the behaviour of the system, unless you actually enable it to do so as well
kovalevsky has quit [Quit: Leaving]
Lemur-for-rent has quit [Ping timeout: 252 seconds]
leon-anavi has quit [Quit: Leaving]
twnqx has quit [Ping timeout: 264 seconds]
roussinm has quit [Quit: WeeChat 3.0]
seninha has quit [Remote host closed the connection]
behanw has joined #yocto
jatedev has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
turkeykittin has joined #yocto
<turkeykittin>
How can I debug log something in a recipe? I'm trying to pass an environment variable in my recipe but I want to check what that variable is (i.e. check if it has been properly set)
florian has quit [Ping timeout: 264 seconds]
<JaMa>
turkeykittin: bitbake -e or bitbake-getvar
<turkeykittin>
Would an enviromental variable set by one recipe be readable by another?
<JaMa>
as in BB_ENV_EXTRAWHITE BB_ENV_PASSTHROUGH_ADDITIONS ? or just exported in some task? if the later then no
<JaMa>
if the other recipe depends on the first, then you can stage a file in sysroot and the other one can read it