oe-chipsec.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Blibbet <blibbet@gmail.com>
To: chipsec@lists.01.org
Subject: Re: CHIPSEC error when building LUV image
Date: Fri, 16 Oct 2015 13:00:18 -0700	[thread overview]
Message-ID: <56215752.7030304@gmail.com> (raw)
In-Reply-To: <C440BA31B54DCD4AAC682D2365C8FEE7C44609@ORSMSX111.amr.corp.intel.com>

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

On 10/14/2015 10:08 AM, Dey, Megha wrote:
> I wanted to know if the CHIPSEC test suite builds and runs on 32 bit
platforms?

I don't know the cause of your problems, but the CHIPSEC PDF says
Windows x86/x64, and says that on Linux, Debian is the only one
explicitly listed with 32-bit, Fedora and Ubuntu say 64-bit, LUV entry
does not specify.

If possible to build LUV with LLVM clang, you might try that, it gives
much better warnings than GCC.

I've only built CHIPSEC on Linux, and only for 64-bit targets. And I'm
afraid I can't help building a local LUV at the moment, sorry.

Lee



  reply	other threads:[~2015-10-16 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 17:08 CHIPSEC error when building LUV image Dey, Megha
2015-10-16 20:00 ` Blibbet [this message]
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=56215752.7030304@gmail.com \
    --to=blibbet@gmail.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).