From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: create ipk failed...
Date: Thu, 06 May 2010 08:12:31 +0200 [thread overview]
Message-ID: <hrtmkf$bp1$2@dough.gmane.org> (raw)
In-Reply-To: <l2pad875cab1005052019o60a63221ya1727def61751e98@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06-05-10 05:19, yenchengwang wrote:
>>
>> hi all,
>> I have a problem when try to "bitbake -b recipes/minicom/
>> minicom-mypkg_2.4.bb"
>>
>> the bellow is the content of my bb file:
>> file name is minicom-mypkg_2.4.bb
>> *********************************************************************************************************
>>
>> SECTION = "console/network"
>> DEPENDS = "ncurses"
>> LICENSE = "GPL"
>>
>> SRC_URI = "
>> https://alioth.debian.org/frs/download.php/3195/minicom-${PV}.tar.gz<https://alioth.debian.org/frs/download.php/3195/minicom-$%7BPV%7D.tar.gz>
>> "
>> S = "${WORKDIR}/minicom-${PV}"
>> PR = "r0"
>>
>> inherit autotools gettext
>>
>> do_configure() {
>> ./configure --host = arm
>> }
>>
>> do_install() {
>> autotools_do_install
>> }
>>
>> *********************************************************************************************************
>>
>> then bitbake -b recipes/minicom/minicom-mypkg_2.4.bb, I always get the
>> below messages:
>>
>>
>> ****************************************************************************************************************************************************************
>> NOTE: the following files were installed but not shipped in any package:
>> NOTE: /usr/local/share/man/man1/ascii-xfr.1
>> NOTE: /usr/local/share/man/man1/minicom.1
>> NOTE: /usr/local/share/man/man1/xminicom.1
>> NOTE: /usr/local/share/man/man1/runscript.1
>> ... ignored
>> NOTE: /usr/local/bin/xminicom
>> NOTE: /usr/local/bin/ascii-xfr
>> NOTE: /usr/local/bin/minicom
>> NOTE: /usr/local/bin/runscript
>> NOTE: /usr/local/bin/.debug/ascii-xfr
>> NOTE: /usr/local/bin/.debug/minicom
>> NOTE: /usr/local/bin/.debug/runscript
>> NOTE: Running task 12 of 17 (ID: 10, /home/rd/oe/build/recipes/minicom/
>> minicom-mypkg_2.4.bb, do_qa_staging)
>> NOTE: Running task 13 of 17 (ID: 16, /home/rd/oe/build/recipes/minicom/
>> minicom-mypkg_2.4.bb, do_package_write_ipk)
>> Packaged contents of minicom-mypkg-dbg into
>> /home/rd/oe/build/tmp/deploy/glibc/ipk/armv5te/minicom-mypkg-dbg_2.4-r0.5_armv5te.ipk
>> NOTE: Not creating empty archive for minicom-mypkg-2.4-r0.5
>> NOTE: Not creating empty archive for minicom-mypkg-doc-2.4-r0.5
>> Packaged contents of minicom-mypkg-dev into
>> /home/rd/oe/build/tmp/deploy/glibc/ipk/armv5te/minicom-mypkg-dev_2.4-r0.5_armv5te.ipk
>> NOTE: Not creating empty archive for minicom-mypkg-static-2.4-r0.5
>> NOTE: Not creating empty archive for minicom-mypkg-locale-2.4-r0.5
>> ...ignored
>>
>> ****************************************************************************************************************************************************************
>>
>> I have no idea why I always get these messages...
>> NOTE: Not creating empty archive for minicom-mypkg-2.4-r0.5
>> NOTE: Not creating empty archive for minicom-mypkg-doc-2.4-r0.5
>> NOTE: Not creating empty archive for minicom-mypkg-static-2.4-r0.5
>> NOTE: Not creating empty archive for minicom-mypkg-locale-2.4-r0.5
>>
>> any information is appreciate !!
Your do_configure is broken, so it installs to /usr/local, which isn't
in FILES_${PN} by default.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL4l3PMkyGM64RGpERAgXFAJ9SB4Y461x3GkXdk+H+Zh23fqezVgCdEENx
N3D1GipD8aYuXF+jkrNhWQs=
=O0I2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-05-06 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6069.1273115899.24517.openembedded-devel@lists.openembedded.org>
[not found] ` <p2lad875cab1005052017k622928e3jabfe4ea684e4ef62@mail.gmail.com>
2010-05-06 3:19 ` create ipk failed yenchengwang
2010-05-06 6:12 ` Koen Kooi [this message]
2010-05-06 6:15 ` Denys Dmytriyenko
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='hrtmkf$bp1$2@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.