All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <darren.hart@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: linux-yocto-rt build fail for sugarbay bsp on grub recipe
Date: Wed, 31 Aug 2011 19:51:33 +0100	[thread overview]
Message-ID: <1314816693.5939.476.camel@rex> (raw)
In-Reply-To: <4E5D90C3.7090607@intel.com>

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



  parent reply	other threads:[~2011-08-31 18:51 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
2011-08-31 18:51     ` Richard Purdie [this message]
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=1314816693.5939.476.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=darren.hart@intel.com \
    --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.