All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Larsen <lars@visionweeding.com>
To: poky@yoctoproject.org
Subject: external kernel module - hash mismatch
Date: Mon, 8 May 2017 14:07:02 +0200	[thread overview]
Message-ID: <f9f3112c-9b77-df97-f5a3-17e46c3e3eb7@visionweeding.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

Hi

I have a recipe where I build an external kernel module (a driver).

I followed the model in the hello_mod.bb example, except that the 
SRC_URI is a git repository and  SRCREV= "${AUTOREV}"

I added
PACKAGE_INSTALL_append() = "kernel-module-camdriverV20"

and it works fine. just as expected.

*But*  If I push changes to the git  repository, bitbake fails hard with 
error messages like this:

/ERROR: When reparsing 
/home/lars/poky/meta-fpe/recipes-core/drivers/camdriver/camdriverV20.bb.do_compile, 
the basehash value changed from cc51ed245a373392856ed0fcd4309081 to 
77f012fc7c9ef8b6a34a0c751e3aaa5f. The metadata is not deterministic and 
this needs to be fixed.//
//ERROR: When reparsing 
/home/lars/poky/meta-fpe/recipes-core/drivers/camdriver/camdriverV20.bb.do_install, 
the basehash value changed from c3a246124e6a97131cdb34bc26db47a7 to 
2713df6e7f9e94aee601d6f654758959. The metadata is not deterministic and 
this needs to be fixed.//
/
the only way i can get it to build is to /rm -rf /tmp

/what am I doing wrong/?

-Lars/

-- 

Best Regards
Lars Larsen

F.Poulsen Engineering Aps
Tjørnager 16
4330 Hvalsø
Denmark
+45 29802784
www.visionweeding.com


[-- Attachment #2: Type: text/html, Size: 1955 bytes --]

             reply	other threads:[~2017-05-08 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08 12:07 Lars Larsen [this message]
2017-05-10  9:05 ` external kernel module - hash mismatch Panagiotis Tamtamis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f9f3112c-9b77-df97-f5a3-17e46c3e3eb7@visionweeding.com \
    --to=lars@visionweeding.com \
    --cc=poky@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.