GithubHelp home page GithubHelp logo

Comments (7)

jordanrh1 avatar jordanrh1 commented on July 24, 2024

Was building fine (except for -Wexpansion-to-defined warnings) as of d979cae.

from ms-tpm-20-ref.

amarochk avatar amarochk commented on July 24, 2024

TravisCI build passes for x64 and i386 Linux build configurations. I'm quite confident that the merge did not contain any changes that could specifically affect the ARM architecture. So, something is probably wrong with your build environment. In particular, both RSA_PRIVATE_SIZE and PRIVATE_VENDOR_SPECIFIC_BYTES are defined in Implementation.h. And the latter is included by all reference implementation source files.

from ms-tpm-20-ref.

jordanrh1 avatar jordanrh1 commented on July 24, 2024

Have you tried building for OPTEE with ARM64? Is OPTEE build succeeding for you?

TA_DEV_KIT_DIR=path/to/export-ta_arm64 TA_CPU=cortex-a53 CROSS_COMPILE=aarch64-linux-gnu- \
make -C ms-tpm-20-ref/Samples/ARM32-FirmwareTPM/optee_ta/fTPM

from ms-tpm-20-ref.

amarochk avatar amarochk commented on July 24, 2024

from ms-tpm-20-ref.

jbech-linaro avatar jbech-linaro commented on July 24, 2024

Inline with what @jordanrh1 said, I experience the same issues (arm32 build) when following the instructions as provided by this git. I've bisected the commit that introduces the build regression to:

5847c02ff793114343dc18e92e60e2919fadc0b8 is the first bad commit                                                                                                                                                   
commit 5847c02ff793114343dc18e92e60e2919fadc0b8                                                                                                                                                                    
Author: Andrey Marochko <[email protected]>                                                                                                                                                            
Date:   Fri Feb 8 13:28:00 2019 -0800                                                                                                                                                                              
                                                                                                                                                                                                                   
    Rev. 1.52.                                                                                                                                                                                                     
    - X.509 support                                                                                                                                                                                                
    - RSA keys representation optimized                                                                                                                                                                            
                                                                                                                                                                                                                   
:100644 100644 883ea24e738d315d3d951c111545ce2cbb93fa35 8c151f4a8437f069cc0abf524b701d416eb44b18 M      .gitignore                                                                                                 
:040000 040000 fa7aac36d722c87f95e1ca5f77066660e2b3e26f 69b4c619b2c0eb94beeb3896bf020d156b902229 M      TPMCmd

Everything prior to this works fine when following the instructions in this git. That commit is huge, so I haven't been able to figure out what is going wrong.

from ms-tpm-20-ref.

jbech-linaro avatar jbech-linaro commented on July 24, 2024

I'm not sure how this is supposed to work, but it looks like there are lots of differences between these two files

./Samples/ARM32-FirmwareTPM/optee_ta/fTPM/reference/include/Implementation.h
./TPMCmd/tpm/include/Implementation.h

What is the reason for having them both? Should they be more or less identical? They looked much more similar on the old version (that doesn't have a build regression). It's clear that we get undeclared variables when compiling the optee_ta, since indeed Implementation.h are missing many of the defines that are being used.

from ms-tpm-20-ref.

amarochk avatar amarochk commented on July 24, 2024

Hi Joakim,

Yes, the reason of the build failure is that the OPTEE source tree uses a (slightly) modified copy of Implementation.h instead of including the latter and then redefining some of its macro symbols (mostly supported algorithms, AFAIK). Devs who maintain the OPTEE code are aware of the issue and were going to fix it. Meanwhile you could try to replace the OPTEE Implementation.h in with the new one. Also, if it matters for your build, you may want to make sure that the set of supported SHA algorithms, ECC curves, and RSA key sizes matches what is in the current OPTEE version.

from ms-tpm-20-ref.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.