Date   

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@...
<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@...>
---
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@...
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@...>
---
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


Re: [PATCH 0/2] [YOCTO #1396] 1396 is reopened from the initial fix

Richard Purdie
 

On Wed, 2011-08-31 at 12:03 -0700, Jessica Zhang wrote:
This patch revert the original fix which broke ppc/powerpc case and fix
term consistency in adt_installer.conf

The following changes since commit 0ac19e84db3794b0d9280bd3cf9bae1719de3d6d:
Jessica Zhang (1):
Merge branch 'master' of ssh://git.yoctoproject.org/poky

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib jzhang/1396-reopen
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jzhang/1396-reopne

Jessica Zhang (2):
Revert "Fix adt-installer for consistent naming for powerpc and add
all arch template for installation"
[YOCTO #1396] Fix powerpc term and provide more template for
different arches
Merged to master, thanks.

Richard


[PATCH 2/2] [YOCTO #1396] Fix powerpc term and provide more template for different arches

Zhang, Jessica
 

Signed-off-by: Jessica Zhang <jessica.zhang@...>
---
.../installer/adt-installer/adt_installer.conf | 15 ++++++++++++++-
1 files changed, 14 insertions(+), 1 deletions(-)

diff --git a/meta/recipes-devtools/installer/adt-installer/adt_installer.conf b/meta/recipes-devtools/installer/adt-installer/adt_installer.conf
index 0c93237..2038b09 100644
--- a/meta/recipes-devtools/installer/adt-installer/adt_installer.conf
+++ b/meta/recipes-devtools/installer/adt-installer/adt_installer.conf
@@ -27,7 +27,7 @@ YOCTOADT_REPO="http://adtrepo.yoctoproject.org/$YOCTOADT_VERSION"

# The following are for system wide setup
# Target architectures that you want to setup host cross dev environment for
-# valid values are: powerpc, mips, arm, x86, x86_64 with space separation between entries
+# valid values are: arm, x86, x86_64, ppc, mips with space separation between entries
YOCTOADT_TARGETS="arm x86"
# Whether install qemu or not, valid entries are: Y/N
YOCTOADT_QEMU="Y"
@@ -50,3 +50,16 @@ YOCTOADT_TARGET_SYSROOT_LOC_arm="$HOME/test-yocto/arm"
#YOCTOADT_ROOTFS_x86="sato-sdk"
#YOCTOADT_TARGET_SYSROOT_IMAGE_x86="sato-sdk"
#YOCTOADT_TARGET_SYSROOT_LOC_x86="$HOME/test-yocto/x86"
+
+#Here's some template of other arches, which you need to change the value in ""
+#YOCTOADT_TARGET_SYSROOT_IMAGE_x86_64=""
+#YOCTOADT_TARGET_SYSROOT_LOC_x86_64=""
+#YOCTOADT_ROOTFS_x86_64=""
+
+#YOCTOADT_TARGET_SYSROOT_IMAGE_ppc=""
+#YOCTOADT_TARGET_SYSROOT_LOC_ppc=""
+#YOCTOADT_ROOTFS_ppc=""
+
+#YOCTOADT_TARGET_SYSROOT_IMAGE_mips=""
+#YOCTOADT_TARGET_SYSROOT_LOC_mips=""
+#YOCTOADT_ROOTFS_mips=""
--
1.7.0.4


[PATCH 1/2] Revert "Fix adt-installer for consistent naming for powerpc and add all arch template for installation"

Zhang, Jessica
 

This reverts commit ae4ad20edbb6ea023155f7ae2b00871d479e370d.
---
.../installer/adt-installer/adt_installer.conf | 17 ++---------------
.../adt-installer/scripts/adt_installer_internal | 2 +-
.../installer/adt-installer/scripts/data_define | 2 +-
3 files changed, 4 insertions(+), 17 deletions(-)

diff --git a/meta/recipes-devtools/installer/adt-installer/adt_installer.conf b/meta/recipes-devtools/installer/adt-installer/adt_installer.conf
index e31f9af..0c93237 100644
--- a/meta/recipes-devtools/installer/adt-installer/adt_installer.conf
+++ b/meta/recipes-devtools/installer/adt-installer/adt_installer.conf
@@ -27,7 +27,7 @@ YOCTOADT_REPO="http://adtrepo.yoctoproject.org/$YOCTOADT_VERSION"

# The following are for system wide setup
# Target architectures that you want to setup host cross dev environment for
-# valid values are: arm, x86, x86_64, powerpc, mips with space separation between entries
+# valid values are: powerpc, mips, arm, x86, x86_64 with space separation between entries
YOCTOADT_TARGETS="arm x86"
# Whether install qemu or not, valid entries are: Y/N
YOCTOADT_QEMU="Y"
@@ -40,7 +40,7 @@ YOCTOADT_NFS_UTIL="Y"

#The followings are for setting up specific target architecture
#YOCTOADT_ROOTFS_$arch is for specifying what root filesystem image files you want to download from the repository. The valid values to replace $arch are: arm, x86, x86_64, powerpc, mips. The valid image files are: minimal, minimal-dev, sato, sato-dev, sato-sdk,lsb, lsb-dev, lsb-sdk. If you want to download multiple images, the entries are space separated
-YOCTOADT_ROOTFS_arm="minimal"
+YOCTOADT_ROOTFS_arm="minimal sato-sdk"
#Specify which root filesystem file to use to extract as target sysroot. Please ensure the entry is in the list of downloaded root filesystem files that specified above in YOCTOADT_ROOTFS_$arch
YOCTOADT_TARGET_SYSROOT_IMAGE_arm="minimal"
#The location where the target sysroot will be setup
@@ -50,16 +50,3 @@ YOCTOADT_TARGET_SYSROOT_LOC_arm="$HOME/test-yocto/arm"
#YOCTOADT_ROOTFS_x86="sato-sdk"
#YOCTOADT_TARGET_SYSROOT_IMAGE_x86="sato-sdk"
#YOCTOADT_TARGET_SYSROOT_LOC_x86="$HOME/test-yocto/x86"
-
-#Here's some template of other arches, which you need to change the value in ""
-#YOCTOADT_TARGET_SYSROOT_IMAGE_x86_64=""
-#YOCTOADT_TARGET_SYSROOT_LOC_x86_64=""
-#YOCTOADT_ROOTFS_x86_64=""
-
-#YOCTOADT_TARGET_SYSROOT_IMAGE_powerpc=""
-#YOCTOADT_TARGET_SYSROOT_LOC_powerpc=""
-#YOCTOADT_ROOTFS_powerpc=""
-
-#YOCTOADT_TARGET_SYSROOT_IMAGE_mips=""
-#YOCTOADT_TARGET_SYSROOT_LOC_mips=""
-#YOCTOADT_ROOTFS_mips=""
diff --git a/meta/recipes-devtools/installer/adt-installer/scripts/adt_installer_internal b/meta/recipes-devtools/installer/adt-installer/scripts/adt_installer_internal
index c7de0e2..870931e 100755
--- a/meta/recipes-devtools/installer/adt-installer/scripts/adt_installer_internal
+++ b/meta/recipes-devtools/installer/adt-installer/scripts/adt_installer_internal
@@ -105,7 +105,7 @@ $OPKG_INSTALL_NATIVE_CMD libtool-nativesdk &>> $YOCTOADT_INSTALL_LOG_FILE
check_result

for native_target_type in $YOCTOADT_TARGETS; do
- native_target_type=`echo "$native_target_type" | sed -e 's/x86_64/x86-64/' -e 's/x86$/i586/'`
+ native_target_type=`echo "$native_target_type" | sed -e 's/x86_64/x86-64/' -e 's/ppc/powerpc/' -e 's/x86$/i586/'`
echo_info "Installing cross toolchain for $native_target_type ..."
echo_info "Installing binutils for $native_target_type ..."
$OPKG_INSTALL_NATIVE_CMD binutils-cross-canadian-$native_target_type &>> $YOCTOADT_INSTALL_LOG_FILE
diff --git a/meta/recipes-devtools/installer/adt-installer/scripts/data_define b/meta/recipes-devtools/installer/adt-installer/scripts/data_define
index 1de21d7..2781e77 100644
--- a/meta/recipes-devtools/installer/adt-installer/scripts/data_define
+++ b/meta/recipes-devtools/installer/adt-installer/scripts/data_define
@@ -32,7 +32,7 @@ OPKG_LIBDIR="/var/lib"
# List all supported root fs types and target types,
# it will be used in user configuration validity checking
YOCTOADT_SUPPORTED_ROOTFS="minimal minimal-dev sato sato-dev sato-sdk lsb lsb-dev lsb-sdk"
-YOCTOADT_SUPPORTED_TARGETS="x86 x86_64 arm powerpc mips"
+YOCTOADT_SUPPORTED_TARGETS="x86 x86_64 arm ppc mips"
# Different host (32 bit or 64 bit) will have different opkg
# configuration files
YOCTOADT_OPKG_CONF_FILE_32="./opkg/conf/opkg-sdk-i686.conf"
--
1.7.0.4


[PATCH 0/2] [YOCTO #1396] 1396 is reopened from the initial fix

Zhang, Jessica
 

This patch revert the original fix which broke ppc/powerpc case and fix
term consistency in adt_installer.conf

The following changes since commit 0ac19e84db3794b0d9280bd3cf9bae1719de3d6d:
Jessica Zhang (1):
Merge branch 'master' of ssh://git.yoctoproject.org/poky

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib jzhang/1396-reopen
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jzhang/1396-reopne

Jessica Zhang (2):
Revert "Fix adt-installer for consistent naming for powerpc and add
all arch template for installation"
[YOCTO #1396] Fix powerpc term and provide more template for
different arches

.../installer/adt-installer/adt_installer.conf | 10 +++++-----
.../adt-installer/scripts/adt_installer_internal | 2 +-
.../installer/adt-installer/scripts/data_define | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)


Re: linux-yocto-rt build fail for sugarbay bsp on grub recipe

Richard Purdie
 

On Tue, 2011-08-30 at 18:39 -0700, Darren Hart wrote:
I've attached mine and Kishore's. Mine builds grub, while his does not.

I noticed that Kishore's config.log differs from mine in some configure tests. For example:

Mine contains (config.log-dvhart):

configure:8739: checking for __bswapsi2
configure:8739: gcc -o conftest -O2 -pipe -g -feliminate-unused-debug-types -DGRUB_MACHINE_PCBIOS=1 -Wall -W -Wshadow -Wpointer-arith -Wmissing-prototypes -Wundef -Wstrict-prototypes -g -falign-jumps=1 -falign-loops=1 -falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow -fno-dwarf2-cfi-asm -m32 -fno-stack-protector -mno-stack-arg-probe -Werror -nostdlib -Wl,--defsym,___main=0x8100 -Wl,--defsym,abort=main -Wno-error -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -m32 conftest.c -lgcc >&5
In file included from /usr/include/features.h:387,
from /usr/include/limits.h:27,
from /usr/lib/gcc/x86_64-linux-gnu/4.4.5/include-fixed/limits.h:122,
from /usr/lib/gcc/x86_64-linux-gnu/4.4.5/include-fixed/syslimits.h:7,
from /usr/lib/gcc/x86_64-linux-gnu/4.4.5/include-fixed/limits.h:11,
from conftest.c:62:
/usr/include/gnu/stubs.h:7: fatal error: gnu/stubs-32.h: No such file or directory compilation terminated.
configure:8739: $? = 1


While there is no reference to stubs.h in Kishore's config.log (confi-1.log):

configure:8739: checking for __bswapsi2
configure:8739: gcc -o conftest -O2 -pipe -g -feliminate-unused-debug-types -DGRUB_MACHINE_PCBIOS=1 -Wall -W -Wshadow -Wpointer-arith -Wmissing-prototypes -Wundef -Wstrict-prototypes -g -falign-jumps=1 -falign-loops=1 -falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow -fno-dwarf2-cfi-asm -m32 -fno-stack-protector -Werror -nostdlib -Wl,--defsym,___main=0x8100 -Wl,--defsym,abort=main -Wno-error -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -m32 conftest.c -lgcc >&5
conftest.c:75: warning: function declaration isn't a prototype
/usr/bin/ld: warning: cannot find entry symbol _start; defaulting to 00000000080480c0
configure:8739: $? = 0
configure:8739: result: yes
This is interesting. What its saying here is that your build system
compiler can't compile 32 bit (the -m32 flag) since there are no 32 bit
headers present. Kishore's must have 32 bit headers installed (or be a
32 bit system). We shouldn't be seeing those differences but what they
amount to I don't know without looking at grub in more detail.

I also found that Kishore's config.log includes:
freetype_cflags='-I/usr/include/freetype2'
freetype_libs='-lfreetype -lz'

While mine includes:
freetype_cflags='-I/build/poky/sugarbay/tmp/sysroots/sugarbay/usr/include/freetype2 -I/build/poky/sugarbay/tmp/sysroots/sugarbay/usr/include'
freetype_libs='-L/build/poky/sugarbay/tmp/sysroots/sugarbay/usr/lib -lfreetype'

This would certainly be cause for a QA test failure.
Yes, this is certainly the problem.

Perhaps a DEPENDS=freetype in the grub recipe is in order?

Alternatively, we could see about configuring it without freetype.
I'd tend to favour the latter unless someone can convince me freetype
support adds something really useful to grub.

Cheers,

Richard


Re: lttng-ust fails to build in current mainline for beagleboard.

Saul Wold <sgw@...>
 

On 08/30/2011 02:41 AM, Enric Balletbò i Serra wrote:
Hi all,

Seems the package lttng-ust fails to build in current mainline, is
currently the build for beagleboard broken ?
This is a known issue, see
http://bugzilla.pokylinux.org/show_bug.cgi?id=1381

The problem appears to be an issue in the Compiler.

Sau!

The log looks like:

ERROR: Function 'do_compile' failed (see
/home/eballetbo/Workspace/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/temp/log.do_compile.24087
for further information)
ERROR: Logfile of failure stored in:
/home/eballetbo/Workspace/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/temp/log.do_compile.24087
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi',
'common']
| NOTE: make -j 4
| make all-recursive
| make[1]: Entering directory
`/home/eballetbo/Workspace/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/ust-0.15'
| Making all in snprintf
| make[2]: Entering directory
`/home/eballetbo/Workspace/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/ust-0.15/snprintf'
| /bin/sh ../arm-poky-linux-gnueabi-libtool --tag=CC --mode=compile
arm-poky-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize
-mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8
--sysroot=/home/eballetbo/Workspace/yocto/build/tmp/sysroots/igep0020
-DHAVE_CONFIG_H -I. -I.. -I../include/ust -I../include
-I../libustcomm -DUST_COMPONENT="ust_snprintf" -fPIC
-fno-strict-aliasing -Wall -O2 -pipe -g -feliminate-unused-debug-types
-MT libustsnprintf_la-vfprintf.lo -MD -MP -MF
.deps/libustsnprintf_la-vfprintf.Tpo -c -o
libustsnprintf_la-vfprintf.lo `test -f 'vfprintf.c' || echo
'./'`vfprintf.c
| arm-poky-linux-gnueabi-libtool: compile: arm-poky-linux-gnueabi-gcc
-march=armv7-a -fno-tree-vectorize -mthumb-interwork
-mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8
--sysroot=/home/eballetbo/Workspace/yocto/build/tmp/sysroots/igep0020
-DHAVE_CONFIG_H -I. -I.. -I../include/ust -I../include -I../libustcomm
-DUST_COMPONENT=ust_snprintf -fPIC -fno-strict-aliasing -Wall -O2
-pipe -g -feliminate-unused-debug-types -MT
libustsnprintf_la-vfprintf.lo -MD -MP -MF
.deps/libustsnprintf_la-vfprintf.Tpo -c vfprintf.c -fPIC -DPIC -o
.libs/libustsnprintf_la-vfprintf.o
| vfprintf.c: In function 'ust_safe_vfprintf':
| vfprintf.c:956:1: error: unrecognizable insn:
| (insn 3968 3967 3969 145 (set (subreg:SI (reg/v:DI 160 [ _umax ]) 0)
| (sign_extend:SI (mem:QI (plus:SI (mult:SI (reg/v:SI 166 [ nextarg ])
| (const_int 8 [0x8]))
| (reg/f:SI 370 [ argtable.7 ])) [0 *D.6937_569+0
S1 A32]))) vfprintf.c:555 -1
| (nil))
| vfprintf.c:956:1: internal compiler error: in extract_insn, at recog.c:2109
| Please submit a full bug report,
| with preprocessed source if appropriate.
| See<http://gcc.gnu.org/bugs.html> for instructions.
| make[2]: *** [libustsnprintf_la-vfprintf.lo] Error 1
| make[2]: Leaving directory
`/home/eballetbo/Workspace/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/ust-0.15/snprintf'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory
`/home/eballetbo/Workspace/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/ust-0.15'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| ERROR: Function 'do_compile' failed (see
/home/eballetbo/Workspace/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/lttng-ust-0.15-r2/temp/log.do_compile.24087
for further information)
NOTE: package lttng-ust-0.15-r2: task do_compile: Failed
ERROR: Task 2016
(/home/eballetbo/Workspace/yocto/meta/recipes-kernel/lttng/lttng-ust_0.15.bb,
do_compile) failed with exit code '1'

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


Re: linux-yocto-rt build fail for sugarbay bsp on grub recipe

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

No.
First I tried without applying the patch by building freetype and then grub as per your suggestion in the thread.
It built.

I will try a fresh build by applying the patch and let you know.

Thanks
Kishore.

-----Original Message-----
From: Hart, Darren
Sent: Wednesday, August 31, 2011 10:00 AM
To: Bodke, Kishore K
Cc: Richard Purdie; yocto@...
Subject: Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

On 08/31/2011 09:51 AM, Bodke, Kishore K wrote:
When I do bitbake freetype followed by bitbake grub , the grub build successfully.

Attached is the freetype.log and grub.log.

It fails if I first build the bitbake grub.

Did you apply the patch I provided?

--
Darren



Thanks
Kishore.

-----Original Message-----
From: Hart, Darren
Sent: Tuesday, August 30, 2011 7:52 PM
To: Richard Purdie
Cc: Bodke, Kishore K; yocto@...
Subject: Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

On 08/30/2011 05:11 PM, Richard Purdie wrote:
On Tue, 2011-08-30 at 16:59 -0700, Bodke, Kishore K wrote:
Hello All,



I am trying to build linux-yocto with rt kernel for sugarbay bsp and
it fails for the grub recipe.



Attached is the build log.



kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^WARN_QA="

WARN_QA="dev-so rpaths debug-deps dev-deps debug-files arch la2
pkgconfig desktop la ldflags perms useless-rpaths"

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^ERROR_QA="

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$



Please let me know what could be the issue.
Could you include the config.log file mentioned in the error report
please?

This should be somewhere like
usr/local/src/crf/test/buildsugarbayrt/tmp/work/x86_64-poky-linux/grub-1.98-r1/*/config.log
I replied with this and a comparison file, but it was rejected due to
being over 200k :(.

Short of it is that Kishore's config.log shows it picking up the
freetype libs from his host system. The patch I proposed adds a DEPENDS
to grub on freetype.

Cheers,

Richard


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

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: linux-yocto-rt build fail for sugarbay bsp on grub recipe

Darren Hart <darren.hart@...>
 

On 08/31/2011 09:51 AM, Bodke, Kishore K wrote:
When I do bitbake freetype followed by bitbake grub , the grub build successfully.

Attached is the freetype.log and grub.log.

It fails if I first build the bitbake grub.

Did you apply the patch I provided?

--
Darren



Thanks
Kishore.

-----Original Message-----
From: Hart, Darren
Sent: Tuesday, August 30, 2011 7:52 PM
To: Richard Purdie
Cc: Bodke, Kishore K; yocto@...
Subject: Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

On 08/30/2011 05:11 PM, Richard Purdie wrote:
On Tue, 2011-08-30 at 16:59 -0700, Bodke, Kishore K wrote:
Hello All,



I am trying to build linux-yocto with rt kernel for sugarbay bsp and
it fails for the grub recipe.



Attached is the build log.



kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^WARN_QA="

WARN_QA="dev-so rpaths debug-deps dev-deps debug-files arch la2
pkgconfig desktop la ldflags perms useless-rpaths"

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^ERROR_QA="

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$



Please let me know what could be the issue.
Could you include the config.log file mentioned in the error report
please?

This should be somewhere like
usr/local/src/crf/test/buildsugarbayrt/tmp/work/x86_64-poky-linux/grub-1.98-r1/*/config.log
I replied with this and a comparison file, but it was rejected due to
being over 200k :(.

Short of it is that Kishore's config.log shows it picking up the
freetype libs from his host system. The patch I proposed adds a DEPENDS
to grub on freetype.

Cheers,

Richard


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

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: linux-yocto-rt build fail for sugarbay bsp on grub recipe

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

When I do bitbake freetype followed by bitbake grub , the grub build successfully.

Attached is the freetype.log and grub.log.

It fails if I first build the bitbake grub.

Thanks
Kishore.

-----Original Message-----
From: Hart, Darren
Sent: Tuesday, August 30, 2011 7:52 PM
To: Richard Purdie
Cc: Bodke, Kishore K; yocto@...
Subject: Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

On 08/30/2011 05:11 PM, Richard Purdie wrote:
On Tue, 2011-08-30 at 16:59 -0700, Bodke, Kishore K wrote:
Hello All,



I am trying to build linux-yocto with rt kernel for sugarbay bsp and
it fails for the grub recipe.



Attached is the build log.



kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^WARN_QA="

WARN_QA="dev-so rpaths debug-deps dev-deps debug-files arch la2
pkgconfig desktop la ldflags perms useless-rpaths"

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^ERROR_QA="

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$



Please let me know what could be the issue.
Could you include the config.log file mentioned in the error report
please?

This should be somewhere like
usr/local/src/crf/test/buildsugarbayrt/tmp/work/x86_64-poky-linux/grub-1.98-r1/*/config.log
I replied with this and a comparison file, but it was rejected due to
being over 200k :(.

Short of it is that Kishore's config.log shows it picking up the
freetype libs from his host system. The patch I proposed adds a DEPENDS
to grub on freetype.

Cheers,

Richard


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

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


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

蔡振军 <caizhenjun@...>
 

Hello All,

         Yesterday I got an error on “task_do_rootfs”. It notice that yocto unable to find package “mio-lib” which I just add to system.However,

the “mio-lib” package is built smoothly with no error. I spend whole day to try to resolve this problem and have no progress indeed.

 

here is the error log:

 

NOTE: Running task 1003 of 1298 (ID: 137, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_fetch)

NOTE: package mio-lib-0.1-r0: task do_fetch: Started

NOTE: package mio-lib-0.1-r0: task do_fetch: Succeeded

NOTE: Running task 1289 of 1298 (ID: 134, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_unpack)

NOTE: package mio-lib-0.1-r0: task do_unpack: Started

NOTE: package mio-lib-0.1-r0: task do_unpack: Succeeded

NOTE: Running task 1290 of 1298 (ID: 135, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_patch)

NOTE: package mio-lib-0.1-r0: task do_patch: Started

NOTE: package mio-lib-0.1-r0: task do_patch: Succeeded

NOTE: Running task 1291 of 1298 (ID: 141, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_populate_lic)

NOTE: Running task 1292 of 1298 (ID: 138, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_configure)

NOTE: package mio-lib-0.1-r0: task do_populate_lic: Started

NOTE: package mio-lib-0.1-r0: task do_configure: Started

NOTE: package mio-lib-0.1-r0: task do_populate_lic: Succeeded

NOTE: package mio-lib-0.1-r0: task do_configure: Succeeded

NOTE: Running task 1293 of 1298 (ID: 139, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_compile)

NOTE: package mio-lib-0.1-r0: task do_compile: Started

NOTE: package mio-lib-0.1-r0: task do_compile: Succeeded

NOTE: Running task 1294 of 1298 (ID: 136, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_install)

NOTE: package mio-lib-0.1-r0: task do_install: Started

NOTE: package mio-lib-0.1-r0: task do_install: Succeeded

NOTE: Running task 1295 of 1298 (ID: 140, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_package)

NOTE: package mio-lib-0.1-r0: task do_package: Started

NOTE: package mio-lib-0.1-r0: task do_package: Succeeded

NOTE: Running task 1296 of 1298 (ID: 142, /home/ll/work/optimus/meta-imx28/recipes-extended/mio-lib/mio-lib_0.1.bb, do_package_write_rpm)

NOTE: package mio-lib-0.1-r0: task do_package_write_rpm: Started

NOTE: package mio-lib-0.1-r0: task do_package_write_rpm: Succeeded

NOTE: Running task 1297 of 1298 (ID: 8, /home/ll/work/optimus/meta-imx28/recipes-core/images/core-image-imx28.bb, do_rootfs)

NOTE: package core-image-imx28-1.0-r0: task do_rootfs: Started

ERROR: Function 'do_rootfs' failed (see /home/ll/work/optimus-imx28-build/tmp/work/mx28evk-insigma-linux-gnueabi/core-image-imx28-1.0-r0/temp/log.do_rootfs.17769 for further information)

ERROR: Logfile of failure stored in: /home/ll/work/optimus-imx28-build/tmp/work/mx28evk-insigma-linux-gnueabi/core-image-imx28-1.0-r0/temp/log.do_rootfs.17769

Log data follows:

| Generating solve db for /home/ll/work/optimus-imx28-build/tmp/deploy/rpm/mx28evk...

|    total:               1      0.000000 MB      0.767100 secs

|    fingerprint:       312      0.002844 MB      0.032388 secs

|    install:           104      0.000000 MB      0.217042 secs

|    dbadd:             104      0.000000 MB      0.207174 secs

|    dbget:            1021      0.000000 MB      0.001158 secs

|    dbput:             104      0.488224 MB      0.136671 secs

|    readhdr:          1041      0.982912 MB      0.169746 secs

|    hdrload:           520      1.447744 MB      0.004313 secs

|    hdrget:          18405      0.000000 MB      0.018025 secs

| Generating solve db for /home/ll/work/optimus-imx28-build/tmp/deploy/rpm/armv5te...

|    total:               1      0.000000 MB      7.642331 secs

|    fingerprint:      1677      0.044516 MB      0.138877 secs

|    install:           559      0.000000 MB      1.274561 secs

|    dbadd:             559      0.000000 MB      1.239767 secs

|    dbget:           17048      0.000000 MB      0.011212 secs

|    dbput:             559      4.296544 MB      1.043691 secs

|    readhdr:          5591      8.601994 MB      4.089920 secs

|    hdrload:          3343     17.026066 MB      0.045179 secs

|    hdrget:         102529      0.000000 MB      0.118865 secs

| Generating solve db for /home/ll/work/optimus-imx28-build/tmp/deploy/rpm/all...

|    total:               1      0.000000 MB      0.294207 secs

|    fingerprint:        18      0.000024 MB      0.000412 secs

|    install:             6      0.000000 MB      0.064882 secs

|    dbadd:               6      0.000000 MB      0.058694 secs

|    dbget:              19      0.000000 MB      0.000081 secs

|    dbput:               6      0.018576 MB      0.005771 secs

|    readhdr:            61      0.037992 MB      0.145214 secs

|    hdrload:            30      0.055128 MB      0.000311 secs

|    hdrget:            983      0.000000 MB      0.001172 secs

| Generating solve db for /home/ll/work/optimus-imx28-build/tmp/deploy/rpm/all...

|    total:               1      0.000000 MB      0.117318 secs

|    fingerprint:        18      0.000024 MB      0.000665 secs

|    install:             6      0.000000 MB      0.062555 secs

|    dbadd:               6      0.000000 MB      0.055995 secs

|    dbget:              19      0.000000 MB      0.000080 secs

|    dbput:               6      0.018576 MB      0.005078 secs

|    readhdr:            61      0.037992 MB      0.000263 secs

|    hdrload:            30      0.055128 MB      0.000242 secs

|    hdrget:            983      0.000000 MB      0.000723 secs

| Processing task-core-boot...

| Processing u-boot...

| Processing mio-lib...

| Unable to find package mio-lib (mio-lib)!

| ERROR: Function 'do_rootfs' failed (see /home/ll/work/optimus-imx28-build/tmp/work/mx28evk-insigma-linux-gnueabi/core-image-imx28-1.0-r0/temp/log.do_rootfs.17769 for further information)

NOTE: package core-image-imx28-1.0-r0: task do_rootfs: Failed

ERROR: Task 8 (/home/ll/work/optimus/meta-imx28/recipes-core/images/core-image-imx28.bb, do_rootfs) failed with exit code '1'

ERROR: '/home/ll/work/optimus/meta-imx28/recipes-core/images/core-image-imx28.bb' failed

 

    Some information maybe helpful I acquire in my terrible trip. Add  “–v” option to bitbake ,log show unable to find package name from solve

db. Use  “grep –rn”  to check, it show as below:

 

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

Binary file ./armv5te/solvedb/Requirename matches

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

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

 

         I use another package which reside in yocto originally named “libaio” to compare.by changing something in bb file and makefile, the

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 cann’t find real reason for this error. What happen to me?

 

Best reagards

feye

 

蔡振军

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

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

电话-138 6745 1910

 


Re: linux-yocto-rt build fail for sugarbay bsp on grub recipe

Darren Hart <darren.hart@...>
 

On 08/30/2011 05:11 PM, Richard Purdie wrote:
On Tue, 2011-08-30 at 16:59 -0700, Bodke, Kishore K wrote:
Hello All,



I am trying to build linux-yocto with rt kernel for sugarbay bsp and
it fails for the grub recipe.



Attached is the build log.



kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^WARN_QA="

WARN_QA="dev-so rpaths debug-deps dev-deps debug-files arch la2
pkgconfig desktop la ldflags perms useless-rpaths"

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^ERROR_QA="

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$



Please let me know what could be the issue.
Could you include the config.log file mentioned in the error report
please?

This should be somewhere like
usr/local/src/crf/test/buildsugarbayrt/tmp/work/x86_64-poky-linux/grub-1.98-r1/*/config.log
I replied with this and a comparison file, but it was rejected due to
being over 200k :(.

Short of it is that Kishore's config.log shows it picking up the
freetype libs from his host system. The patch I proposed adds a DEPENDS
to grub on freetype.

Cheers,

Richard


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

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: linux-yocto-rt build fail for sugarbay bsp on grub recipe

Darren Hart <darren.hart@...>
 

Kishore, can you try this patch? You can just checkout this branch in
your meta-intel repository after adding the meta-intel-contrib remote,
or you can add it manually.

http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/commit/?h=dvhart/grubfix&id=60652a51878cbd0327c5f828acdbb73e31caafba

Thanks,

Darren

On 08/30/2011 06:39 PM, Darren Hart wrote:
On 08/30/2011 05:11 PM, Richard Purdie wrote:
On Tue, 2011-08-30 at 16:59 -0700, Bodke, Kishore K wrote:
Hello All,



I am trying to build linux-yocto with rt kernel for sugarbay bsp and
it fails for the grub recipe.



Attached is the build log.



kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^WARN_QA="

WARN_QA="dev-so rpaths debug-deps dev-deps debug-files arch la2
pkgconfig desktop la ldflags perms useless-rpaths"

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
bitbake -e | egrep "^ERROR_QA="

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$



Please let me know what could be the issue.
Could you include the config.log file mentioned in the error report
please?
I've attached mine and Kishore's. Mine builds grub, while his does not.

I noticed that Kishore's config.log differs from mine in some configure tests. For example:

Mine contains (config.log-dvhart):

configure:8739: checking for __bswapsi2
configure:8739: gcc -o conftest -O2 -pipe -g -feliminate-unused-debug-types -DGRUB_MACHINE_PCBIOS=1 -Wall -W -Wshadow -Wpointer-arith -Wmissing-prototypes -Wundef -Wstrict-prototypes -g -falign-jumps=1 -falign-loops=1 -falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow -fno-dwarf2-cfi-asm -m32 -fno-stack-protector -mno-stack-arg-probe -Werror -nostdlib -Wl,--defsym,___main=0x8100 -Wl,--defsym,abort=main -Wno-error -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -m32 conftest.c -lgcc >&5
In file included from /usr/include/features.h:387,
from /usr/include/limits.h:27,
from /usr/lib/gcc/x86_64-linux-gnu/4.4.5/include-fixed/limits.h:122,
from /usr/lib/gcc/x86_64-linux-gnu/4.4.5/include-fixed/syslimits.h:7,
from /usr/lib/gcc/x86_64-linux-gnu/4.4.5/include-fixed/limits.h:11,
from conftest.c:62:
/usr/include/gnu/stubs.h:7: fatal error: gnu/stubs-32.h: No such file or directory compilation terminated.
configure:8739: $? = 1


While there is no reference to stubs.h in Kishore's config.log (confi-1.log):

configure:8739: checking for __bswapsi2
configure:8739: gcc -o conftest -O2 -pipe -g -feliminate-unused-debug-types -DGRUB_MACHINE_PCBIOS=1 -Wall -W -Wshadow -Wpointer-arith -Wmissing-prototypes -Wundef -Wstrict-prototypes -g -falign-jumps=1 -falign-loops=1 -falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow -fno-dwarf2-cfi-asm -m32 -fno-stack-protector -Werror -nostdlib -Wl,--defsym,___main=0x8100 -Wl,--defsym,abort=main -Wno-error -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -m32 conftest.c -lgcc >&5
conftest.c:75: warning: function declaration isn't a prototype
/usr/bin/ld: warning: cannot find entry symbol _start; defaulting to 00000000080480c0
configure:8739: $? = 0
configure:8739: result: yes


I also found that Kishore's config.log includes:
freetype_cflags='-I/usr/include/freetype2'
freetype_libs='-lfreetype -lz'

While mine includes:
freetype_cflags='-I/build/poky/sugarbay/tmp/sysroots/sugarbay/usr/include/freetype2 -I/build/poky/sugarbay/tmp/sysroots/sugarbay/usr/include'
freetype_libs='-L/build/poky/sugarbay/tmp/sysroots/sugarbay/usr/lib -lfreetype'

This would certainly be cause for a QA test failure.

Perhaps a DEPENDS=freetype in the grub recipe is in order?

Alternatively, we could see about configuring it without freetype.

Kishore, can you check to see if freetype is built on your system? Should be located at:

/usr/local/src/crf/test/buildsugarbayrt/tmp/work/x86_64-poky-linux/freetype-2.4.6-r0

Kishore, finally, we can confirm this is the problem by having you try this:
$ bitbake freetype
$ bitbake grub

I suspect this will complete.


This should be somewhere like
usr/local/src/crf/test/buildsugarbayrt/tmp/work/x86_64-poky-linux/grub-1.98-r1/*/config.log

Cheers,

Richard

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel