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

[Cui, Dexuan]

Hi Andy,
If you're attending the ESDC contest, please try to build and setup ADT 
environment by yourself:
http://software.intel.com/en-us/forums/showthread.php?t=104267&o=a&s=lr

If you're not, just ignore my mail. :)

Thanks,
-- Dexuan

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Zhang, Jessica
Sent: Friday, April 06, 2012 1:52 PM
To: Andy Gikling; yocto@yoctoproject.org
Subject: Re: [yocto] Eclipse-ADT-build-error (Lu, Lianhao)

Hi Andy,

Please file a bug against 1.1.1, seems something is not quite right and we can 
use the bug to track the issue.

Thanks for reporting the issue.

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

[yocto] using and auditing kernel config fragments

[Tomas Frydrych]

Hi,

I am trying to add a kernel config fragment to the yocto 2.6.37 kernel
for BeagleBoard, because I need a driver for a rt2800usb dongle.

For some reason which I cannot work out, the rt2800usb options are
removed (rather then disabled) from the yocto kernel config, i.e., if I
run 'bitbake -c menuconfig linux-yocto', there is very little under
Drivers->Net->WLAN. If I run menuconfig in the devshell, there are lots
more WLAN drivers available, including the rt2800.

So, I created custom fragment with the appropriate options, which works
to the extent it gets picked up, but then the options are removed during
the kernel_configme process and end up in the missing_required.cfg, and
there is no information I can find anywhere in the logs as to why this
is the case. Any ideas how to find out what the problem is?

(I am using yocto master)

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

[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 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 base64.c  -fPIC -DPIC -o .libs/base64.o
| 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 beecrypt.c  -fPIC -DPIC -o .libs/beecrypt.o
| 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 blowfish.c  -fPIC -DPIC -o .libs/blowfish.o
| 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 blockmode.c  -fPIC -DPIC -o .libs/blockmode.o
| 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./in

Re: [yocto] why is YOCTO_GIT_URL defined to use http?

[Khem Raj]

On 03/18/2012 09:17 AM, Robert P. J. Day wrote:

  quite so, i wrote the above assuming there was a reason why you
*couldn't*  clone using thehttp://  protocol, and that this had been an
explicit decision (for whatever reason).  assuming, though, that it's
just an oversight and someone can fix that, i'll just carry on with my
proofreading.


its upto upstream package repo policy whatever protocols for git they 
want to expose. some may decide to expose http some not

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

Re: [yocto] using and auditing kernel config fragments

[Autif Khan]

> For some reason which I cannot work out, the rt2800usb options are
> removed (rather then disabled) from the yocto kernel config, i.e., if I
> run 'bitbake -c menuconfig linux-yocto', there is very little under
> Drivers->Net->WLAN. If I run menuconfig in the devshell, there are lots
> more WLAN drivers available, including the rt2800.

Under Device Drivers -> Network device support -> Wireless LAN, You
have to enable Ralink driver support to see the options for
CONFIG_RT2800USB

It is not under Device Drivers -> Network device support -> Wireless LAN

It is under Device Drivers -> Network device support -> Wireless LAN
-> Ralink driver support
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] using and auditing kernel config fragments

[Autif Khan]

>> For some reason which I cannot work out, the rt2800usb options are
>> removed (rather then disabled) from the yocto kernel config, i.e., if I
>> run 'bitbake -c menuconfig linux-yocto', there is very little under
>> Drivers->Net->WLAN. If I run menuconfig in the devshell, there are lots
>> more WLAN drivers available, including the rt2800.
>
> Under Device Drivers -> Network device support -> Wireless LAN, You
> have to enable Ralink driver support to see the options for
> CONFIG_RT2800USB
>
> It is not under Device Drivers -> Network device support -> Wireless LAN
>
> It is under Device Drivers -> Network device support -> Wireless LAN
> -> Ralink driver support

I forgot to mention - Under Networking Support -> Wireless, you need
to enable cfg80211 AND msc80211 (Generic IEEE 802.11 Netowrking Stack)

Then the Ralink driver support shows up under Wireless LAN
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] using and auditing kernel config fragments

[Bruce Ashfield]

On Fri, Apr 6, 2012 at 5:34 AM, Tomas Frydrych
 wrote:
