All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: linux-yocto-rt build fail for sugarbay bsp on grub recipe
Date: Tue, 30 Aug 2011 18:46:08 -0700	[thread overview]
Message-ID: <4E5D9260.4080708@intel.com> (raw)
In-Reply-To: <4E5D90C3.7090607@intel.com>


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


  reply	other threads:[~2011-08-31  1:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 23:59 linux-yocto-rt build fail for sugarbay bsp on grub recipe Bodke, Kishore K
2011-08-31  0:11 ` Richard Purdie
2011-08-31  1:39   ` Darren Hart
2011-08-31  1:46     ` Darren Hart [this message]
2011-08-31 18:51     ` Richard Purdie
2011-08-31  2:51   ` Darren Hart
2011-08-31 16:51     ` Bodke, Kishore K
2011-08-31 17:00       ` Darren Hart
2011-08-31 17:02         ` Bodke, Kishore K

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E5D9260.4080708@intel.com \
    --to=darren.hart@intel.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.