public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: yuchenlin <yuchenlin@synology.com>
To: "Chen, Farrah" <farrah.chen@intel.com>
Cc: edk2-devel@lists.01.org
Subject: Re: OVMF compile error
Date: Wed, 07 Nov 2018 13:37:17 +0800	[thread overview]
Message-ID: <162a89e7ad90977ad1525cccc4973d38@synology.com> (raw)
In-Reply-To: <1B925CC0CD9F3341B32D442251E7E1DC3D8699E9@shsmsx102.ccr.corp.intel.com>

On 2018-11-07 12:39, Chen, Farrah wrote:
> Hi,
> 
> When we build OVMF with the latest commit:
> 328409ce8de7f318ee9c929b64302bd361cd1dbd, we met below error:
> 
> OvmfPkg/build.sh -a X64 -n 8
> 
> ...........................
> 
> OK
> make[1]: Leaving directory `/home/fan/edk2/BaseTools/Tests'
> make: Leaving directory `/home/fan/edk2/BaseTools'
> Running edk2 build for OvmfPkgX64
> Build environment: 
> Linux-3.10.0-862.el7.x86_64-x86_64-with-redhat-7.5-Maipo
> Build start time: 12:13:50, Nov.07 2018
> 
> WORKSPACE        = /home/fan/edk2
> ECP_SOURCE       = /home/fan/edk2/EdkCompatibilityPkg
> EDK_SOURCE       = /home/fan/edk2/EdkCompatibilityPkg
> EFI_SOURCE       = /home/fan/edk2/EdkCompatibilityPkg
> EDK_TOOLS_PATH   = /home/fan/edk2/BaseTools
> CONF_PATH        = /home/fan/edk2/Conf
> 
> 
> Architecture(s)  = X64
> Build target     = DEBUG
> Toolchain        = GCC48
> 
> Active Platform          = /home/fan/edk2/OvmfPkg/OvmfPkgX64.dsc
> Flash Image Definition   = /home/fan/edk2/OvmfPkg/OvmfPkgX64.fdf
> 
> Processing meta-data .......
> 
> build.py...
> /home/fan/edk2/CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf(31):
> error 000E: File/directory not found in workspace
>         /home/fan/edk2/CryptoPkg/Library/OpensslLib/openssl/e_os.h
> 
> 
> - Failed -
> Build end time: 12:13:59, Nov.07 2018
> Build total time: 00:00:09
> 
> 
> 
> 
> Thanks,
> Fan
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


Hi,

Try:

git submodule init
git submodule update --recursive

And build it again.

Thanks,
yuchenlin


  reply	other threads:[~2018-11-07  5:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  4:39 OVMF compile error Chen, Farrah
2018-11-07  5:37 ` yuchenlin [this message]
2018-11-07 10:00   ` Chen, Farrah
  -- strict thread matches above, loose matches on Subject: below --
2017-07-06  8:36 Chen, Farrah
2017-07-06  8:47 ` Laszlo Ersek
2017-07-07  2:12   ` Chen, Farrah
2017-08-11  2:46 ` Chen, Farrah
2017-08-11 11:21   ` Laszlo Ersek
     [not found] <1B925CC0CD9F3341B32D442251E7E1DC36D93C55@shsmsx102.ccr.corp.intel.com>
2016-09-14  7:21 ` Chen, Farrah

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-list 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=162a89e7ad90977ad1525cccc4973d38@synology.com \
    --to=devel@edk2.groups.io \
    /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