Hi, On Tue, Aug 18, 2020 at 11:32 PM Khem Raj <[email protected]> wrote: > > On Tue, Aug 18, 2020 at 1:09 PM Marek Belisko <[email protected]> wrote: > > > > Hi, > > > > I'm using poky warrion and added meta-openembedded to have libgpiod > > recipe. I'm using a custom 5.6 kernel and I would like to update > > libgpiod to version 1.5.1 but this version needs kernel headers >= 5.g > > (but kernel headers on warrior are 4.x). My idea was to somehow pass > > STAGING_KERNEL_DIR to CFLAGS but this seems it's not the way to go. As > > I understand from the kernel-header recipe I cannot simply bump > > kernel-headers because libc depends on it also. Any ideas how to > > achieve this? Thanks. > > if it need UAPI headers from kernel then linux-libc-headers should be > bumped for best results How about this notice at the beginning of the linux-libc-heades recipe: ######################################################################### #### PLEASE READ ######################################################################### # # You're probably looking here thinking you need to create some new copy # of linux-libc-headers since you have your own custom kernel. To put # this simply, you DO NOT. # # Why? These headers are used to build the libc. If you customise the # headers you are customising the libc and the libc becomes machine # specific. Most people do not add custom libc extensions to the kernel # and have a machine specific libc. # # But you have some kernel headers you need for some driver? That is fine # but get them from STAGING_KERNEL_DIR where the kernel installs itself. # This will make the package using them machine specific but this is much # better than having a machine specific C library. This does mean your # recipe needs a # do_configure[depends] += "virtual/kernel:do_shared_workdir" # but again, that is fine and makes total sense. # # There can also be a case where your kernel extremely old and you want # an older libc ABI for that old kernel. The headers installed by this # recipe should still be a standard mainline kernel, not your own custom # one. # # -- RP
I think it's not the way to go. An I'm using pretty new kernel 5.6. So STAGIG_KERNEL_DIR is not correct way? Thanks. > > > > > BR, > > > > marek > > > > -- > > as simple and primitive as possible > > ------------------------------------------------- > > Marek Belisko - OPEN-NANDRA > > Freelance Developer > > > > Ruska Nova Ves 219 | Presov, 08005 Slovak Republic > > Tel: +421 915 052 184 > > skype: marekwhite > > twitter: #opennandra > > web: http://open-nandra.com > > BR, marek -- as simple and primitive as possible ------------------------------------------------- Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#86446): https://lists.openembedded.org/g/openembedded-devel/message/86446 Mute This Topic: https://lists.openembedded.org/mt/76273189/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
