From: Blibbet <blibbet@gmail.com>
To: chipsec@lists.01.org
Subject: Re: CHIPSEC error when building LUV image
Date: Thu, 22 Oct 2015 10:13:39 -0700 [thread overview]
Message-ID: <56291943.9090001@gmail.com> (raw)
In-Reply-To: <56215752.7030304@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
You might also want to ask on the LUV list about this build error. This
might be a LUV-centric issue. The LUV team ported CHIPSEC to their
system. The CHIPSEC team -- AFAIK -- has/have been using an alternative
Linux live-boot solution until recently, so the LUV team may be better
to answer a LUV-centric build question than the CHIPSEC team.
I wonder:
Does a 32- and 64-bit LUV behave differently, w/r/t firmware tests, on
different architectures?
Does CHIPSEC behave differently on when built 32- or 64-bit -- on Linux
or Windows or UEFI?
Perhaps we need LUV64-live and LUV32-live to solve??
Gettting more confused as I type, so I'll stop typing. :-)
On 10/16/2015 01:00 PM, Blibbet wrote:
> 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
>
>
prev parent reply other threads:[~2015-10-22 17:13 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
2015-10-22 17:13 ` Blibbet [this message]
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=56291943.9090001@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).