>
>
>
> On 11/23/2020 2:16 AM, Federico Pellegrin wrote:
>
>
> Hi,
> I think it would be interesting information to know "how" you change the
> value inside "u-boot-at91/sama5d3_xplained_nandflash_config".
>
> As every time you rebuild it may
Hi,
I think it would be interesting information to know "how" you change the
value inside "u-boot-at91/sama5d3_xplained_nandflash_config".
As every time you rebuild it may be redownloaded, you should do this via a
patch to append to the recipe.
Are you doing this? Or just changing it locally?
Signed-off-by: Federico Pellegrin
---
.../{aircrack-ng_1.3.bb => aircrack-ng_1.6.bb}| 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
rename recipes-security/aircrack-ng/{aircrack-ng_1.3.bb => aircrack-ng_1.6.bb}
(82%)
diff --git a/recipes-security/aircrack-ng/ai
Add possibility, via PACKAGECONFIG variable, to enable cryptodev
(hardware crypto acceleration) for gnutls in a very similar way
as it is already present for openssl.
Signed-off-by: Federico Pellegrin
---
meta/recipes-support/gnutls/gnutls_3.7.1.bb | 1 +
1 file changed, 1 insertion(+)
diff
Hi,
To skip the QA you can use:
INSANE_SKIP_${PN} += "dev-elf"
(or any QA part you'd like to skip, ie. dev-elf or dev-so ...)
Cheers,
Federico
Il giorno gio 23 set 2021 alle ore 15:33 Lijun Chen
ha scritto:
> Hi,
>
>
> If I switch to the default setting of the googletest recipe, the header
gt; /usr/local/include/gmock/internal/custom/README.md
> Please set FILES such that these items are packaged. Alternatively if they
> are unneeded, avoid installing them or delete them within do_install.
> googletest: 69 installed and not shipped files. [installed-vs-shipped]
> E
1 9:27 AM, Federico Pellegrin wrote:
> >
> > Hello,
> > Running on a quite recent kernel (5.14.10 from Fedora 34) I've came
> > across a problem when building util-linux (2.35.2) native, namely in the
> > configure phase:
> >
> > configure: error: raw selec
Hi Jupiter,
To centralize, agreed that you are using systemd, one way I could see is
setting the variables in systemd-system.conf using the DefaultEnvironment
directive, see:
https://freedesktop.org/software/systemd/man/systemd-system.conf.html
This states:
DefaultEnvironment=¶
Hello,
Running on a quite recent kernel (5.14.10 from Fedora 34) I've came across
a problem when building util-linux (2.35.2) native, namely in the configure
phase:
configure: error: raw selected, but required raw.h header file not available
After a bit or research I believe it is due to:
Hi Jupiter,
/etc/profile and similar are interactive shell (/bash) concepts, not really
system startup ones. So indeed: just on a login (be it local, ssh and so
on) they are executed.
If you want to execute something else without the need for logging it, you
should look elsewhere, depending on
Hello,
Some more details would be needed (ie. you have systemd?), but this could
be a good point to start: https://wiki.archlinux.org/title/Systemd-resolved
(ie. see a bit down, like:
https://wiki.archlinux.org/title/Systemd-resolved#Manually )
Cheers,
Federico
Il giorno gio 13 gen 2022 alle
Hello,
I've been playing around building a Yocto imagine based on kirkstone/master
on the just released Fedora 36 beta test image. (just to give a few bits
more details: builds a MX8X image, works perfectly fine with Fedora 34 and
35 since quite some time)
The first and most obvious thing I've
lt;
> richard.pur...@linuxfoundation.org> wrote:
>
>> On Sun, 2022-04-03 at 09:12 +0200, Federico Pellegrin wrote:
>> > I've been playing around building a Yocto imagine based on
>> kirkstone/master on
>> > the just released Fedora 36 beta test image. (just to give
Hi Jupiter,
I cannot help you on the specific chip you ask, but responding to the
second part of your question I have quite good experience with Microchip
WILC1000/3000 on SDIO which, after a part separate repo and then staging,
is now in mailine from quite some time:
Hi all,
I've been working with signing packages via gpg (specificall RPM, but that
shouldn't really matter) lately and things mostly work fine (modulo that
small patch from some 2 weeks ago now in master).
I have just one more possibly minor issue I wanted to get possibly an
opinion from the
-ed). For more recent versions it may just
potentially create confusion IMO.
Cheers,
Federico
Il giorno dom 5 giu 2022 alle ore 00:58 akuster808
ha scritto:
>
>
> On 6/3/22 23:31, Federico Pellegrin wrote:
> > Since ~16 months the base of meta-rust was merged into meta-oe,
> >
signing-keys-1.0-r0
This MR will fix the situation bringing the specific provider
PROVIDES to include also the generic package (RPM example):
signing-keys
signing-keys-rpm = 1.0-r0
Likely another way could be also to change the requirement for
dev or just allow empty packages as well.
Signed-off-by
Since ~16 months the base of meta-rust was merged into meta-oe,
down to honister as far as I can see, and therefore the indications
to use meta-rust are really not needed and may just create extra
work and possibly problems to users.
---
README | 12
1 file changed, 12 deletions(-)
Hi,
After applying the patch to the source, I suppose you built the kernel (and
is just missing in your email) ? If not that is a quite important step
missing ;)
Besides that:
1) preempt-rt patch is often very kernel version specific, while I see your
two version don't exactly match: didn't it
Hi Michael,
Sorry for the maybe obvious remark (and cannot find the original post if
maybe you gave more details) but: did you enable in openssh daemon
configuration to allow for root login?
By default that is not permitted, in /etc/ssh/sshd_config you have:
#PermitRootLogin prohibit-password
Hello David,
There is nothing really special compared to "usual" recipes or whatever you
use RPM or another packager.
In short:
1) You should create (likely in a layer of yours) the recipe for your
"third-party" package. You should put in this package the right
dependencies (using either DEPENDS
Hello,
Just as a small reference since I raised some doubts and questions in
Buildroot community on this: there has been also some troubles to
understand the correctness or not there (as I found some packages with
problems due to this source-less management) and this then sparked, besides
or modules that could be executed as scripts
as well as modules). (here is some discussion:
http://lists.busybox.net/pipermail/buildroot/2022-August/648686.html )
Cheers,
Federico
>
> Alex
>
> On Sun, 13 Nov 2022 at 14:25, Federico Pellegrin
> wrote:
> >
> >
> &g
Hi,
nodejs is very, *very*, heavy to build due to it's complex C++ code. I
would suggest you to limit the number of parallel builds supported: this
may slow down other (lighter) builds but will avoid going out of memory for
heavy ones such as node.
This can be done by putting in your local
Hi,
Il giorno gio 16 nov 2023 alle ore 07:26 MOHAMMED HASSAN <
hassanchatta...@gmail.com> ha scritto:
> *| install: cannot create directory
> ‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/package-lock.json’:
> File exists*
>
>
>
>
>
25 matches
Mail list logo
