On 06/22/2010 06:00 PM, saleh usman wrote:
I've bitbake ossie-gpp-node recipe alone. It is showing some massages while
doing packaging during this build. Plz give me some direction if you may
understand something from these messages.Terminal log is shown below.
Saleh
[sa...@localhost ~]$ bitbake -b
sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 1 of 17 (ID: 6,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_setscene)
staging-ossie-gpp-node-armv5te-angstrom-linux-gnueabi - svn-r1
Removing package staging-ossie-gpp-node-armv5te-angstrom-linux-gnueabi from
root...
NOTE: Running task 2 of 17 (ID: 5,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_fetch)
NOTE: Running task 3 of 17 (ID: 0,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_unpack)
NOTE: Unpacking /sdr/ossie_collection/packages/ossie-nodes/default_GPP_node to
/sdr/build/tmp/work/armv5te-angstrom-linux-gnueabi/ossie-gpp-node-1.0-r1/
NOTE: Running task 4 of 17 (ID: 1,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_patch)
NOTE: Running task 5 of 17 (ID: 7,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_configure)
NOTE: Running task 6 of 17 (ID: 8,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_qa_configure)
NOTE: Running task 7 of 17 (ID: 9,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_compile)
NOTE: Running task 8 of 17 (ID: 2,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_install)
NOTE: Running task 9 of 17 (ID: 12,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_package)
NOTE: the following files were installed but not shipped in any package:
NOTE: /sdr/nodes/default_GPP_node/DeviceManager.scd.xml
NOTE: /sdr/nodes/default_GPP_node/DeviceManager.spd.xml
NOTE: /sdr/nodes/default_GPP_node/DeviceManager.dcd.xml
NOTE: /sdr/nodes/default_GPP_node/DeviceManager.prf.xml
/sdr nodes changed to /sdr/dom/nodes. Make a local copy of the default
GPP node files, change the recipe to use a local set of filles
(SRC_URI="file:///path/to/file") (three ///'s are important). Edit the
paths to match the work gpp-sound node.
Hopefully this helps. My wifi is spotty atm and will get really bad next
week.
Philip
NOTE: Running task 10 of 17 (ID: 3,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb,
do_populate_staging)
NOTE: Running task 11 of 17 (ID: 16,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb,
do_package_write_ipk)
Packaged contents of ossie-gpp-node-dbg into
/sdr/build/tmp/deploy/glibc/ipk/armv5te/ossie-gpp-node-dbg_1.0-r1.5_armv5te.ipk
NOTE: Not creating empty archive for ossie-gpp-node-1.0-r1.5
NOTE: Not creating empty archive for ossie-gpp-node-doc-1.0-r1.5
Packaged contents of ossie-gpp-node-dev into
/sdr/build/tmp/deploy/glibc/ipk/armv5te/ossie-gpp-node-dev_1.0-r1.5_armv5te.ipk
NOTE: Not creating empty archive for ossie-gpp-node-static-1.0-r1.5
NOTE: Not creating empty archive for ossie-gpp-node-locale-1.0-r1.5
NOTE: Running task 12 of 17 (ID: 11,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_package_write)
NOTE: Running task 13 of 17 (ID: 15,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_package_stage)
/sdr/build/tmp/work/armv5te-angstrom-linux-gnueabi/ossie-gpp-node-1.0-r1/staging-pkg/deploy/glibc/ipk/armv5te/
/sdr/build/tmp/work/armv5te-angstrom-linux-gnueabi/ossie-gpp-node-1.0-r1/staging-pkg/deploy/glibc/ipk/armv5te/
NOTE: Running task 14 of 17 (ID: 14,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb,
do_package_stage_all)
NOTE: Running task 15 of 17 (ID: 13,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb,
do_distribute_sources)
NOTE: Running task 16 of 17 (ID: 10,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_qa_staging)
NOTE: Running task 17 of 17 (ID: 4,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node.bb, do_build)
NOTE: Tasks Summary: Attempted 17 tasks of which 0 didn't need to be rerun and
0 failed.
Hi
Philipe
I am stuck there. Plz tell me at least how to control the ipkg packaging for
ossie-gpp-node. Because the main issue is with this.
Saleh
Philipe
Please give me some direction to solve this problem?
Saleh
Actually what I did , I copied the directory of ossie-gpp-node from vmware
image which contains source code. Then I edited bitbake recipe to use this
source code which is attached in which I changed SRC_URI and S variables. Now
when I bitbake ossie-gpp-node, it is built successfully but during butbake of
console-image its ipkg package is not installed in file system due to reasons
which we have already discussed.
Now if you are buzzy , plz give me guidelines so that I may solve this problem
by myself.
Saleh
On 06/15/2010 08:49 AM, saleh usman wrote:
Hi
Philipe
Did you look at log files? any suggestion to solve the problem?
I'm locked in another crisis at the moment. My concern is I never
updated the GPP node to work with the same paths in /sdr as I did for
the gpp sound node. It is a nuisance to look at the gpp node source
because it is in the ossie repo in a deleted branch so I have to
remember how to view it in trac.
Sorry,
Philip
Saleh
I've looked the recipes of ossie-gpp-sound-node and ossie-gpp-node. There is an
additional variable
BROKEN = "1"
in recipe of ossie-gpp-node.
Saleh
On 06/13/2010 09:49 AM, saleh usman wrote:
I've already tried it. That builds successfully as shown below but
console-image fails.
Problem which I've understood is that bitbake ossie-gpp-node actually creates
ipk packages
ossie-gpp-node-dbg
ossie-gpp-node-dev
But it doesn't not creat ipk package of ossie-gpp-node
This is clear from attached files.
How this issue may be fixed.
The ossie-gpp-node ipk should have the dcd file in it I think. Can you
post a log from a build of ossie-gpp-node? Look a that recipe and a
working node recipe ...
Philip
Saleh
[sa...@localhost ~]$ bitbake ossie-gpp-node
NOTE: Handling BitBake files: \ (8169/8169) [100 %]
NOTE: Parsing finished. 7530 cached, 309 parsed, 330 skipped, 0 masked.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Tasks Summary: Attempted 630 tasks of which 630 didn't need to be rerun
and 0 failed.
[sa...@localhost ~]$ bitbake ossie-demo
NOTE: Handling BitBake files: \ (8169/8169) [100 %]
NOTE: Parsing finished. 7530 cached, 309 parsed, 330 skipped, 0 masked.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Tasks Summary: Attempted 695 tasks of which 695 didn't need to be rerun
and 0 failed.
On 06/13/2010 08:10 AM, saleh usman wrote:
OpenEmbedded is giving an error of not building root files system due to
missing dependency of gpp_node
for ossie_demo as shown in attached log file.
When I bitbake ossie-demo and ossie-gpp-node seperately these are built
successfully. Error occurs when
I run bitbake console-image.
where might be the problem ? Plz help me to diagnose this error.
try bitbake ossie-gpp-node, then bitbake console-image. You need to
study how OE works.
You are currently the most knowledgeable person working on OSSIE for
embedded systems at the moment :)
Philip
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
https://signup.live.com/signup.aspx?id=60969
Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now.
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
https://signup.live.com/signup.aspx?id=60969
Hotmail: Free, trusted and rich email service. Get it now.
Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now.
Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now.
Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now.
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
