[yocto] out of tree kernel modules using autotools
Hello,
I'm beginning a process to try to build zfs-on-linux for my image (as I
have yet to find any existing work in this area), and am running into some
trouble building out of tree kernel modules with autotools.
I've been loosely basing my recipe off of the one over here:
https://github.com/Freescale/meta-freescale/blob/master/recipes-kernel/kernel-modules/kernel-module-perf-qoriq_0.8.2.bb
Here is the current recipe:
inherit module autotools
SRC_URI = "
http://archive.zfsonlinux.org/downloads/zfsonlinux/spl/spl-0.6.5.6.tar.gz";
SRC_URI[md5sum] = "4544b80018ddc5c39ed395363a582228"
SRC_URI[sha256sum] =
"167595fe76eb5497c3a1ffe396b6300155d0cbe46d06824a710099ca1ae1b8bd"
EXTRA_OECONF += "--with-config=kernel --with-linux=${KERNEL_PATH}"
This recipe builds fine, except that it's using the installed kernel
sources for the base ubuntu system rather than those build by yocto. I can
confirm that the kernel has already been built, and sources are available,
however when entering into the devshell for this package neither KERNEL_SRC
nor KERNEL_PATH are defined (they are simply empty), despite what the
documentation for the module bbclass indicates.
It seems I'm missing something important here? Also any other references
to examples of building these types of modules would be greatly appreciated.
Regards,
Matt
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] out of tree kernel modules using autotools
On Thu, Apr 7, 2016 at 10:05 AM, Matt Broadstone wrote:
> Hello,
> I'm beginning a process to try to build zfs-on-linux for my image (as I
> have yet to find any existing work in this area), and am running into some
> trouble building out of tree kernel modules with autotools.
>
> I've been loosely basing my recipe off of the one over here:
> https://github.com/Freescale/meta-freescale/blob/master/recipes-kernel/kernel-modules/kernel-module-perf-qoriq_0.8.2.bb
>
> Here is the current recipe:
>
>
> inherit module autotools
> SRC_URI = "
> http://archive.zfsonlinux.org/downloads/zfsonlinux/spl/spl-0.6.5.6.tar.gz";
> SRC_URI[md5sum] = "4544b80018ddc5c39ed395363a582228"
> SRC_URI[sha256sum] =
> "167595fe76eb5497c3a1ffe396b6300155d0cbe46d06824a710099ca1ae1b8bd"
> EXTRA_OECONF += "--with-config=kernel --with-linux=${KERNEL_PATH}"
>
>
> This recipe builds fine, except that it's using the installed kernel
> sources for the base ubuntu system rather than those build by yocto. I can
> confirm that the kernel has already been built, and sources are available,
> however when entering into the devshell for this package neither KERNEL_SRC
> nor KERNEL_PATH are defined (they are simply empty), despite what the
> documentation for the module bbclass indicates.
>
> It seems I'm missing something important here? Also any other references
> to examples of building these types of modules would be greatly appreciated.
>
> Regards,
> Matt
>
It looks like the variable is indeed defined, however not in a way where I
could have seen it via the devshell. I fixed the build by adding an
additional `--with-linux-obj=${STAGING_KERNEL_BUILDDIR}`, apologies for the
noise!
Matt
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] cmake recipe find_file failure
Hi,
I'm trying to build a recipe for apache qpid, which is a cmake-based
project. Configuration is currently failing due to "find_file" not being
able to find a file in the source directory for the build:
find_file(QPID_VERSION_FILE NAMES QPID_VERSION.txt PATHS
${PROJECT_SOURCE_DIR}/.. ${PROJECT_SOURCE_DIR} NO_DEFAULT_PATH)
mark_as_advanced(QPID_VERSION_FILE)
if(NOT QPID_VERSION_FILE)
message(FATAL_ERROR "Cannot find QPID_VERSION.txt")
endif(NOT QPID_VERSION_FILE)
What's truly puzzling is that if I try the following:
execute_process(COMMAND ls ${PROJECT_SOURCE_DIR} OUTPUT_VARIABLE
TEST_OUTPUT)
message("LS RESULT: ${TEST_OUTPUT}")
the paths are indeed correct; the result of the ls contains the
QPID_VERSION.txt file. This seems to indicate to me that something else is
failing internally, but am not sure where I should be looking exactly.
Has anyone experienced this before? Are there any general tips for
debugging these types of failures in cmake projects in yocto?
Regards,
Matt
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] cmake recipe find_file failure
On Sat, Apr 9, 2016 at 8:43 AM, Matt Broadstone wrote:
> Hi,
> I'm trying to build a recipe for apache qpid, which is a cmake-based
> project. Configuration is currently failing due to "find_file" not being
> able to find a file in the source directory for the build:
>
> find_file(QPID_VERSION_FILE NAMES QPID_VERSION.txt PATHS
> ${PROJECT_SOURCE_DIR}/.. ${PROJECT_SOURCE_DIR} NO_DEFAULT_PATH)
> mark_as_advanced(QPID_VERSION_FILE)
> if(NOT QPID_VERSION_FILE)
> message(FATAL_ERROR "Cannot find QPID_VERSION.txt")
> endif(NOT QPID_VERSION_FILE)
>
> What's truly puzzling is that if I try the following:
>
> execute_process(COMMAND ls ${PROJECT_SOURCE_DIR} OUTPUT_VARIABLE
> TEST_OUTPUT)
> message("LS RESULT: ${TEST_OUTPUT}")
>
> the paths are indeed correct; the result of the ls contains the
> QPID_VERSION.txt file. This seems to indicate to me that something else is
> failing internally, but am not sure where I should be looking exactly.
>
> Has anyone experienced this before? Are there any general tips for
> debugging these types of failures in cmake projects in yocto?
>
> Regards,
> Matt
>
Continuing in the tradition of answering my own silly questions, this seems
to be related to the fact that the cmake.bbclass
overwrites CMAKE_FIND_ROOT_PATH's default value (empty) with yocto-specific
values so as to prevent bleed from the host. Hope this helps someone in the
future.
Matt
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] any pointers to a yocto-based image to use as a live install utility?
On Wed, May 25, 2016 at 11:03 AM, Robert P. J. Day wrote: > On Wed, 25 May 2016, akuster wrote: > > > Robert, > > > > On 05/25/2016 03:18 AM, Robert P. J. Day wrote: > > > > > > specifically in the context of powerpc systems, are there any > > > suggestions for an image that could be used to boot an older powerpc > > > system, running completely out of ram, and using that as an install > > > utility which would then be responsible for detecting/formatting a > > > hard drive, creating/formatting filesystems, downloading/installing > > > the OS, post-install configuration and so on? > > > > This sounds like an installer MV has and that I have been given approval > > to release (just haven’t had the time to submit it). Its X86 centric ie > > uses grub and support efi > > > I'm incredibly interested in this, do you have a tentative release plan? Regards, Matt > > It boots up from an iso image and runs a ncurses based interface that > > allows you to select HD, create partitions and filesystem types. It will > > install what ever image you built. It creates grub conf and installs it. > > The installer bit is written in python. > > given that it's based on grub, how compatible would it be with a > powerpc target? what i need is *specifically* for powerpc. and what > i'm after can't require a graphical interface, it needs to be > script-based as it will have to run on remote systems. > > rday > > -- > > > Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
