oe-chipsec.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dey, Megha <megha.dey@intel.com>
To: chipsec@lists.01.org
Subject: CHIPSEC error when building LUV image
Date: Wed, 14 Oct 2015 17:08:52 +0000	[thread overview]
Message-ID: <C440BA31B54DCD4AAC682D2365C8FEE7C44609@ORSMSX111.amr.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3194 bytes --]

Hi,



I was trying to build the Linux UEFI Validation (LUV) image for 32 bit systems. The LUV image incorporates the CHIPSEC test suite as well.



I get the following warnings and errors during build time:

------------------------------------------------------------------------------------------------------------

CC

[M]  /home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec_km.o

/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec_km.c: In function 'patch_apply_ucode':

/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec_km.c:573:14: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]

  ucode_start=(unsigned long long) ucode_buf;

              ^

/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec_km.c: In function 'd_ioctl':

/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec_km.c:946:3: warning: right shift count >= width of type

   ptr[1] = (uint32_t)(dtr.base >> 32);

   ^

/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec_km.c:1365:17: warning: left shift count >= width of type

                 ptr[0] = first | (second << 32);

                 ^

/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec_km.c:1405:17: warning: right shift count >= width of type

                 iowrite32( ( value >> 32 ) & 0xFFFFFFFF, ioaddr );

                 ^

/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec_km.c:951:10: warning: 'dt_pa.u.high' may be used uninitialized in this function [-Wmaybe-uninitialized]

   ptr[3] = dt_pa.u.high;

          ^

  LD

[M]  /home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec.o

i586-oe-linux-ld.bfd: i386:x86-64 architecture of input file `/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/amd64/cpu.o' is incompatible with i386 output

make[3]: ***

[/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux/chipsec.o] Error 1

make[2]: ***

[_module_/home/megha/luv_new/build/tmp/work/qemux86-oe-linux/chipsec/git-r0/git/source/drivers/linux] Error 2

make[2]: Leaving directory

`/home/megha/luv_new/build/tmp/work-shared/qemux86/kernel-build-artifacts'

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory

`/home/megha/luv_new/build/tmp/work-shared/qemux86/kernel-source'

make: *** [chipsec] Error 2

------------------------------------------------------------------------------------------------------------------------



I wanted to know if the CHIPSEC test suite builds and runs on 32 bit platforms? (in which case there is a problem with the CHIPSEC recipe in LUV).

Else, any pointers as to why I see these warnings and errors?

Any help would be appreciated!!



Thanks,

Megha


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 7339 bytes --]

             reply	other threads:[~2015-10-14 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 17:08 Dey, Megha [this message]
2015-10-16 20:00 ` CHIPSEC error when building LUV image Blibbet
2015-10-22 17:13   ` Blibbet

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=C440BA31B54DCD4AAC682D2365C8FEE7C44609@ORSMSX111.amr.corp.intel.com \
    --to=megha.dey@intel.com \
    --cc=chipsec@lists.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).