From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Struggling with creating recipe liblockdev
Date: Wed, 05 Sep 2012 12:22:43 +0100 [thread overview]
Message-ID: <50473603.4030708@communistcode.co.uk> (raw)
I am really struggling with making a new recipe for a library called
lockdev. It is fairly old and fairly basic but I am failling at the
initial hurdles!
So far I have:
DESCRIPTION = "Manage character and block device lockfiles."
HOMEPAGE =
"http://anonscm.debian.org/gitweb/?p=lockdev/lockdev.git;a=summary"
LICENSE = "LGPLv2.1"
LIC_FILES_CHKSUM = "file://LICENSE;md5=d8045f3b8f929c1cb29a1e3fd737b499"
PR = "r1.4"
PV = "1.0.3"
SRC_URI =
"http://ftp.de.debian.org/debian/pool/main/l/lockdev/lockdev_${PV}.orig.tar.gz
\
file://lockdev_1.0.3-1.4.patch \
"
SRC_URI[md5sum] = "64b9c1b87b125fc348e892e24625524a"
SRC_URI[sha256sum] =
"ccae635d7ac3fdd50897eceb250872b3d9a191d298f213e7f0c836910d869f82"
Which gives me the error:NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: liblockdev: LIC_FILES_CHKSUM points to an
invalid file:
/home/jack/Projects/poky-rasp/raspberry/tmp/work/armv6-vfp-poky-linux-gnueabi/liblockdev-1.0.3-r1.4/liblockdev-1.0.3/LICENSE
ERROR: Logfile of failure stored in:
/home/jack/Projects/poky-rasp/raspberry/tmp/work/armv6-vfp-poky-linux-gnueabi/liblockdev-1.0.3-r1.4/temp/log.do_configure.29246
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| DEBUG: Shell function do_configure finished
| DEBUG: Executing python function do_qa_configure
| NOTE: Checking autotools environment for common misconfiguration
| DEBUG: Python function do_qa_configure finished
| ERROR: Function failed: liblockdev: LIC_FILES_CHKSUM points to an
invalid file:
/home/jack/Projects/poky-rasp/raspberry/tmp/work/armv6-vfp-poky-linux-gnueabi/liblockdev-1.0.3-r1.4/liblockdev-1.0.3/LICENSE
ERROR: Task 5
(/home/jack/Projects/poky-rasp/meta-oe/meta-oe/recipes-extended/liblockdev/liblockdev_1.0.3.bb,
do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 798 tasks of which 797 didn't need to be
rerun and 1 failed.
Summary: 1 task failed:
/home/jack/Projects/poky-rasp/meta-oe/meta-oe/recipes-extended/liblockdev/liblockdev_1.0.3.bb,
do_configure
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
When I enter a devshell, the LICENSE file is there but in the directory
../liblockdev-1.0.3 not the directory I am dropped in. Where am I going
wrong?
[jack@archHP liblockdev-1.0.3]$ pwd
/home/jack/Projects/poky-rasp/raspberry/tmp/work/armv6-vfp-poky-linux-gnueabi/liblockdev-1.0.3-r1.4/liblockdev-1.0.3
[jack@archHP liblockdev-1.0.3]$ cd ..
[jack@archHP liblockdev-1.0.3-r1.4]$ tree
.
|-- liblockdev-1.0.3
| |-- debian
| | |-- NEWS
| | |-- changelog
| | |-- compat
| | |-- control
| | |-- copyright
| | |-- liblockdev1-dbg.dirs
| | |-- liblockdev1-dbg.docs
| | |-- liblockdev1-dev.dirs
| | |-- liblockdev1-dev.manpages
| | |-- liblockdev1-perl.dirs
| | |-- liblockdev1.postinst
| | `-- rules
| `-- patches
| |-- lockdev_1.0.3-1.4.patch ->
/home/jack/Projects/poky-rasp/meta-oe/meta-oe/recipes-extended/liblockdev/files/lockdev_1.0.3-1.4.patch
| `-- series
|-- license-destdir
| `-- liblockdev
| `-- generic_LGPLv2.1
|-- lockdev-1.0.3
| |-- AUTHORS
| |-- ChangeLog
| |-- ChangeLog.old
| |-- LICENSE
| |-- LockDev
| | |-- Changes
| | |-- LockDev.pm
| | |-- LockDev.xs
| | |-- MANIFEST
| | |-- Makefile.PL
| | |-- test.pl
| | `-- typemap
| |-- Makefile
| |-- README.debug
| |-- Rules.mk
| |-- debian
| | `-- foo
| |-- docs
| | |-- LSB.991201
| | `-- lockdev.3
| `-- src
| |-- lockdev.c
| |-- lockdev.h
| |-- sample.c
| `-- ttylock.h
|-- lockdev_1.0.3-1.4.patch
`-- temp
|-- log.do_configure -> log.do_configure.29246
|-- log.do_configure.29088
|-- log.do_configure.29246
|-- log.do_devshell -> log.do_devshell.29318
|-- log.do_devshell.29150
|-- log.do_devshell.29318
|-- log.do_fetch -> log.do_fetch.29023
|-- log.do_fetch.29023
|-- log.do_patch -> log.do_patch.29028
|-- log.do_patch.29028
|-- log.do_populate_lic_setscene -> log.do_populate_lic_setscene.29015
|-- log.do_populate_lic_setscene.29015
|-- log.do_unpack -> log.do_unpack.29024
|-- log.do_unpack.29024
|-- log.task_order
|-- run.base_do_fetch.29023
|-- run.base_do_patch.29028
|-- run.base_do_unpack.29024
|-- run.do_configure.29088
|-- run.do_configure.29246
|-- run.do_devshell.29150
|-- run.do_devshell.29318
|-- run.do_fetch.29023
|-- run.do_patch.29028
|-- run.do_populate_lic_setscene.29015
|-- run.do_qa_configure.29088
|-- run.do_qa_configure.29246
|-- run.do_unpack.29024
|-- run.patch_do_patch.29028
|-- run.sstate_unpack_package.29015
|-- run.sysroot_cleansstate.29088
`-- run.sysroot_cleansstate.29246
11 directories, 69 files
[jack@archHP liblockdev-1.0.3-r1.4]$
Thanks for any help in advance!
Regards,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next reply other threads:[~2012-09-05 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 11:22 Jack Mitchell [this message]
2012-09-05 11:30 ` Struggling with creating recipe liblockdev Burton, Ross
2012-09-05 11:32 ` Jack Mitchell
2012-09-05 11:33 ` Phil Blundell
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=50473603.4030708@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@lists.openembedded.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.