> Hi,
>
> I am trying to add a kernel config fragment to the yocto 2.6.37 kernel
> for BeagleBoard, because I need a driver for a rt2800usb dongle.
>
> For some reason which I cannot work out, the rt2800usb options are
> removed (rather then disabled) from the yocto kernel config, i.e., if I
> run 'bitbake -c menuconfig linux-yocto', there is very little under
> Drivers->Net->WLAN. If I run menuconfig in the devshell, there are lots
> more WLAN drivers available, including the rt2800.
>
> So, I created custom fragment with the appropriate options, which works
> to the extent it gets picked up, but then the options are removed during
> the kernel_configme process and end up in the missing_required.cfg, and
> there is no information I can find anywhere in the logs as to why this
> is the case. Any ideas how to find out what the problem is?

If they end up in missing_required.cfg, it almost always means that a
dependency of the options listed in your fragment haven't been specified
and hence the option tossed out by lkc.

Looking via menuconfig or via the Kconfigs should show you what
the dependencies are, and your .config will show you what was specified
and ended up in the configuration. If dependencies are missing, add them
to your fragment .. and they should make it to the end.

Cheers,

Bruce

>
> (I am using yocto master)
>
> Tomas
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] using and auditing kernel config fragments

[Tomas Frydrych]

On 06/04/12 14:40, Autif Khan wrote:
> I forgot to mention - Under Networking Support -> Wireless, you need
> to enable cfg80211 AND msc80211 (Generic IEEE 802.11 Netowrking Stack)
> 
> Then the Ralink driver support shows up under Wireless LAN

Thanks, that's the bit I was missing. :)

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

[yocto] Belated experience survey of using Yocto 1.2

[Bob Cochran]

Q: Which architecture did you choose to build?

A: Very basic tests with default qemux86 and more extensive tests with 
mpc8315e-rdb (I have that piece of hardware)


Q: How easily were you able to build an image and boot an image?

A: Qemu was very easy & nice.  For mpc8315, I created a u-boot image to 
boot my hardware.  This required some customization of my recipe, which 
should probably be included in the README.hardware (since u-boot ram 
image is so basic for embedded powerpc).  I added "ext2.gz.u-boot" to 
IMAGE_FSTYPES and inherited image_types_uboot.


Q: Is there any surprise to you in the process of doing this Beta 
testing? If so, would you please describe it and tell us how you 
expected it to work?


A: I was a little confused on why we were told to use the web 
documentation and not build & use the current documentation in the 
project tree.  I never had the chance to figure out whether & where they 
were out of synch, but I did run into a problem when installing ADT and 
trying to find the 
http://downloads.yoctoproject.org/releases/eclipse-plugin/1.1.1 link, 
which didn't exist.


Q: How do you like our HOB interface? Please provide us with your 
thoughts and suggestions on HOB interface and functionality.


A: I launched it but decided it wasn't for me.  I'm not a fan of 
multiple layers of abstraction.  I am curious as to whether hob includes 
graphical visibility tools for the project tree.  I'll revisit this 
again later.



Q: Was it easy to find the support you needed to build and boot an image?

A: I didn't have any problems, but I usually rely on searching the mail 
lists or the source code when I do have issues.  I did send out one 
question about MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS.  It seemed that the 
documentation didn't adequately specify when and when not this variable 
will cause an error in the build process.



Q: Which Bugzilla reports did you submit?

A: none, but I did submit a patch for README.hardware

Q: Did you try anything else with Yocto 1.2?

A: here's what I did with mpc83155:

1) created my own layer and custom image recipe, starting with 
core-image-minimal

2) added various packages like dropbear and disk tools
3) created a u-boot ramdisk and booted from it via tftp
4) created the (meta-ide) toolchain and did some basic tests
5) Tried to install the eclipse plugin but ran into problems with ADT 
build version too old.  From the mail lists, it looks like I have a 
mismatch with the environment variable since my plugin was downloaded 
from 1.1.   I decided to call it quits here since I need to clean up my 
eclipse plugins for other reasons.  I'm looking forward to using the 
Yocto Eclipse plugin in the future.



Q: What would you like to have in Yocto Project for future releases?

