On 03/28/2010 08:03 AM, saleh usman wrote:
I'm proceeding now by manually changing AC_CHECK_LIB([boost_filesystem],
[main], [], [AC_MSG_ERROR([cannot find boost_filesystem library.])]).
Two things: Do not build ossie-image. Follow the instructions from the
article at:
http://www.opensdr.com/node/7
and second, "svn up" the ossie_collection. I had the wrong version
ossie-sca in the version file.
Philip
Now there is an issue that OE is unable to fetch source code of ossie-gpp-node.
Terminal log follows
[sa...@localhost ~]$ bitbake ossie-image
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: Running task 1956 of 3538 (ID: 1683,
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node_svn.bb, do_fetch)
NOTE: fetch
http://www.angstrom-distribution.org/unstable/sources/default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz
--16:14:12--
http://www.angstrom-distribution.org/unstable/sources/default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz
=>
`/sdr/openembedded/sources/default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz'
Resolving www.angstrom-distribution.org... 188.40.83.200
Connecting to www.angstrom-distribution.org|188.40.83.200|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
16:14:14 ERROR 404: Not Found.
NOTE: fetch
http://mirrors.openembedded.org//default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz
--16:14:14--
http://mirrors.openembedded.org//default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz
=>
`/sdr/openembedded/sources/default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz'
Resolving mirrors.openembedded.org... 82.197.159.157
Connecting to mirrors.openembedded.org|82.197.159.157|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
16:14:15 ERROR 404: Not Found.
NOTE: fetch
http://sources.openembedded.org//default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz
--16:14:15--
http://sources.openembedded.org//default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz
=>
`/sdr/openembedded/sources/default_GPP_node_ossie.wireless.vt.edu_.repos.ossie.nodes.default_GPP_node.trunk_375_.tar.gz'
Resolving sources.openembedded.org... 140.211.169.165
Connecting to sources.openembedded.org|140.211.169.165|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
16:14:16 ERROR 404: Not Found.
NOTE: Fetch
svn://ossie.wireless.vt.edu/repos/ossie/nodes/default_GPP_node/trunk;module=default_GPP_node;proto=https
Error validating server certificate for 'https://ossie.wireless.vt.edu:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
- The certificate has expired.
Certificate information:
- Hostname: ossie.wireless.vt.edu
- Valid: from Feb 15 23:23:26 2009 GMT until Feb 15 23:23:26 2010 GMT
- Issuer: OSSIE, MPRG, Blacksburg, Virginia, US
- Fingerprint: 68:e6:b4:cd:f1:c4:32:22:65:a5:71:87:92:ec:01:b1:de:a7:82:5e
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: PROPFIND request
failed on '/repos/ossie/nodes/default_GPP_node/trunk/default_GPP_node'
svn: PROPFIND of '/repos/ossie/nodes/default_GPP_node/trunk/default_GPP_node':
Server certificate verification failed: certificate has expired, issuer is not
trusted (https://ossie.wireless.vt.edu)
NOTE: Task failed: Fetch failed: Fetch command export HOME=/home/Saleh; export
SSH_AUTH_SOCK=/tmp/ssh-sTTasw2572/agent.2572; export
PATH=/sdr/build/tmp/staging/i686-linux/usr/bin/armv5te-angstrom-linux-gnueabi:/sdr/build/tmp/staging/i686-linux/usr/bin/armv5te-angstrom-linux-gnueabi:/sdr/build/tmp/staging/i686-linux/usr/sbin:/sdr/build/tmp/staging/i686-linux/usr/bin:/sdr/build/tmp/cross/armv5te//bin:/sdr/build/tmp/staging/i686-linux/sbin:/sdr/build/tmp/staging/i686-linux/bin:/sdr/bitbake/bin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/Saleh/bin;
/usr/bin/env svn co -r 375
https://ossie.wireless.vt.edu/repos/ossie/nodes/default_GPP_node/trunk/default_gpp_n...@375
default_GPP_node failed with signal 1, output:
Error validating server certificate for 'https://ossie.wireless.vt.edu:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
- The certificate has expired.
Certificate information:
- Hostname: ossie.wireless.vt.edu
- Valid: from Feb 15 23:23:26 2009 GMT until Feb 15 23:23:26 2010 GMT
- Issuer: OSSIE, MPRG, Blacksburg, Virginia, US
- Fingerprint: 68:e6:b4:cd:f1:c4:32:22:65:a5:71:87:92:ec:01:b1:de:a7:82:5e
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: PROPFIND request
failed on '/repos/ossie/nodes/default_GPP_node/trunk/default_GPP_node'
svn: PROPFIND of '/repos/ossie/nodes/default_GPP_node/trunk/default_GPP_node':
Server certificate verification failed: certificate has expired, issuer is not
trusted (https://ossie.wireless.vt.edu)
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node_svn.bb do_fetch failed
ERROR: Task 1683
(/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node_svn.bb, do_fetch)
failed
NOTE: Tasks Summary: Attempted 1955 tasks of which 1955 didn't need to be rerun
and 1 failed.
ERROR: '/sdr/ossie_collection/packages/ossie-nodes/ossie-gpp-node_svn.bb' failed
Saleh
Subject: Re: Boost library issue
To: [email protected]
From: [email protected]
Date: Sat, 27 Mar 2010 14:28:56 +0000
Take a look at the trac site http://trac.geekisp.com/opensdr to see what is
actually committed and make sure it matches what you have. I'll double check
later tonight when I get home.
Philip
From: saleh usman<[email protected]>
Date: Sat, 27 Mar 2010 19:18:59 +0500To: OSSIE Embedded
Discussion<[email protected]>Subject: RE: Boost library issue
AC_CHECK_LIB([boost_filesystem-mt], [main], [], [AC_MSG_ERROR([cannot find
boost_filesystem library.])])
That line was in release 1 which I was changed manually but in release 2 that
line has not been still changed. while I've updated ossie collection.
Saleh
From: [email protected]
To: [email protected]
Subject: RE: Boost library issue
Date: Sat, 27 Mar 2010 19:03:47 +0500
I've updated both ossie_colletoin and openembedded by svn up and git pull but
again I am getting the same error.Now configure.ac line has also been changed to
I've also removed DEFAULT_PREFERENCE=-1 from boos_1.37.0.bb recipe.
Now where might be the problem.
Saleh
Date: Thu, 25 Mar 2010 10:15:53 -0400
From: [email protected]
To: [email protected]
Subject: Re: Boost library issue
On 03/25/2010 10:09 AM, saleh usman wrote:
"svn up" in ossie_collection again.
I did this but that error is there.When I do svn up in ossie_collectoin it
responds
[sa...@localhost ossie_collection]$ svn up
Skipped '.'
Is it updated properly while this skipped appears.
This suggests you do not have write permissions in the directory you are
trying to update. Don't ever do anything while logged in as root.
I changed the configure script back
to looking for libboost_filesystem-mt again. This should work in OE for
both dm6446 and beagleboard machines. (I looked to see what is in
staging). This should also work on desktop distros, since the ones I
checked use the softlink to the library name without the -mt.
I am checking for dm6446 and beagleboard now, but it will be tomorrow
before I know it works for both machines.
To make sure you have the right files, look in tmp/work/... for the
ossie-cf source and read the configure.ac file. There should be a line
with AC_CHECK_LIB and libboost_filesystem-mt in it. (Those strings are
only approximiate)
I've checked configure.ac file and
AC_CHECK_LIB([boost_filesystem], [main], [], [AC_MSG_ERROR([cannot find
boost_filesystem library.])])
line is present there.
When get teh correct checkout of ossie_collection and build ossie-cf,
that line will change to:
AC_CHECK_LIB([boost_filesystem-mt], [main], [], [AC_MSG_ERROR([cannot
find boost_filesystem library.])])
You are really close.
Philip
I really need to put all this in a git repo to make it easier for others
to work on. Subversion has become very limiting.
Philip
Date: Wed, 24 Mar 2010 11:46:20 -0400
From: [email protected]
To: [email protected]
Subject: Re: Boost library issue
On 03/24/2010 11:44 AM, saleh usman wrote:
I checked cd ossie_collection and svn up but that didn't worked.It is showing
same error.
Attched is configure.log file.
I mean config.log from tmp/work/armv5.../ossie...
I'm going to see if I can reproduce the problem locally. I will be slow
fixing it since I have some other pressing work atm.
Philip
Saleh
Date: Wed, 24 Mar 2010 11:29:25 -0400
From: [email protected]
To: [email protected]
Subject: Re: Boost library issue
On 03/24/2010 11:21 AM, saleh usman wrote:
Now again when openembedded reached at boost library configuration, bitbake
failed and it is showing the same old error as with boost version 1.36.
The root problem is OE needs to stage boost libs and make sure a soft
link exists to the non -mt name ....
I did a really quick hack to the ossie_collection to try and get you
past this.
cd ossie_collection and svn up
If this does not work send the config.log file so i can look at it closer.
Philip
Saleh
Terminal log follows
NOTE: Running task 1649 of 3551 (ID: 1159,
/sdr/ossie_collection/recipes/ossie-libraries/ossie-cf_svn.bb, do_configure)
ERROR: function do_configure failed
ERROR: log data follows
(/sdr/build/tmp/work/armv5te-angstrom-linux-gnueabi/ossie-cf-0.0.0+svnr247-r1/temp/log.do_configure.26954)
| automake (GNU automake) 1.10.2
| Copyright (C) 2008 Free Software Foundation, Inc.
| License GPLv2+: GNU GPL version 2 or later<http://gnu.org/licenses/gpl.html>
| This is free software: you are free to change and redistribute it.
| There is NO WARRANTY, to the extent permitted by law.
|
| Written by Tom Tromey<[email protected]>
| and Alexandre Duret-Lutz<[email protected]>.
| AUTOV is 1.10
| NOTE: Executing autoreconf --verbose --install --force --exclude=autopoint
-I/sdr/build/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/share/aclocal-1.10
-I /sdr/build/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/share/aclocal
| autoreconf: Entering directory `.'
| autoreconf: configure.ac: not using Gettext
| autoreconf: running: aclocal -I
/sdr/build/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/share/aclocal-1.10 -I
/sdr/build/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/share/aclocal --force
| autoreconf: configure.ac: tracing
| autoreconf: running: libtoolize --copy --force
| libtoolize: putting auxiliary files in `.'.
| libtoolize: copying file `./ltmain.sh'
| libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
| libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
| libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
| autoreconf: running: /sdr/build/tmp/staging/i686-linux/usr/bin/autoconf
--include=/sdr/build/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/share/aclocal-1.10
--include=/sdr/build/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/share/aclocal
--force --warnings=cross
| autoreconf: configure.ac: not using Autoheader
| autoreconf: running: automake --foreign --add-missing --copy --force-missing
--warnings=cross
| automake: unknown warning category `cross'
| configure.ac:9: installing `./config.guess'
| configure.ac:9: installing `./config.sub'
| configure.ac:4: installing `./install-sh'
| configure.ac:4: installing `./missing'
| framework/Makefile.am: installing `./depcomp'
| autoreconf: running: gnu-configize
| autoreconf: Leaving directory `.'
| NOTE: Running
/sdr/build/tmp/work/armv5te-angstrom-linux-gnueabi/ossie-cf-0.0.0+svnr247-r1/trunk/configure
--build=i686-linux
--host=arm-angstrom-linux-gnueabi
--target=arm-angstrom-linux-gnueabi --prefix=/usr
--exec_prefix=/usr --bindir=/usr/bin
--sbindir=/usr/sbin --libexecdir=/usr/libexec
--datadir=/usr/share --sysconfdir=/etc
--sharedstatedir=/com --localstatedir=/var
--libdir=/usr/lib --includedir=/usr/include
--oldincludedir=/usr/include --infodir=/usr/share/info
--mandir=/usr/share/man
--with-omniorb=/sdr/build/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/bin/..
IDL=/sdr/build/tmp/staging/i686-linux/usr/bin/omniidl ...
| configure: WARNING: unrecognized options: --with-omniorb
| configure: loading site script /sdr/openembedded/site/endian-little
| configure: loading site script /sdr/openembedded/site/common-linux
| configure: loading site script /sdr/openembedded/site/common-glibc
| configure: loading site script /sdr/openembedded/site/arm-common
| configure: loading site script /sdr/openembedded/site/arm-linux
| configure: loading site script /sdr/openembedded/site/common
| configure: loading site script /sdr/openembedded/site/common
| checking for a BSD-compatible install...
/sdr/build/tmp/staging/i686-linux/usr/bin/install -c
| checking whether build environment is sane... yes
| checking for a thread-safe mkdir -p...
/sdr/build/tmp/staging/i686-linux/usr/bin/mkdir -p
| checking for gawk... gawk
| checking whether make sets $(MAKE)... yes
| checking for arm-angstrom-linux-gnueabi-strip...
arm-angstrom-linux-gnueabi-strip
| checking for C++ compiler default output file name... a.out
| checking whether the C++ compiler works... yes
| checking whether we are cross compiling... yes
| checking for suffix of executables...
| checking for suffix of object files... o
| checking whether we are using the GNU C++ compiler... yes
| checking whether ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb accepts -g... yes
| checking for style of include used by make... GNU
| checking dependency style of ccache arm-angstrom-linux-gnueabi-g++
-march=armv5te -mtune=arm926ej-s -mthumb-interwork -mno-thumb... gcc3
| checking for a BSD-compatible install...
/sdr/build/tmp/staging/i686-linux/usr/bin/install -c
| checking whether make sets $(MAKE)... (cached) yes
| checking build system type... i686-pc-linux-gnu
| checking host system type... arm-angstrom-linux-gnueabi
| checking for arm-angstrom-linux-gnueabi-gcc... ccache
arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=arm926ej-s
-mthumb-interwork -mno-thumb
| checking whether we are using the GNU C compiler... yes
| checking whether ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb accepts -g... yes
| checking for ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb option to accept ISO C89... none
needed
| checking dependency style of ccache arm-angstrom-linux-gnueabi-gcc
-march=armv5te -mtune=arm926ej-s -mthumb-interwork -mno-thumb... gcc3
| checking for a sed that does not truncate output... /bin/sed
| checking for grep that handles long lines and -e... /bin/grep
| checking for egrep... /bin/grep -E
| checking for fgrep... /bin/grep -F
| checking for ld used by ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb... arm-angstrom-linux-gnueabi-ld
| checking if the linker (arm-angstrom-linux-gnueabi-ld) is GNU ld... yes
| checking for BSD- or MS-compatible name lister (nm)...
arm-angstrom-linux-gnueabi-nm
| checking the name lister (arm-angstrom-linux-gnueabi-nm) interface... BSD nm
| checking whether ln -s works... yes
| checking the maximum length of command line arguments... 98304
| checking whether the shell understands some XSI constructs... yes
| checking whether the shell understands "+="... yes
| checking for arm-angstrom-linux-gnueabi-ld option to reload object files... -r
| checking for arm-angstrom-linux-gnueabi-objdump...
arm-angstrom-linux-gnueabi-objdump
| checking how to recognize dependent libraries... pass_all
| checking for arm-angstrom-linux-gnueabi-ar... arm-angstrom-linux-gnueabi-ar
| checking for arm-angstrom-linux-gnueabi-strip... (cached)
arm-angstrom-linux-gnueabi-strip
| checking for arm-angstrom-linux-gnueabi-ranlib...
arm-angstrom-linux-gnueabi-ranlib
| checking command to parse arm-angstrom-linux-gnueabi-nm output from ccache
arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=arm926ej-s
-mthumb-interwork -mno-thumb object... ok
| checking how to run the C preprocessor... arm-angstrom-linux-gnueabi-gcc -E
| checking for ANSI C header files... yes
| checking for sys/types.h... yes
| checking for sys/stat.h... yes
| checking for stdlib.h... yes
| checking for string.h... yes
| checking for memory.h... yes
| checking for strings.h... yes
| checking for inttypes.h... yes
| checking for stdint.h... yes
| checking for unistd.h... yes
| checking for dlfcn.h... yes
| checking whether we are using the GNU C++ compiler... (cached) yes
| checking whether ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb accepts -g... (cached) yes
| checking dependency style of ccache arm-angstrom-linux-gnueabi-g++
-march=armv5te -mtune=arm926ej-s -mthumb-interwork -mno-thumb... (cached) gcc3
| checking how to run the C++ preprocessor... ccache
arm-angstrom-linux-gnueabi-g++ -march=armv5te -mtune=arm926ej-s
-mthumb-interwork -mno-thumb -E
| checking for objdir... .libs
| checking if ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb supports -fno-rtti
-fno-exceptions... no
| checking for ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb option to produce PIC... -fPIC
-DPIC
| checking if ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb PIC flag -fPIC -DPIC works... yes
| checking if ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb static flag -static works... yes
| checking if ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb supports -c -o file.o... yes
| checking if ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb supports -c -o file.o...
(cached) yes
| checking whether the ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb linker
(arm-angstrom-linux-gnueabi-ld) supports shared libraries... yes
| checking whether -lc should be explicitly linked in... no
| checking dynamic linker characteristics... GNU/Linux ld.so
| checking how to hardcode library paths into programs... immediate
| checking whether stripping libraries is possible... yes
| checking if libtool supports shared libraries... yes
| checking whether to build shared libraries... yes
| checking whether to build static libraries... yes
| checking for ld used by ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb... arm-angstrom-linux-gnueabi-ld
| checking if the linker (arm-angstrom-linux-gnueabi-ld) is GNU ld... yes
| checking whether the ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb linker
(arm-angstrom-linux-gnueabi-ld) supports shared libraries... yes
| checking for ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb option to produce PIC... -fPIC
-DPIC
| checking if ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb PIC flag -fPIC -DPIC works... yes
| checking if ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb static flag -static works... yes
| checking if ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb supports -c -o file.o... yes
| checking if ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb supports -c -o file.o...
(cached) yes
| checking whether the ccache arm-angstrom-linux-gnueabi-g++ -march=armv5te
-mtune=arm926ej-s -mthumb-interwork -mno-thumb linker
(arm-angstrom-linux-gnueabi-ld) supports shared libraries... yes
| checking dynamic linker characteristics... GNU/Linux ld.so
| checking how to hardcode library paths into programs... immediate
| checking for main in -lomniORB4... yes
| checking omniORB4/CORBA.h usability... yes
| checking omniORB4/CORBA.h presence... yes
| checking for omniORB4/CORBA.h... yes
| checking for omniidl... /sdr/build/tmp/staging/i686-linux/usr/bin/omniidl
| checking boost/filesystem/operations.hpp usability... yes
| checking boost/filesystem/operations.hpp presence... yes
| checking for boost/filesystem/operations.hpp... yes
| checking for main in -lboost_filesystem... no
| configure: error: cannot find boost_filesystem library.
| FATAL: oe_runconf failed
NOTE: Task failed:
/sdr/build/tmp/work/armv5te-angstrom-linux-gnueabi/ossie-cf-0.0.0+svnr247-r1/temp/log.do_configure.26954
ERROR: TaskFailed event exception, aborting
ERROR: Build of /sdr/ossie_collection/recipes/ossie-libraries/ossie-cf_svn.bb
do_configure failed
ERROR: Task 1159
(/sdr/ossie_collection/recipes/ossie-libraries/ossie-cf_svn.bb, do_configure)
failed
NOTE: Tasks Summary: Attempted 1648 tasks of which 1547 didn't need to be rerun
and 1 failed.
ERROR: '/sdr/ossie_collection/recipes/ossie-libraries/ossie-cf_svn.bb' failed
_________________________________________________________________
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 powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
https://signup.live.com/signup.aspx?id=60969
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
https://signup.live.com/signup.aspx?id=60969
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. 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
