public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: 'Leif Lindholm' <leif.lindholm@linaro.org>
Cc: "'edk2-devel@lists.01.org'" <edk2-devel@lists.01.org>,
	"Feng, YunhuaX" <yunhuax.feng@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>,
	"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [Patch 4/4 V3] BaseTools: Update Makefile to support FFS file generation
Date: Thu, 7 Dec 2017 09:59:27 +0000	[thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D51F46E1C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <B9726D6DCCFB8B4CA276A9169B02216D51F45F17@SHSMSX103.ccr.corp.intel.com>

Hi Leif,

Please help to check whether this patch " [edk2] [PATCH] BaseTools: Fix GenSec can't found the depex file" can fix it. thanks a lot.

Best Regards,
Zhu Yonghong

-----Original Message-----
From: Zhu, Yonghong 
Sent: Thursday, December 07, 2017 9:00 AM
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: edk2-devel@lists.01.org; Feng, YunhuaX <yunhuax.feng@intel.com>; Gao, Liming <liming.gao@intel.com>; Zhu, Yonghong <yonghong.zhu@intel.com>
Subject: RE: [edk2] [Patch 4/4 V3] BaseTools: Update Makefile to support FFS file generation

Thanks Leif.  I will provide patch to fix it soon.

Best Regards,
Zhu Yonghong


-----Original Message-----
From: Leif Lindholm [mailto:leif.lindholm@linaro.org]
Sent: Thursday, December 07, 2017 2:24 AM
To: Zhu, Yonghong <yonghong.zhu@intel.com>
Cc: edk2-devel@lists.01.org; Feng, YunhuaX <yunhuax.feng@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: Re: [edk2] [Patch 4/4 V3] BaseTools: Update Makefile to support FFS file generation

Hi Yonghong,

I'm afraid I have come across an issue with this one as well:
When trying to build OptionRomPkg/Bus/Usb/UsbNetworking/Ax88772b
into a platform (edk2-platforms/Platform/Hisilicon/HiKey/), GenSec fails with:

Generating FVMAIN FV
####################################
########################################
########Return Value = 2
GenSec: ERROR 0001: Error opening file
  /work/git/tianocore/Build/HiKey/RELEASE_GCC5/AARCH64/OptionRomPkg/Bus/Usb/UsbNetworking/Ax88772b/Ax88772b/OUTPUT/Ax88772b.depex
GenSec: ERROR 2000: Status is not successful

If I revert commit 37de70b7, the platform builds successfully again.
D03 and D05 platforms also appear to have issues with this, but in that case due to drivers in edk2-non-osi.

/
    Leif

On Wed, Nov 29, 2017 at 10:02:06PM +0800, Yonghong Zhu wrote:
> Update Makefile to support FFS file generation with new build option 
> --genfds-multi-thread.
> 
> Cc: Liming Gao <liming.gao@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
> Signed-off-by: Yunhua Feng <yunhuax.feng@intel.com>
> ---
>  BaseTools/Source/Python/AutoGen/AutoGen.py         |  23 ++-
>  BaseTools/Source/Python/AutoGen/GenMake.py         |  90 ++++++++-
>  BaseTools/Source/Python/Common/GlobalData.py       |   1 +
>  BaseTools/Source/Python/GenFds/AprioriSection.py   |  14 +-
>  BaseTools/Source/Python/GenFds/CompressSection.py  |  10 +-
>  BaseTools/Source/Python/GenFds/DataSection.py      |  37 ++--
>  BaseTools/Source/Python/GenFds/DepexSection.py     |   6 +-
>  BaseTools/Source/Python/GenFds/EfiSection.py       |  78 +++++---
>  BaseTools/Source/Python/GenFds/Fd.py               |  24 ++-
>  BaseTools/Source/Python/GenFds/FfsFileStatement.py |   4 +-
>  BaseTools/Source/Python/GenFds/FfsInfStatement.py  | 202 ++++++++++++---------
>  BaseTools/Source/Python/GenFds/Fv.py               | 189 ++++++++++---------
>  BaseTools/Source/Python/GenFds/FvImageSection.py   |   8 +-
>  BaseTools/Source/Python/GenFds/GenFds.py           |  20 ++
>  .../Source/Python/GenFds/GenFdsGlobalVariable.py   | 174 ++++++++++++++----
>  BaseTools/Source/Python/GenFds/GuidSection.py      | 168 +++++++++--------
>  .../Source/Python/GenFds/OptRomFileStatement.py    |   4 +-
>  .../Source/Python/GenFds/OptRomInfStatement.py     |  12 +-
>  BaseTools/Source/Python/GenFds/OptionRom.py        |  25 +--
>  BaseTools/Source/Python/GenFds/Region.py           |  49 +++--
>  BaseTools/Source/Python/GenFds/Section.py          |   4 +-
>  BaseTools/Source/Python/GenFds/UiSection.py        |   5 +-
>  BaseTools/Source/Python/GenFds/VerSection.py       |   9 +-
>  BaseTools/Source/Python/build/build.py             |  48 ++++-
>  24 files changed, 793 insertions(+), 411 deletions(-)


  reply	other threads:[~2017-12-07  9:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 14:02 [Patch 0/4 V3] BaseTools: Enable multiple thread to generate FFS file Yonghong Zhu
2017-11-29 14:02 ` [Patch 1/4 V3] BaseTools: GenFfs support to get alignment value from SectionFile Yonghong Zhu
2017-11-29 14:02 ` [Patch 2/4 V3] BaseTools: Update Trim to generate VfrBinOffset Binary Yonghong Zhu
2017-11-29 14:02 ` [Patch 3/4 V3] BaseTools: Update Gensec to set PROCESSING_REQUIRED value Yonghong Zhu
2017-12-05 11:53   ` Leif Lindholm
2017-12-05 13:56     ` Zhu, Yonghong
2017-11-29 14:02 ` [Patch 4/4 V3] BaseTools: Update Makefile to support FFS file generation Yonghong Zhu
2017-12-06 18:23   ` Leif Lindholm
2017-12-07  0:59     ` Zhu, Yonghong
2017-12-07  9:59       ` Zhu, Yonghong [this message]
2017-12-01  6:13 ` [Patch 0/4 V3] BaseTools: Enable multiple thread to generate FFS file Gao, Liming

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=B9726D6DCCFB8B4CA276A9169B02216D51F46E1C@SHSMSX103.ccr.corp.intel.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