A: These may already exist (& I haven't used HOB), but I'm currently 
looking for:


1) How to step through python code in recipes (my current plan is to 
hack bitbake).
2) Cut down the number of variables that generate items like package 
sets, packages, and tasks.  It seems that there are too many variables 
and the nuances between them are too subtle.  Let users introduce these 
subtle variables for their own needs, but the project should only have 
as few as necessary.
3) tool to perform quick reverse searches on variables - where are my 
variables being first set and then overridden in the various conf files.
4) A visibility tool that helps me understand why each directory or file 
was built (e.g, part of toolchain, rootfs, particular package 
dependency, etc.) and whether this directory / file was ultimately 
required to generate the toolchain or rootfs.  I have a feeling that I 
have quite a bit of dead bits in my project tree, but I haven't had a 
chance to dig in yet.
5) Less emphasis on external documentation and more on commenting in 
code.  Make sure all comments make sense to the casual developer.
6) Catalog of user experience on stability & deployment issues with 
yocto & OE recipes.  Be able to rate and comment about each package 
(e.g., interface you see in the (app store / marketplace / ubuntu 
software center ).
7) A better statement on the relationship of OE and Yocto going forward. 
 Am I going to be able to seamlessly build all OE recipes at some point?
8) Better web interface into the mail archives & encourage users in the 
documentation to search mail archives before posting questions (mailing 
lists aren't mentioned in the current quick start).



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

Re: [yocto] [PATCH 0/4][edison] Fix bootimg bug 2138 for 1.1.2

[Joshua Lock]

On 05/04/12 14:09, Darren Hart wrote:

Backport the following patches to edison. The backport involves massaging
this minimal set of patches to apply to bootimg.bbclass without pulling
in the refactoring or EFI support added in master about the same time.

These patches have been tested by building atom-pc core-image-minimal with
edison, a dosfsck and mount test on resulting image, and booting on the n450.

The following changes since commit 0fbd6a161576b2cafa8583adde0ffb15347c884a:

   poky.conf: Bumping SKD_VERSION (2012-03-14 15:49:33 -0700)

are available in the git repository at:
   git://git.pokylinux.org/poky-contrib dvhart/edison/bug/2138
   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/edison/bug/2138

Darren Hart (4):
   bootimg: Use mcopy to construct the hddimg
   bootimg: Account for FAT filesystem overhead in image size
   bootimg: Fix a math thinko in the block count calculation
   bootimg: Do not force FAT32 on all images, it violates the FAT
 specification

  meta/classes/bootimg.bbclass |   53 -
  1 files changed, 46 insertions(+), 7 deletions(-)



Thanks! I've merged these to my Edison test branch and (assuming testing 
goes well) will submit a consolidated pull shortly.


Cheers,
Joshua
--
Joshua '贾詡' Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/1][1.1.2] syslinux: Avoid using linux.ext2_fs.h if possible

[Joshua Lock]

On 04/04/12 13:50, Darren Hart wrote:

Please apply to poky/edison branch for 1.1.2 release. A corresponding patch has
been sent for oe-core and poky/master for the 1.2 release.

The following changes since commit 0fbd6a161576b2cafa8583adde0ffb15347c884a:

   poky.conf: Bumping SKD_VERSION (2012-03-14 15:49:33 -0700)

are available in the git repository at:
   git://git.pokylinux.org/poky-contrib dvhart/bug2236
   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/bug/2036


For folks playing along at home, that http url is wrong.
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/bug2236



Darren Hart (1):
   syslinux: Avoid using linux.ext2_fs.h if possible

  .../libinstaller-Avoid-using-linux-ext2_fs.h.patch |  975 
  meta/recipes-devtools/syslinux/syslinux_4.03.bb|5 +-
  2 files changed, 978 insertions(+), 2 deletions(-)
  create mode 100644 
meta/recipes-devtools/syslinux/files/libinstaller-Avoid-using-linux-ext2_fs.h.patch


Thanks! I've merged these to my Edison test branch and (assuming testing 
goes well) will submit a consolidated pull shortly.


Cheers,
Joshua
--
Joshua '贾詡' Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Unable to find recipe for glibc-2.11.1

[Khem Raj]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/26/2012 01:42 AM, Navani Srivastava wrote:
> Hi,
> 
> I am looking for recipe of glibc-2.11.1 version. I googled for it 
> but no success. Can anyone please suggest me the link from where i 
> can download the same?

you can look at 2.10.1 recipes from classic OE and port it over. btw
system C library is core part of system. I wonder why you need 2.11.1
specifically
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9/y3wACgkQuwUzVZGdMxRpYACeIs57ceetqDxpQNbAk84AH5La
KfkAn1RpC7HqVfYj/95JHIjGUt0Hazx/
=jBNP
-END PGP SIGNATURE-
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto