Date   

Re: e100 driver does not build

Tom Zanussi <tom.zanussi@...>
 

On Thu, 2011-09-01 at 11:34 -0700, Saxena, Rahul wrote:
Yes, I had noticed that it is part of intel-1xxxx feature also.

I tend to think that it is better to separate out CONFIG_E100 option from intel-1xxxx
I think that platforms that want 1G/10G enabled would not need 10/100 driver
Yeah, makes sense. I can do that if you want, or you can - either way
is fine with me...

Tom

It means that config option was never set or got turned off because of
unmet depencies <<

However I am not sure if this works in all cases as I did not see
"# CONFIG_E100 is not set" even when its dependent configurations were not satisfied

Rahul

-----Original Message-----
From: Zanussi, Tom
Sent: Thursday, September 01, 2011 11:22 AM
To: Saxena, Rahul
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] e100 driver does not build

On Thu, 2011-09-01 at 11:11 -0700, Saxena, Rahul wrote:
Yes, the problem was due to missing dependent options..
I had incorrectly assumed that dependent options would get pulled in
or perhaps a error would be generated.
It worked after I added following 3 options stated as dependent options
in a Kernel configuration database that I saw:

CONFIG_ISA
CONFIG_EISA
CONFIG_NET_PCI

I am still iterating to check if all three of the above are really needed or
or if just the CONFIG_NET_PCI option is needed.

I had enabled the option using a .cfg file. Also checking again to see if a warning
gets generated when the dependent options are not included.
Note that it's also part of the intel-1xxxx feature, which is basically
there for reusability - they were all together in a bunch of BSPs so I
moved them into a feature. I'm wondering whether we want to break them
up or at least create a separate e100 feature.

BTW what does a message such as following in the .config file mean ?

"CONFIG_xxxxx is not set"
It means that config option was never set or got turned off because of
unmet depencies.

Tom


Thanks
Rahul

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
Sent: Wednesday, August 31, 2011 6:27 PM
To: Zanussi, Tom
Cc: Saxena, Rahul; yocto@yoctoproject.org
Subject: Re: [yocto] e100 driver does not build

On 11-08-31 7:18 PM, Tom Zanussi wrote:

On Wed, 2011-08-31 at 16:04 -0700, Saxena, Rahul wrote:
I am unable to get the e100 driver to build for my BSP.

I have configured to build it as a module. I do not see the e100.ko
file being generated nor does

CONFIG_E100 appear in the generated .config file in my build area.



However I do see the driver source file e100.c in
tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1
+xxxx ../linux/drivers/net



I do not have any problems with other drivers (igb, E1000 etc) that I
have configured in exactly similar way.



Any insight on this issue ?
It's probably missing another option it depends on e.g. is
CONFIG_NET_PCI and CONFIG_MII enabled in your .config?
This is most likely what it is.

Out of curiosity, how did you enable the option ? Via a config fragement
(.cfg file) or via menuconfig .. or something else?

If you tried to set something via a fragment and it doesn't make it to
the final .config, you should see a warning during the kernel build
phase.

Cheers,

Bruce


Tom



Thanks

Rahul


_______________________________________________
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: e100 driver does not build

Saxena, Rahul <rahul.saxena@...>
 

Yes, I had noticed that it is part of intel-1xxxx feature also.

I tend to think that it is better to separate out CONFIG_E100 option from intel-1xxxx
I think that platforms that want 1G/10G enabled would not need 10/100 driver

It means that config option was never set or got turned off because of
unmet depencies <<

However I am not sure if this works in all cases as I did not see
"# CONFIG_E100 is not set" even when its dependent configurations were not satisfied

Rahul

-----Original Message-----
From: Zanussi, Tom
Sent: Thursday, September 01, 2011 11:22 AM
To: Saxena, Rahul
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] e100 driver does not build

On Thu, 2011-09-01 at 11:11 -0700, Saxena, Rahul wrote:
Yes, the problem was due to missing dependent options..
I had incorrectly assumed that dependent options would get pulled in
or perhaps a error would be generated.
It worked after I added following 3 options stated as dependent options
in a Kernel configuration database that I saw:

CONFIG_ISA
CONFIG_EISA
CONFIG_NET_PCI

I am still iterating to check if all three of the above are really needed or
or if just the CONFIG_NET_PCI option is needed.

I had enabled the option using a .cfg file. Also checking again to see if a warning
gets generated when the dependent options are not included.
Note that it's also part of the intel-1xxxx feature, which is basically
there for reusability - they were all together in a bunch of BSPs so I
moved them into a feature. I'm wondering whether we want to break them
up or at least create a separate e100 feature.

BTW what does a message such as following in the .config file mean ?

"CONFIG_xxxxx is not set"
It means that config option was never set or got turned off because of
unmet depencies.

Tom


Thanks
Rahul

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
Sent: Wednesday, August 31, 2011 6:27 PM
To: Zanussi, Tom
Cc: Saxena, Rahul; yocto@yoctoproject.org
Subject: Re: [yocto] e100 driver does not build

On 11-08-31 7:18 PM, Tom Zanussi wrote:

On Wed, 2011-08-31 at 16:04 -0700, Saxena, Rahul wrote:
I am unable to get the e100 driver to build for my BSP.

I have configured to build it as a module. I do not see the e100.ko
file being generated nor does

CONFIG_E100 appear in the generated .config file in my build area.



However I do see the driver source file e100.c in
tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1
+xxxx ../linux/drivers/net



I do not have any problems with other drivers (igb, E1000 etc) that I
have configured in exactly similar way.



Any insight on this issue ?
It's probably missing another option it depends on e.g. is
CONFIG_NET_PCI and CONFIG_MII enabled in your .config?
This is most likely what it is.

Out of curiosity, how did you enable the option ? Via a config fragement
(.cfg file) or via menuconfig .. or something else?

If you tried to set something via a fragment and it doesn't make it to
the final .config, you should see a warning during the kernel build
phase.

Cheers,

Bruce


Tom



Thanks

Rahul


_______________________________________________
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: RT kernel with core-image-sato build failed for sugarbay

Saul Wold <sgw@...>
 

On 08/31/2011 04:49 PM, Bodke, Kishore K wrote:
Hi,

I am trying to build core-image-sato with rt kernel for sugarbay and it
fails for the do_rootfs .

Attached is the build log.

Could you please let me know what went wrong?
Did you save a log of the build itself by any chance? It seems strange that you would have this dependencies are not being met.

Sau!

Thanks

Kishore.



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


Re: e100 driver does not build

Tom Zanussi <tom.zanussi@...>
 

On Thu, 2011-09-01 at 11:11 -0700, Saxena, Rahul wrote:
Yes, the problem was due to missing dependent options..
I had incorrectly assumed that dependent options would get pulled in
or perhaps a error would be generated.
It worked after I added following 3 options stated as dependent options
in a Kernel configuration database that I saw:

CONFIG_ISA
CONFIG_EISA
CONFIG_NET_PCI

I am still iterating to check if all three of the above are really needed or
or if just the CONFIG_NET_PCI option is needed.

I had enabled the option using a .cfg file. Also checking again to see if a warning
gets generated when the dependent options are not included.
Note that it's also part of the intel-1xxxx feature, which is basically
there for reusability - they were all together in a bunch of BSPs so I
moved them into a feature. I'm wondering whether we want to break them
up or at least create a separate e100 feature.

BTW what does a message such as following in the .config file mean ?

"CONFIG_xxxxx is not set"
It means that config option was never set or got turned off because of
unmet depencies.

Tom


Thanks
Rahul

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
Sent: Wednesday, August 31, 2011 6:27 PM
To: Zanussi, Tom
Cc: Saxena, Rahul; yocto@yoctoproject.org
Subject: Re: [yocto] e100 driver does not build

On 11-08-31 7:18 PM, Tom Zanussi wrote:

On Wed, 2011-08-31 at 16:04 -0700, Saxena, Rahul wrote:
I am unable to get the e100 driver to build for my BSP.

I have configured to build it as a module. I do not see the e100.ko
file being generated nor does

CONFIG_E100 appear in the generated .config file in my build area.



However I do see the driver source file e100.c in
tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1
+xxxx ../linux/drivers/net



I do not have any problems with other drivers (igb, E1000 etc) that I
have configured in exactly similar way.



Any insight on this issue ?
It's probably missing another option it depends on e.g. is
CONFIG_NET_PCI and CONFIG_MII enabled in your .config?
This is most likely what it is.

Out of curiosity, how did you enable the option ? Via a config fragement
(.cfg file) or via menuconfig .. or something else?

If you tried to set something via a fragment and it doesn't make it to
the final .config, you should see a warning during the kernel build
phase.

Cheers,

Bruce


Tom



Thanks

Rahul


_______________________________________________
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: e100 driver does not build

Bruce Ashfield <bruce.ashfield@...>
 

On 11-09-01 2:11 PM, Saxena, Rahul wrote:
Yes, the problem was due to missing dependent options..
I had incorrectly assumed that dependent options would get pulled in
or perhaps a error would be generated.
A warning can (and will) be generated for options that are
set by a BSP and don't end up in a final .config, but that's only
if you've placed them in a .cfg file and fed them through the
config auditing steps of the linux-yocto build (this is automatic).

dependencies won't be set automatically, it's the opposite,
you must ensure they are set or a particular Kconfig value must
select them.

It worked after I added following 3 options stated as dependent options
in a Kernel configuration database that I saw:

CONFIG_ISA
CONFIG_EISA
CONFIG_NET_PCI

I am still iterating to check if all three of the above are really needed or
or if just the CONFIG_NET_PCI option is needed.

I had enabled the option using a .cfg file. Also checking again to see if a warning
gets generated when the dependent options are not included.

BTW what does a message such as following in the .config file mean ?

"CONFIG_xxxxx is not set"
It should be:

# CONFIG_foo is not set

And that is should be read as "config foo is disabled"

Bruce



Thanks
Rahul

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
Sent: Wednesday, August 31, 2011 6:27 PM
To: Zanussi, Tom
Cc: Saxena, Rahul; yocto@yoctoproject.org
Subject: Re: [yocto] e100 driver does not build

On 11-08-31 7:18 PM, Tom Zanussi wrote:

On Wed, 2011-08-31 at 16:04 -0700, Saxena, Rahul wrote:
I am unable to get the e100 driver to build for my BSP.

I have configured to build it as a module. I do not see the e100.ko
file being generated nor does

CONFIG_E100 appear in the generated .config file in my build area.



However I do see the driver source file e100.c in
tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1
+xxxx ../linux/drivers/net



I do not have any problems with other drivers (igb, E1000 etc) that I
have configured in exactly similar way.



Any insight on this issue ?
It's probably missing another option it depends on e.g. is
CONFIG_NET_PCI and CONFIG_MII enabled in your .config?
This is most likely what it is.

Out of curiosity, how did you enable the option ? Via a config fragement
(.cfg file) or via menuconfig .. or something else?

If you tried to set something via a fragment and it doesn't make it to
the final .config, you should see a warning during the kernel build
phase.

Cheers,

Bruce


Tom



Thanks

Rahul


_______________________________________________
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: e100 driver does not build

Saxena, Rahul <rahul.saxena@...>
 

Yes, the problem was due to missing dependent options..
I had incorrectly assumed that dependent options would get pulled in
or perhaps a error would be generated.
It worked after I added following 3 options stated as dependent options
in a Kernel configuration database that I saw:

CONFIG_ISA
CONFIG_EISA
CONFIG_NET_PCI

I am still iterating to check if all three of the above are really needed or
or if just the CONFIG_NET_PCI option is needed.

I had enabled the option using a .cfg file. Also checking again to see if a warning
gets generated when the dependent options are not included.

BTW what does a message such as following in the .config file mean ?

"CONFIG_xxxxx is not set"


Thanks
Rahul

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
Sent: Wednesday, August 31, 2011 6:27 PM
To: Zanussi, Tom
Cc: Saxena, Rahul; yocto@yoctoproject.org
Subject: Re: [yocto] e100 driver does not build

On 11-08-31 7:18 PM, Tom Zanussi wrote:

On Wed, 2011-08-31 at 16:04 -0700, Saxena, Rahul wrote:
I am unable to get the e100 driver to build for my BSP.

I have configured to build it as a module. I do not see the e100.ko
file being generated nor does

CONFIG_E100 appear in the generated .config file in my build area.



However I do see the driver source file e100.c in
tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1
+xxxx ../linux/drivers/net



I do not have any problems with other drivers (igb, E1000 etc) that I
have configured in exactly similar way.



Any insight on this issue ?
It's probably missing another option it depends on e.g. is
CONFIG_NET_PCI and CONFIG_MII enabled in your .config?
This is most likely what it is.

Out of curiosity, how did you enable the option ? Via a config fragement
(.cfg file) or via menuconfig .. or something else?

If you tried to set something via a fragment and it doesn't make it to
the final .config, you should see a warning during the kernel build
phase.

Cheers,

Bruce


Tom



Thanks

Rahul


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


Re: [PATCH][meta-intel] grub: remove the dependency on freetype, disable grub-mkfont

Saul Wold <sgw@...>
 

Seeing this change reminded me that we really should move grub_1.98 to oe-core, is there any objection to this? Any reason this should not be part of oe-core to support general x86_64 machines?

Sau!

On 08/31/2011 07:34 PM, Darren Hart wrote:
Grub's configure task was picking up the host freetype libraries if
bitbake hadn't gotten around building freetype yet. We could add a
dependency on freetype, but it's only used for the optional grub-mkfont
utility which we don't really need.

Disable grub-mkfont via EXTRA_OECONF, removing the dependency on freetype.

Testing: core-image-minimal build and install on sugarbay.

Signed-off-by: Darren Hart<dvhart@linux.intel.com>
Tested-by: Tom Zanussi<tom.zanussi@intel.com>
---
common/recipes-bsp/grub/grub_1.98.bb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/common/recipes-bsp/grub/grub_1.98.bb b/common/recipes-bsp/grub/grub_1.98.bb
index 0cd3a40..802733f 100644
--- a/common/recipes-bsp/grub/grub_1.98.bb
+++ b/common/recipes-bsp/grub/grub_1.98.bb
@@ -24,7 +24,7 @@ SRC_URI = "ftp://alpha.gnu.org/gnu/grub/grub-${PV}.tar.gz \
inherit autotools
inherit gettext

-EXTRA_OECONF = "--with-platform=pc --target=i386"
+EXTRA_OECONF = "--with-platform=pc --target=i386 --disable-grub-mkfont"

do_configure() {
oe_runconf


Re: RT kernel with core-image-sato build failed for sugarbay

Tom Zanussi <tom.zanussi@...>
 

On Wed, 2011-08-31 at 16:49 -0700, Bodke, Kishore K wrote:
Hi,



I am trying to build core-image-sato with rt kernel for sugarbay and
it fails for the do_rootfs .
FWIW, I was able to build and boot core-image-sato with the rt kernel:

Linux sugarbay 3.0.3-rt8-yocto-preempt-rt+ #1 SMP PREEMPT RT Wed Aug 31
21:33:27 CDT 2011 x86_64 GNU/Linux

using the following commits:

poky/master 705ec50edda7f7fb8c132238fe3f1477384a470e
meta/intel 902d2f3c919cd1d870dc8d35a7521cbba42e53ea

Actually, meta/intel was that commit with Darren's grub patch on top
(meta-intel/dvhart/grub-freetype).

Tom



Attached is the build log.



Could you please let me know what went wrong?



Thanks

Kishore.


[PATCH][meta-intel] grub: remove the dependency on freetype, disable grub-mkfont

Darren Hart <dvhart@...>
 

Grub's configure task was picking up the host freetype libraries if
bitbake hadn't gotten around building freetype yet. We could add a
dependency on freetype, but it's only used for the optional grub-mkfont
utility which we don't really need.

Disable grub-mkfont via EXTRA_OECONF, removing the dependency on freetype.

Testing: core-image-minimal build and install on sugarbay.

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Tested-by: Tom Zanussi <tom.zanussi@intel.com>
---
common/recipes-bsp/grub/grub_1.98.bb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/common/recipes-bsp/grub/grub_1.98.bb b/common/recipes-bsp/grub/grub_1.98.bb
index 0cd3a40..802733f 100644
--- a/common/recipes-bsp/grub/grub_1.98.bb
+++ b/common/recipes-bsp/grub/grub_1.98.bb
@@ -24,7 +24,7 @@ SRC_URI = "ftp://alpha.gnu.org/gnu/grub/grub-${PV}.tar.gz \
inherit autotools
inherit gettext

-EXTRA_OECONF = "--with-platform=pc --target=i386"
+EXTRA_OECONF = "--with-platform=pc --target=i386 --disable-grub-mkfont"

do_configure() {
oe_runconf
--
1.7.6


Re: Unable to find package mio-lib (mio-lib)!

蔡振军 <caizhenjun@...>
 

Appreciate your response. This error is caused by the reason you describe. I add a name of package not created to installation list.

Changing to –staticdev package name, this error disappear as expected.

 

Thanks.

feye

 

蔡振军

网新技术有限公司物联网事业部

杭州天目山路226号网新大厦

电话-138 6745 1910

 


Re: e100 driver does not build

Bruce Ashfield <bruce.ashfield@...>
 

On 11-08-31 7:18 PM, Tom Zanussi wrote:

On Wed, 2011-08-31 at 16:04 -0700, Saxena, Rahul wrote:
I am unable to get the e100 driver to build for my BSP.

I have configured to build it as a module. I do not see the e100.ko
file being generated nor does

CONFIG_E100 appear in the generated .config file in my build area.



However I do see the driver source file e100.c in
tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1
+xxxx ../linux/drivers/net



I do not have any problems with other drivers (igb, E1000 etc) that I
have configured in exactly similar way.



Any insight on this issue ?
It's probably missing another option it depends on e.g. is
CONFIG_NET_PCI and CONFIG_MII enabled in your .config?
This is most likely what it is.

Out of curiosity, how did you enable the option ? Via a config fragement
(.cfg file) or via menuconfig .. or something else?

If you tried to set something via a fragment and it doesn't make it to
the final .config, you should see a warning during the kernel build
phase.

Cheers,

Bruce


Tom



Thanks

Rahul


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


RT kernel with core-image-sato build failed for sugarbay

Bodke, Kishore K <kishore.k.bodke@...>
 

Hi,

 

I am trying to build core-image-sato with rt kernel for sugarbay and it fails for the do_rootfs .

 

Attached is the build log.

 

Could you please let me know what went wrong?

 

Thanks

Kishore.


Re: e100 driver does not build

Tom Zanussi <tom.zanussi@...>
 

On Wed, 2011-08-31 at 16:04 -0700, Saxena, Rahul wrote:
I am unable to get the e100 driver to build for my BSP.

I have configured to build it as a module. I do not see the e100.ko
file being generated nor does

CONFIG_E100 appear in the generated .config file in my build area.



However I do see the driver source file e100.c in
tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1
+xxxx ../linux/drivers/net



I do not have any problems with other drivers (igb, E1000 etc) that I
have configured in exactly similar way.



Any insight on this issue ?
It's probably missing another option it depends on e.g. is
CONFIG_NET_PCI and CONFIG_MII enabled in your .config?

Tom



Thanks

Rahul


e100 driver does not build

Saxena, Rahul <rahul.saxena@...>
 

I am unable to get the e100 driver to build for my BSP.

I have configured to build it as a module. I do  not see the e100.ko file being generated nor does

 CONFIG_E100 appear in the generated .config file in my build area.

 

However I do see the driver source file e100.c in   tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1+xxxx ../linux/drivers/net    

 

I do not have any problems with other drivers (igb, E1000 etc)  that I have configured in exactly similar way.

 

Any insight on this issue ? 

 

Thanks

Rahul


Re: ARM summit at Plumbers 2011

Steve McIntyre <steve.mcintyre@...>
 

[ Last big cross-post; I'll just post to the cross-distro list in
future! ]

On Tue, Aug 23, 2011 at 05:11:34PM +0100, Steve McIntyre wrote:
On Tue, Aug 09, 2011 at 07:15:34PM +0100, Steve McIntyre wrote:

[ARM summit at Plumbers, Thursday 8th September]
UPDATE: we've not had many people confirm interest in this event yet,
which is a shame. If you would like to join us for this session,
please reply and let me know. If we don't get enough interest by the
end of Sunday (28th August), then we'll have to cancel the meeting.
And that seemed to provoke enought interest from people all over,
which is good. This event is definitely going on. Let's look forwards
to some good discussion. :-)

Cheers,
--
Steve McIntyre steve.mcintyre@linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs


Re: bbappend - Where should my file be?

Richard Purdie
 

On Wed, 2011-08-31 at 20:33 +0100, Chris Tapp wrote:
Sorry for the delay in looking at this again.

I can't re-create the behaviour here either, though it was repeatable
before. However, since then I've made quite a few changes to the
recipe and done a complete re-build.

It was also failing with the correct paths - I was trying all sorts of
combinations when the correct one wasn't working!

I'll try and do some more testing here (with what I think the recipe
was at the time) to see if I can get it to show again. I've only got a
slow build machine, so it may take a while ;-)
Ok, in the meantime I've resolved the bug as worksforme since we're
unable to reproduce. Please do open (or reopen) one if you can reproduce
the problem though, I'd be interested to get to the bottom of it.

Cheers,

Richard


Re: [PATCH 1/1] poky.conf: perform network sanity check by default for poky distros

Richard Purdie
 

On Wed, 2011-08-31 at 12:21 -0700, Joshua Lock wrote:
On Thu, 2011-08-25 at 10:15 -0700, Joshua Lock wrote:
Add CONNECTIVITY_CHECK_URIS to run the network connectivity sanity test for
http, https and git sources.

The variable is soft-assigned so that it's easily overrideable.

Signed-off-by: Joshua Lock <josh@linux.intel.com>
---
meta-yocto/conf/distro/poky.conf | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index c5fc3b9..46b22f4 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -54,5 +54,10 @@ ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"

-
+# The CONNECTIVITY_CHECK_URI's are used to test whether we can succesfully
+# fetch from the network (and warn you if not). To disable the test set
+# the variable to be empty.
+CONNECTIVITY_CHECK_URIS ?= "git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=HEAD \
+ https://eula-downloads.yoctoproject.org/index.php \
+ http://bugzilla.yoctoproject.org/report.cgi"
Any feedback on this patch?
Merged to master, thanks.

(it had slipped out the queue somehow, sorry)

Richard


Re: bbappend - Where should my file be?

Chris Tapp
 

On 30 Aug 2011, at 19:07, Richard Purdie wrote:

On Fri, 2011-08-12 at 00:51 +0100, Chris Tapp wrote:
I've got a linux-wrs_git.bbappend file in a layer (under poky laverne
4.0.1) that contains:

COMPATIBLE_MACHINE_Vortex86DX = "Vortex86DX"
WRMACHINE_Vortex86DX = "common_pc"

FILESEXTRAPATHS := "${THISDIR}/${PN}"

SRC_URI += " file://defconfig"

Where should the defconfig file be relative to the bbappend?

I've tried:

MyLayer
+--- recipies
+--- linux
+--- linux-wrs_git.bbappend
+--- linux-wrs_git
+--- defconfig


However, my defconfig file isn't being picked up during do_unpack:

cp: cannot stat `/home/chris/yocto/yocto-versions/laverne-4.0.1/meta/
recipes-kernel/linux/files/defconfig': No such file or directory
NOTE: Unpacking /home/chris/yocto/yocto-downloads/
git_git.pokylinux.org.linux-2.6-windriver.git.tar.gz to /home/chris/
yocto/mbox-3300-build/tmp/work/Vortex86DX-poky-linux/linux-
wrs
-2.6.34
+
git0
+
b67e060194a38c6331da1532bd06446087a42b3b_0
+0431115c9d720fee5bb105f6a7411efb4f851d26-r12/
NOTE: Unpacking /home/chris/yocto/yocto-versions/laverne-4.0.1/meta/
recipes-kernel/linux/files/defconfig to /home/chris/yocto/mbox-3300-
build/tmp/work/Vortex86DX-poky-linux/linux-
wrs
-2.6.34
+
git0
+
b67e060194a38c6331da1532bd06446087a42b3b_0
+0431115c9d720fee5bb105f6a7411efb4f851d26-r12/
ERROR: Task failed:

Which seems to show that it's not looking in FILESEXTRAPATHS.

The .bbappend file seems to be processed, as commenting out the
SRC_URI line gets rid of the error.

What have I got wrong?
I've just been looking at the open bug related to this
(http://bugzilla.yoctoproject.org/show_bug.cgi?id=1379) and I can't
reproduce an issue with layers ending with -numeric causing a
problem :/.

In the above example,

recipies/linux/linux-wrs/defconfig

is the correct path since PN == "linux-wrs". (you had linux-wrs_git).
Could you check whether the layer numeric part is a red herring please
and whether the above path works?
Hi Richard,

Sorry for the delay in looking at this again.

I can't re-create the behaviour here either, though it was repeatable before. However, since then I've made quite a few changes to the recipe and done a complete re-build.

It was also failing with the correct paths - I was trying all sorts of combinations when the correct one wasn't working!

I'll try and do some more testing here (with what I think the recipe was at the time) to see if I can get it to show again. I've only got a slow build machine, so it may take a while ;-)

Chris Tapp

opensource@keylevel.com
www.keylevel.com


Re: [PATCH 1/1] poky.conf: perform network sanity check by default for poky distros

Joshua Lock <josh@...>
 

On Thu, 2011-08-25 at 10:15 -0700, Joshua Lock wrote:
Add CONNECTIVITY_CHECK_URIS to run the network connectivity sanity test for
http, https and git sources.

The variable is soft-assigned so that it's easily overrideable.

Signed-off-by: Joshua Lock <josh@linux.intel.com>
---
meta-yocto/conf/distro/poky.conf | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index c5fc3b9..46b22f4 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -54,5 +54,10 @@ ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"

-
+# The CONNECTIVITY_CHECK_URI's are used to test whether we can succesfully
+# fetch from the network (and warn you if not). To disable the test set
+# the variable to be empty.
+CONNECTIVITY_CHECK_URIS ?= "git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=HEAD \
+ https://eula-downloads.yoctoproject.org/index.php \
+ http://bugzilla.yoctoproject.org/report.cgi"
Any feedback on this patch?

Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre


Re: Unable to find package mio-lib (mio-lib)!

Richard Purdie
 

On Wed, 2011-08-31 at 14:28 +0800, 蔡振军 wrote:

grep -rn "mio-lib" ./

Binary file ./armv5te/mio-lib-dbg-0.1-r0.armv5te.rpm matches

Binary file ./armv5te/mio-lib-dev-0.1-r0.armv5te.rpm matches

Binary file ./armv5te/solvedb/Nvra matches

Binary file ./armv5te/solvedb/__db.006 matches

Binary file ./armv5te/solvedb/__db.003 matches

Binary file ./armv5te/solvedb/Providename matches

Binary file ./armv5te/solvedb/Packages matches

Binary file ./armv5te/solvedb/Name matches

./armv5te/solvedb/manifest:7:/home/ll/work/optimus-imx28-build/tmp/deploy/rpm/armv5te/mio-lib-dbg-0.1-r0.armv5te.rpm

./armv5te/solvedb/manifest:351:/home/ll/work/optimus-imx28-build/tmp/deploy/rpm/armv5te/mio-lib-dev-0.1-r0.armv5te.rpm

./armv5te/solvedb/manifest:474:/home/ll/work/optimus-imx28-build/tmp/deploy/rpm/armv5te/mio-lib-staticdev-0.1-r0.armv5te.rpm
So there is
no ./armv5te/solvedb/manifest:7:/home/ll/work/optimus-imx28-build/tmp/deploy/rpm/armv5te/mio-lib-0.1-r0.armv5te.rpm

This means you probably didn't install any files into the main package
itself so it was empty and not created.


error appear when I delete some line in makefile’s install
target.Fllow is my operation:



install: $(all_targets)

install -D -m 644 libaio.h $(includedir)/libaio.h

install -D -m 644 libaio.a $(libdir)/libaio.a

install -D -m 755 $(libname) $(libdir)/$(libname)
===============original one

ln -sf $(libname) $(libdir)/$(soname)

ln -sf $(libname) $(libdir)/libaio.so



||

||

||

\/



install: $(all_targets)

install -D -m 644 libaio.h $(includedir)/libaio.h

install -D -m 644 libaio.a $(libdir)/libaio.a
===================== bad work





install: $(all_targets)

install -D -m 755 $(libname) $(libdir)/$(libname)
=======================google work
I don't know exactly what you mean here but your probably almost
certainly is due to the do_install function not installing the correct
files, or you are only installing headers and a static library so only
the -dev and -staticdev packages are created.

Cheers,

Richard