public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Shenglei Zhang" <shenglei.zhang@intel.com>,
	edk2-devel@lists.01.org
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [PATCH 06/10] OvmfPkg/README: Remove UNIXGCC
Date: Fri, 1 Feb 2019 14:47:25 +0100	[thread overview]
Message-ID: <11bb68ea-73ac-718e-23d8-def2c0f45db0@redhat.com> (raw)
In-Reply-To: <90f309f1-204b-49fa-189a-4144fef9c322@redhat.com>

On 02/01/19 10:50, Philippe Mathieu-Daudé wrote:
> Hi,
> 
> On 2/1/19 6:34 AM, Shenglei Zhang wrote:
>> Remove content related to UNIXGCC in README.
>> https://bugzilla.tianocore.org/show_bug.cgi?id=1377
>>
>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Cc: Anthony Perard <anthony.perard@citrix.com>
>> Cc: Julien Grall <julien.grall@linaro.org>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Shenglei Zhang <shenglei.zhang@intel.com>
>> ---
>>  OvmfPkg/README | 19 -------------------
>>  1 file changed, 19 deletions(-)
>>
>> diff --git a/OvmfPkg/README b/OvmfPkg/README
>> index 68ce0750af..c014d07bfb 100644
>> --- a/OvmfPkg/README
>> +++ b/OvmfPkg/README
>> @@ -402,25 +402,6 @@ main firmware (MAINFV) into RAM memory at address 0x800000. The
>>  remaining OVMF firmware then uses this decompressed firmware
>>  volume image.
>>  
>> -=== UNIXGCC Debug ===
>> -
>> -If you build with the UNIXGCC toolchain, then debugging will be disabled
>> -due to larger image sizes being produced by the UNIXGCC toolchain. The
>> -first choice recommendation is to use GCC48 or newer instead.
>> -
>> -If you must use UNIXGCC, then you can override the build options for
>> -particular libraries and modules in the .dsc to re-enable debugging
>> -selectively. For example:
>> -  [Components]
>> -  OvmfPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf {
>> -    <BuildOptions>
>> -      GCC:*_*_*_CC_FLAGS             = -UMDEPKG_NDEBUG
>> -  }
>> -  MdeModulePkg/Universal/BdsDxe/BdsDxe.inf {
>> -    <BuildOptions>
>> -      GCC:*_*_*_CC_FLAGS             = -UMDEPKG_NDEBUG
>> -  }
>> -
>>  === UEFI Windows 7 & Windows 2008 Server ===
>>  
>>  * One of the '-vga std' and '-vga qxl' QEMU options should be used.
>>
> 
> Doesn't it make sense to squash this commit with the previous one as
> "OvmfPkg: Remove UNIXGCC"?

Good point.

Thanks
Laszlo


  reply	other threads:[~2019-02-01 13:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01  5:34 [PATCH 00/10] Remove unused tool chain configuration Shenglei Zhang
2019-02-01  5:34 ` [PATCH 01/10] BaseTools/tools_def.template: Remove VS2003 and VS2005 Shenglei Zhang
2019-02-01  5:34 ` [PATCH 02/10] OptionRomPkg/ReadMe.txt: Remove VS2005 Shenglei Zhang
2019-02-01  5:34 ` [PATCH 03/10] BaseTools/tools_def.template: Remove DDK3790 Shenglei Zhang
2019-02-01  5:34 ` [PATCH 04/10] BaseTools/tools_def.template: Remove UNIXGCC Shenglei Zhang
2019-02-01  8:52   ` Laszlo Ersek
2019-02-01  5:34 ` [PATCH 05/10] OvmfPkg: Remove UNIXGCC in DSC files Shenglei Zhang
2019-02-01  8:53   ` Laszlo Ersek
2019-02-01  5:34 ` [PATCH 06/10] OvmfPkg/README: Remove UNIXGCC Shenglei Zhang
2019-02-01  8:55   ` Laszlo Ersek
2019-02-01  9:50   ` Philippe Mathieu-Daudé
2019-02-01 13:47     ` Laszlo Ersek [this message]
2019-02-01  5:34 ` [PATCH 07/10] BaseTools: Update MYTOOLS Shenglei Zhang
2019-02-01  5:34 ` [PATCH 08/10] BaseTools/tools_def.template: Remove ELFGCC Shenglei Zhang
2019-02-01  8:56   ` Laszlo Ersek
2019-02-01  5:34 ` [PATCH 09/10] BaseTools/tools_def.template: Remove CYGGCC Shenglei Zhang
2019-02-01  8:58   ` Laszlo Ersek
2019-02-01  5:34 ` [PATCH 10/10] OptionRomPkg/ReadMe.txt: " Shenglei Zhang
2019-02-01 10:25 ` [PATCH 00/10] Remove unused tool chain configuration Ard Biesheuvel
2019-02-01 13:23   ` 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=11bb68ea-73ac-718e-23d8-def2c0f45db0@redhat.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