[yocto] Problem about print in fetching

[caterwaul]

Hi,


I want to print out all the URI_SRC I use during the build.  And I have tried 3 
methods in 2 places as follow. But all of these can not print out the src path. 
Did I make some mistakes? Could anyone help me on this? Thank you.


PLACE ONE  in poky-edison-6.0.1/bitbake/lib/bb/fetch2/__init__.py
class Fetch(object):
def __init__(self, urls, d, cache = True):
..
for url in urls:
if url not in self.ud:
print('%s' % url) # code I added
self.ud[url] = FetchData(url, d)
..


PLACE TWO  in poky-edison-6.0.1/meta/classes/base.bbclass
python base_do_fetch() {


src_uri = (bb.data.getVar('SRC_URI', d, True) or "").split()
if len(src_uri) == 0:
return
print('%s' % src_url) # code I added
bb.note('%s' % src_url) # code I added
}


Jim Green___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Porting of specific Kernel/Driver into yocto.

[Om Prakash PAL]

Hi Bruce,
Thanks for your reply.
I am totally new to Yocto.
I have gone through the section BSP/Linux kernel configuration and if I am not 
wrong then it explains how can we configure the kernel, not the how we can 
add/replace a  component(driver etc). 
lets take the example of UART driver, I want to add my own UART driver code.
Should I write a separate recipe file (.bb) for UART Driver?.
if yes then I have to write the recipe files for all my drivers that will be 
very time consuming. 
Is there any other way that I can port all my desired drivers into Yocto 
kernel?.
Please help me.
Thanks a lot in advance. 

Best Regards,
Om Prakash Pal  

From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Wednesday, April 04, 2012 6:17 PM
To: Om Prakash PAL
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 12-04-04 04:46 AM, Om Prakash PAL wrote:
> Hi,
> I want to build my local kernel/Driver code, not the default one.
> please help how can i do it ?.
> any wiki/docs on this?.

The BSP developer guides show how to extend the yocto kernels, and
also have sections on custom/different kernel versions. Have you
seen that doc yet ? Or have you seen it, and have specific questions ?

Bruce

>
> Best Regards,
> Om Prakash Pal
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Problem about print in fetching

[caterwaul]

Hi,


I want to print out all the URI_SRC I use during the build.  And I have tried 3 
methods in 2 places as follow. But all of these can not print out the src path. 
Did I make some mistakes? Could anyone help me on this? Thank you.


PLACE ONE  in poky-edison-6.0.1/bitbake/lib/bb/fetch2/__init__.py
class Fetch(object):
def __init__(self, urls, d, cache = True):
..
for url in urls:
if url not in self.ud:
print('%s' % url) # code I added
self.ud[url] = FetchData(url, d)
..


PLACE TWO  in poky-edison-6.0.1/meta/classes/base.bbclass
python base_do_fetch() {


src_uri = (bb.data.getVar('SRC_URI', d, True) or "").split()
if len(src_uri) == 0:
return
print('%s' % src_url) # code I added
bb.note('%s' % src_url) # code I added
}


Jim Green


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Problem about print in fetching

[Chris Larson]

2012/4/8 caterwaul :
> I want to print out all the URI_SRC I use during the build.  And I have
> tried 3 methods in 2 places as follow. But all of these can not print out
> the src path. Did I make some mistakes? Could anyone help me on this? Thank
> you.
>
> PLACE ONE  in poky-edison-6.0.1/bitbake/lib/bb/fetch2/__init__.py
> class Fetch(object):
>     def __init__(self, urls, d, cache = True):
> ..
>         for url in urls:
>             if url not in self.ud:
>                 print('%s' % url) # code I added
>                 self.ud[url] = FetchData(url, d)
> ..
>
> PLACE TWO  in poky-edison-6.0.1/meta/classes/base.bbclass
> python base_do_fetch() {
>
> src_uri = (bb.data.getVar('SRC_URI', d, True) or "").split()
> if len(src_uri) == 0:
> return
>         print('%s' % src_url) # code I added
>         bb.note('%s' % src_url) # code I added
> }

Both of these will result in messages going to the log file for the
task, but not the console output. By default, bitbake only shows
warnings, errors, and critical messages to the console / bitbake's UI.
Use bb.warn() or bb.error() for printf-style debugging.
-- 
Christopher Larson
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] build the adt error

[shushm]

