make[2]: *** No rule to make target 'fitImage'. Stop.

make[2]: *** No rule to make target 'fitImage'. Stop.

[Robert P. J. Day]

  i'll start a new thread to focus on just this issue. again, building
core-image-minimal for mpc8315e-rdb, adding this to local.conf:

  INHERIT += "kernel-fitimage"             <-- do i need this line?
  KERNEL_IMAGETYPES_append = " fitImage"

anyway, run:

  $ bitbake virtual/kernel

and eventually get:

  make[2]: *** No rule to make target 'fitImage'.  Stop.

which makes sense since there is no such make target defined in the
kernel, but that shouldn't be happening since the image type of
"fitImage" should be mapped to "zImage" in kernel-fitimage.bbclass,
should it not?

python __anonymous () {
    kerneltypes = d.getVar('KERNEL_IMAGETYPES') or ""
    if 'fitImage' in kerneltypes.split():
        depends = d.getVar("DEPENDS")
        depends = "%s u-boot-mkimage-native dtc-native" % depends
        d.setVar("DEPENDS", depends)

        if d.getVar("UBOOT_ARCH") == "x86":
            replacementtype = "bzImage"
        else:
            replacementtype = "zImage"

        # Override KERNEL_IMAGETYPE_FOR_MAKE variable, which is internal
        # to kernel.bbclass . We have to override it, since we pack zImage
        # (at least for now) into the fitImage .
        typeformake = d.getVar("KERNEL_IMAGETYPE_FOR_MAKE") or ""
        if 'fitImage' in typeformake.split():
            d.setVar('KERNEL_IMAGETYPE_FOR_MAKE', typeformake.replace('fitImage', replacementtype))
        ... snip ...

isn't that snippet supposed to replace "fitImage" with "zImage" in
KERNEL_IMAGETYPE_FOR_MAKE? but if i dump with:

  $ bitbake -e virtual/kernel

i get:

  # $KERNEL_IMAGETYPES [3 operations]
  ... snip ...
  KERNEL_IMAGETYPES="uImage  fitImage"

and

  # $KERNEL_IMAGETYPE_FOR_MAKE
  #   set kernel.bbclass:48 [__anon_81__home_rpjday_oe_dist_layers_poky_meta_classes_kernel_bbclass]
  #     "uImage  fitImage"
  KERNEL_IMAGETYPE_FOR_MAKE="uImage  fitImage"

so "fitImage" is still there. shouldn't that have been replaced by
"zImage"? what am i overlooking here?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: make[2]: *** No rule to make target 'fitImage'. Stop.

[Robert P. J. Day]

On Mon, 13 Mar 2017, Robert P. J. Day wrote:

>
>   i'll start a new thread to focus on just this issue. again, building
> core-image-minimal for mpc8315e-rdb, adding this to local.conf:
>
>   INHERIT += "kernel-fitimage"             <-- do i need this line?
>   KERNEL_IMAGETYPES_append = " fitImage"
>
> anyway, run:
>
>   $ bitbake virtual/kernel
>
> and eventually get:
>
>   make[2]: *** No rule to make target 'fitImage'.  Stop.

... snip ...

  i would still love to figure out how to generate a simple FIT image
when building core-image-minimal for mpc8315e-rdb.

  first, based on what i read, my first attempt was to add the
following line to local.conf:

  KERNEL_IMAGETYPES_append = " fitImage"

however:

  $ bitbake virtual/kernel

  ... snip ...

  | NOTE: make -j 8 HOSTCC=gcc  HOSTCPP=gcc  -E uImage
  CC=powerpc-poky-linux-gcc  -fuse-ld=bfd LD=powerpc-poky-linux-ld.bfd
  | NOTE: make -j 8 HOSTCC=gcc  HOSTCPP=gcc  -E fitImage
  CC=powerpc-poky-linux-gcc  -fuse-ld=bfd LD=powerpc-poky-linux-ld.bfd

  ... snip ...

  | make[2]: *** No rule to make target 'fitImage'.  Stop.
  | Makefile:150: recipe for target 'sub-make' failed
  | make[1]: *** [sub-make] Error 2
  | Makefile:24: recipe for target '__sub-make' failed
  | make: *** [__sub-make] Error 2

which makes sense since there is no such target, "fitImage", in the
kernel build structure.

  what am i screwing up here? how do i generate a simple FIT image?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: make[2]: *** No rule to make target 'fitImage'. Stop.

[Belisko Marek]

Hi Robert,

On Tue, Mar 14, 2017 at 9:16 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Mon, 13 Mar 2017, Robert P. J. Day wrote:
>
>>
>>   i'll start a new thread to focus on just this issue. again, building
>> core-image-minimal for mpc8315e-rdb, adding this to local.conf:
>>
>>   INHERIT += "kernel-fitimage"             <-- do i need this line?
>>   KERNEL_IMAGETYPES_append = " fitImage"
>>
>> anyway, run:
>>
>>   $ bitbake virtual/kernel
>>
>> and eventually get:
>>
>>   make[2]: *** No rule to make target 'fitImage'.  Stop.
>
> ... snip ...
>
>   i would still love to figure out how to generate a simple FIT image
> when building core-image-minimal for mpc8315e-rdb.
>
>   first, based on what i read, my first attempt was to add the
> following line to local.conf:
>
>   KERNEL_IMAGETYPES_append = " fitImage"
You need probably also add:

KERNEL_CLASSES += "kernel-fitimage"

to local.conf
>
> however:
>
>   $ bitbake virtual/kernel
>
>   ... snip ...
>
>   | NOTE: make -j 8 HOSTCC=gcc  HOSTCPP=gcc  -E uImage
>   CC=powerpc-poky-linux-gcc  -fuse-ld=bfd LD=powerpc-poky-linux-ld.bfd
>   | NOTE: make -j 8 HOSTCC=gcc  HOSTCPP=gcc  -E fitImage
>   CC=powerpc-poky-linux-gcc  -fuse-ld=bfd LD=powerpc-poky-linux-ld.bfd
>
>   ... snip ...
>
>   | make[2]: *** No rule to make target 'fitImage'.  Stop.
>   | Makefile:150: recipe for target 'sub-make' failed
>   | make[1]: *** [sub-make] Error 2
>   | Makefile:24: recipe for target '__sub-make' failed
>   | make: *** [__sub-make] Error 2
>
> which makes sense since there is no such target, "fitImage", in the
> kernel build structure.
>
>   what am i screwing up here? how do i generate a simple FIT image?
>
> 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

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

Re: make[2]: *** No rule to make target 'fitImage'. Stop.

[Robert P. J. Day]

On Tue, 14 Mar 2017, Belisko Marek wrote:

> Hi Robert,
>
> On Tue, Mar 14, 2017 at 9:16 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> > On Mon, 13 Mar 2017, Robert P. J. Day wrote:
> >
> >>
> >>   i'll start a new thread to focus on just this issue. again, building
> >> core-image-minimal for mpc8315e-rdb, adding this to local.conf:
> >>
> >>   INHERIT += "kernel-fitimage"             <-- do i need this line?
> >>   KERNEL_IMAGETYPES_append = " fitImage"
> >>
> >> anyway, run:
> >>
> >>   $ bitbake virtual/kernel
> >>
> >> and eventually get:
> >>
> >>   make[2]: *** No rule to make target 'fitImage'.  Stop.
> >
> > ... snip ...
> >
> >   i would still love to figure out how to generate a simple FIT image
> > when building core-image-minimal for mpc8315e-rdb.
> >
> >   first, based on what i read, my first attempt was to add the
> > following line to local.conf:
> >
> >   KERNEL_IMAGETYPES_append = " fitImage"
> You need probably also add:
>
> KERNEL_CLASSES += "kernel-fitimage"
>
> to local.conf

  that *appears* to have solved the problem ... so why is it i didn't
realize that? where is that written up that i somehow missed it?

  and would it not make sense that selecting FIT image in one variable
should automatically set the other required variables?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: make[2]: *** No rule to make target 'fitImage'. Stop.

[Belisko Marek]

On Tue, Mar 14, 2017 at 9:53 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Tue, 14 Mar 2017, Belisko Marek wrote:
>
>> Hi Robert,
>>
>> On Tue, Mar 14, 2017 at 9:16 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>> > On Mon, 13 Mar 2017, Robert P. J. Day wrote:
>> >
>> >>
>> >>   i'll start a new thread to focus on just this issue. again, building
>> >> core-image-minimal for mpc8315e-rdb, adding this to local.conf:
>> >>
>> >>   INHERIT += "kernel-fitimage"             <-- do i need this line?
>> >>   KERNEL_IMAGETYPES_append = " fitImage"
>> >>
>> >> anyway, run:
>> >>
>> >>   $ bitbake virtual/kernel
>> >>
>> >> and eventually get:
>> >>
>> >>   make[2]: *** No rule to make target 'fitImage'.  Stop.
>> >
>> > ... snip ...
>> >
>> >   i would still love to figure out how to generate a simple FIT image
>> > when building core-image-minimal for mpc8315e-rdb.
>> >
>> >   first, based on what i read, my first attempt was to add the
>> > following line to local.conf:
>> >
>> >   KERNEL_IMAGETYPES_append = " fitImage"
>> You need probably also add:
>>
>> KERNEL_CLASSES += "kernel-fitimage"
>>
>> to local.conf
>
>   that *appears* to have solved the problem ... so why is it i didn't
> realize that? where is that written up that i somehow missed it?
It is not documented in yocto manual (I cannot find anything about
fitimage at all), so maybe it could be extended.
>
>   and would it not make sense that selecting FIT image in one variable
> should automatically set the other required variables?
I think something like that can be doable and it will save a lot of
time for people who want's to have it enabled.
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
>
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
>

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

Re: make[2]: *** No rule to make target 'fitImage'. Stop.

[Robert P. J. Day]

On Wed, 15 Mar 2017, Belisko Marek wrote:

> On Tue, Mar 14, 2017 at 9:53 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> > On Tue, 14 Mar 2017, Belisko Marek wrote:
> >
> >> Hi Robert,
> >>
> >> On Tue, Mar 14, 2017 at 9:16 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >> > On Mon, 13 Mar 2017, Robert P. J. Day wrote:
> >> >
> >> >>
> >> >>   i'll start a new thread to focus on just this issue. again, building
> >> >> core-image-minimal for mpc8315e-rdb, adding this to local.conf:
> >> >>
> >> >>   INHERIT += "kernel-fitimage"             <-- do i need this line?
> >> >>   KERNEL_IMAGETYPES_append = " fitImage"
> >> >>
> >> >> anyway, run:
> >> >>
> >> >>   $ bitbake virtual/kernel
> >> >>
> >> >> and eventually get:
> >> >>
> >> >>   make[2]: *** No rule to make target 'fitImage'.  Stop.
> >> >
> >> > ... snip ...
> >> >
> >> >   i would still love to figure out how to generate a simple FIT image
> >> > when building core-image-minimal for mpc8315e-rdb.
> >> >
> >> >   first, based on what i read, my first attempt was to add the
> >> > following line to local.conf:
> >> >
> >> >   KERNEL_IMAGETYPES_append = " fitImage"
> >> You need probably also add:
> >>
> >> KERNEL_CLASSES += "kernel-fitimage"
> >>
> >> to local.conf
> >
> >   that *appears* to have solved the problem ... so why is it i didn't
> > realize that? where is that written up that i somehow missed it?

> It is not documented in yocto manual (I cannot find anything about
> fitimage at all), so maybe it could be extended.

  i'll check later to see where it would seem to belong, unless
someone has a suggestion.

> >   and would it not make sense that selecting FIT image in one
> > variable should automatically set the other required variables?

> I think something like that can be doable and it will save a lot of
> time for people who want's to have it enabled.

  actually, i take back that suggestion, as i think it would overly
complicate kernel.bbclass (at least the way i read it).

  i can see that, for backward compatibility, kernel.bbclass contains
the following:

  # Here we pull in all various kernel image types which we support.
  #
  # In case you're wondering why kernel.bbclass inherits the other image
  # types instead of the other way around, the reason for that is to
  # maintain compatibility with various currently existing meta-layers.
  # By pulling in the various kernel image types here, we retain the
  # original behavior of kernel.bbclass, so no meta-layers should get
  # broken.
  #
  # KERNEL_CLASSES by default pulls in kernel-uimage.bbclass, since this
  # used to be the default behavior when only uImage was supported. This
  # variable can be appended by users who implement support for new kernel
  # image types.

  KERNEL_CLASSES ?= " kernel-uimage "
  inherit ${KERNEL_CLASSES}

so it's quite simple to extend the set of .bbclass files that provide
new kernel image types with, say:

  KERNEL_CLASSES += "kernel-fitimage"

beyond that, however, since a new kernel class file might define a
*pile* of new kernel image types, poor kernel.bbclass would need to
recognize all of them and know which kernel class file to inherit for
each new kernel type, which seems unwieldy.

  so as long as how to define new kernel image types is explained
clerly (is it?), then a discussion of FIT images should simply need to
refer the reader to that section.

  thoughts?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================