When I use the bitbake meta-toolchain-sdk,it comes the error: Failed 
dependencies:

| libcurl.so.4 is needed by qemu-nativesdk-0.15.1-r4.i686.
PS:I have checked the libcurl.so.4 in /usr/lib/i386-linux-gnu.
How can I fix it? Thank you~

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] managing layer priorities

[Tomas Frydrych]

Hi,

Is there a way to change the priority that a layer assigns itself in its
layer.conf? E.g., I want to add meta-oe alongside of meta-yocto, but I
want it to have a lower priority than the latter. Currently meta-yocto
gives itself "5" and meta-oe "6", I'd like to change this without having
to modify meta-oe/conf/layer.conf, but can't find a way to do this.

Tomas
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Porting of specific Kernel/Driver into yocto.

[Bruce Ashfield]

On 12-04-08 10:04 AM, Om Prakash PAL wrote:

Hi Bruce,
Thanks for your reply.
I am totally new to Yocto.
I have gone through the section BSP/Linux kernel configuration and if I am not 
wrong then it explains how can we configure the kernel, not the how we can 
add/replace a  component(driver etc).
lets take the example of UART driver, I want to add my own UART driver code.
Should I write a separate recipe file (.bb) for UART Driver?.
if yes then I have to write the recipe files for all my drivers that will be 
very time consuming.
Is there any other way that I can port all my desired drivers into Yocto 
kernel?.


No recipes are required per-driver, unless you are building them all
as out of tree modules.

The typical way this is done is to simply work in the extracted linux
src tree (build/tmp/work//linux-yocto-/linux), manually
patch, or copy your drivers into the tree. At this point, you'll port
the drivers, doing test builds (bitbake -f -c compile linux-yocto) to
ensure that your port is working. When you've completed the build phase,
boot tests would be in order. (Do not do a 'clean' or you'll lose in
progress changes).

When you are happy with the changes, the directory where you were working
is with the kernel git repository. So you can simply commit your 
changes, and generate patches.


   git format-patch -o  HEAD^ (or however many commits
you have)

Take those patches, create a layer with a bbappend and add them like
any other patch to any package. They'll be applied to subsequent builds
of the kernel.

I'm skipping a lot of detail there, but it is all found in the various
manuals, and I don't want to repeat it here.

Cheers,

Bruce


Please help me.
Thanks a lot in advance.

Best Regards,
Om Prakash Pal

From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Wednesday, April 04, 2012 6:17 PM
To: Om Prakash PAL
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 12-04-04 04:46 AM, Om Prakash PAL wrote:

Hi,
I want to build my local kernel/Driver code, not the default one.
please help how can i do it ?.
any wiki/docs on this?.


The BSP developer guides show how to extend the yocto kernels, and
also have sections on custom/different kernel versions. Have you
seen that doc yet ? Or have you seen it, and have specific questions ?

Bruce



Best Regards,
Om Prakash Pal
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto




___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Yocto] Build Failure in beecrypt-4.2.1-r1 package with poky-1.2_M4.rc2 on Open Suse 12.1

[Ashish Pandey]

Hi Khem Raj ,

  I tried woth " --disable-java" option but it is giving same error.
Please check once again and help me to build.

Regards,

Ashish

Huawei Technology



This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!


From: yocto-boun...@yoctoproject.org [yocto-boun...@yoctoproject.org] on behalf 
of Khem Raj [raj.k...@gmail.com]
Sent: 07 April 2012 12:32:53
To: yocto@yoctoproject.org
Subject: Re: [yocto] [Yocto] Build Failure in beecrypt-4.2.1-r1 package with 
poky-1.2_M4.rc2 on Open Suse 12.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 04/06/2012 06:12 AM, Ashish Pandey wrote:
> Hi All ,
>
> I was trying to build "poky-1.2_M4.rc2" with "bitbake
> core-image-lsb-sdk" option.
>
> I have got build error in the beecrypt-4.2.1-r1 Package. My build
> machine is Open Suse 12.1 and following is the configuration.
>
> yocto@linux-461v:~/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean>
> uname -a Linux linux-461v 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov
> 3 14:45:45 UTC 2011 (187dde0) i686 i686 i386 GNU/Linux
>
> Please verify this error , Is this a problem with build machine or
> there is some problem with new release. Kindly let me know if there
> is any data missed here. Please confirm the issue.
>
>
>
> Error Log :
>
>
> NOTE: Running task 3811 of 5184 (ID: 1614,
> /home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/meta/recipes-support/beecrypt/beecrypt_4.2.1.bb,
> do_compile) NOTE: package beecrypt-4.2.1-r1: task do_compile:
> Started ERROR: Function failed: do_compile (see
> /home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/work/i586-poky-linux/beecrypt-4.2.1-r1/temp/log.do_compile.27618
> for further information) ERROR: Logfile of failure stored in:
> /home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/work/i586-poky-linux/beecrypt-4.2.1-r1/temp/log.do_compile.27618
>
>
Log data follows:
> | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common',
> 'common-linux', 'common-glibc', 'i586-linux', 'common'] | NOTE:
> make -j 6 | make  all-recursive | make[1]: Entering directory
> `/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/work/i586-poky-linux/beecrypt-4.2.1-r1/beecrypt-4.2.1'
>
>
| Making all in .
> | make[2]: Entering directory
> `/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/work/i586-poky-linux/beecrypt-4.2.1-r1/beecrypt-4.2.1'
>
>
| ./i586-poky-linux-libtool --tag=CC   --mode=compile
i586-poky-linux-gcc  -m32   -march=i586
-
--sysroot=/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/sysroots/qemux86
- -DHAVE_CONFIG_H -I. -I./include-O2 -pipe -g
- -feliminate-unused-debug-types -Wa,--noexecstack -c -o aes.lo aes.c
> | ./i586-poky-linux-libtool --tag=CC   --mode=compile
> i586-poky-linux-gcc  -m32   -march=i586
> --sysroot=/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/sysroots/qemux86
> -DHAVE_CONFIG_H -I. -I./include-O2 -pipe -g
> -feliminate-unused-debug-types -Wa,--noexecstack -c -o base64.lo
> base64.c | ./i586-poky-linux-libtool --tag=CC   --mode=compile
> i586-poky-linux-gcc  -m32   -march=i586
> --sysroot=/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/sysroots/qemux86
> -DHAVE_CONFIG_H -I. -I./include-O2 -pipe -g
> -feliminate-unused-debug-types -Wa,--noexecstack -c -o beecrypt.lo
> beecrypt.c | ./i586-poky-linux-libtool --tag=CC   --mode=compile
> i586-poky-linux-gcc  -m32   -march=i586
> --sysroot=/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/sysroots/qemux86
> -DHAVE_CONFIG_H -I. -I./include-O2 -pipe -g
> -feliminate-unused-debug-types -Wa,--noexecstack -c -o blockmode.lo
> blockmode.c | ./i586-poky-linux-libtool --tag=CC   --mode=compile
> i586-poky-linux-gcc  -m32   -march=i586
> --sysroot=/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/sysroots/qemux86
> -DHAVE_CONFIG_H -I. -I./include-O2 -pipe -g
> -feliminate-unused-debug-types -Wa,--noexecstack -c -o blockpad.lo
> blockpad.c | ./i586-poky-linux-libtool --tag=CC   --mode=compile
> i586-poky-linux-gcc  -m32   -march=i586
> --sysroot=/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/sysroots/qemux86
> -DHAVE_CONFIG_H -I. -I./include-O2 -pipe -g
> -feliminate-unused-debug-types -Wa,--noexecstack -c -o blowfish.lo
> blowfish.c | i586-poky-linux-libtool: compile:  i586-poky-linux-gcc
> -m32 -march=i586
> --sysroot=/home/yocto/Yocto-builds-test/poky-1.2_M4.rc2/lsb-sdk-clean/tmp/sysroots/qemux86
> -DHAVE_CONFIG_H -I. -I./include -O2 -pipe -g
> -feliminate-unused-debug-types -Wa,--noexecstack -c

Re: [yocto] [Yocto] Build Failure in beecrypt-4.2.1-r1 package with poky-1.2_M4.rc2 on Open Suse 12.1

[Khem Raj]

On Sun, Apr 8, 2012 at 9:07 PM, Ashish Pandey  wrote:
>
>  I tried woth " --disable-java" option but it is giving same error.
> Please check once again and help me to build.

post your configure logs somewhere disabling java should have disabled
any JNI detection
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Eclipse-ADT-build-error (Lu, Lianhao)

[Zhang, Jessica]

Hi Andy,



I've made some changes in the eclipse plug-in code that can be more robust for 
handling user cross development settings that should be included in for 1.1.2 
and 1.2 releases.  But in the mean time to solve your issue, instead of 
pointing your sysroot to "/opt/poky/1.1.1/sysroots" please go one level down to 
"/opt/poky/1.1.1/sysroots/armv5te-poky-linux-gnueabi" this should resolve your 
issue for using the ADT 1.1.1 plugin for cross compilation.



Thanks,

Jessica



From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Andy Gikling
Sent: Thursday, April 05, 2012 8:31 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] Eclipse-ADT-build-error (Lu, Lianhao)



Lianhao,



I've looked into this more deeply and I'm pretty sure I've followed the 
directions in the ADT manual correctly as I've gotten this to work before in  
ADT v1.1.  I'm having the same problem Lu seems to be having.  To answer your 
questions:



1. Host OS? - Ubuntu 11.10 - 32bit VM

2. Which version of eclipse?  3.7.2

3. Which version of Yocto eclipse plugin? 1.2.0.2x - I just tried to get it as 
per the manual but the link on the ADT manual for the plugin is broken.  I was 
able to use the update feature from within Ecplise - this brought me from 1.1 
to 1.2.0.2x

4. Which image do you use as sysroot? core-image-sato or core-image-sato-sdk? - 
Core-image-minimal

5. Which version of metadata do you use to build the image? Sugarbay - is that 
what you're looking for?

6. How do you install the toolchain? Using adt-installer or extracting 
meta-toolchain tarball? If using meta-toolchain tarball, which version do you 
use? - used the premade tarball from: 
http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/toolchain/i686/poky-eglibc-i686-arm-toolchain-gmae-1.1.1.tar.bz2
  - once extracted, in Ecplise, I point at /opt/poky/1.1.1 for my Toolchain 
Root and /opt/poky/1.1.1/sysroots/ for my Sysroot Location.



Following the ADT manual closely, I've sourced the ADT env vars with $source 
/opt/poky/1.1.1/environment-setup-x86_64-poky-linux



Now, I've opened a new C Hello World template project and use Project -> 
Reconfigure Project.  Unfortunately this fails.  The console reads "> 
configure: error: C compiler cannot create executables" as Lu has seen.  All 
the other Eclipse requirements from the ADT manual have been installed as well.



The config.log shows this snippet as the culprit:

...

Thread model: posix

gcc version 4.6.1 20110627 (prerelease) (GCC)

configure:2413: $? = 0

configure:2402: x86_64-poky-linux-g++ -V >&5

x86_64-poky-linux-g++: error: unrecognized option '-V'

x86_64-poky-linux-g++: fatal error: no input files

compilation terminated.

configure:2413: $? = 1

configure:2402: x86_64-poky-linux-g++ -qversion >&5

x86_64-poky-linux-g++: error: unrecognized option '-qversion'

x86_64-poky-linux-g++: fatal error: no input files

compilation terminated.

configure:2413: $? = 1

configure:2433: checking whether the C++ compiler works

...



So interestingly, I went ahead and tried to run autogen.sh directly from the 
terminal with "sh autogen.sh" and this also gives me the same error: 
"configure: error: C compiler cannot create executables"



However, when I run this with sudo in the terminal it works.  I can then call 
"sudo ./configure" from the terminal and that also works.  Now I have a 
Makefile in my src directory as expected.  Unfortunately, this project still 
doesn't build in Eclipse.  I keep getting "no rule for make target 'all' "



I've done all of the above again, fresh, after calling "chmod -R 777 
/home/userName/workspace" so it might not be a permissions problem.



I've run through these ADT steps in the 1.1 version of the ADT manual without 
any problems.  What changed?  Do I submit a bug?



Regards,



~Andy Gikling

LasX Industries Inc.

agikl...@lasx.com











___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] managing layer priorities

[Tomas Frydrych]

On 08/04/12 23:28, Tomas Frydrych wrote:
> Is there a way to change the priority that a layer assigns itself in its
> layer.conf? E.g., I want to add meta-oe alongside of meta-yocto, but I
> want it to have a lower priority than the latter. Currently meta-yocto
> gives itself "5" and meta-oe "6", I'd like to change this without having
> to modify meta-oe/conf/layer.conf, but can't find a way to do this.

Never mind, it is possible to override these in the last layer listed in
BBLAYERS.

Tomas

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto