public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "wang xiaofeng" <winggundum82@163.com>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: fail to build OVMF with GCC62 in Ubuntu
Date: Tue, 22 Aug 2017 16:55:28 +0800 (CST)	[thread overview]
Message-ID: <6ead7a5e.8108.15e09275c40.Coremail.winggundum82@163.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14D774239@shsmsx102.ccr.corp.intel.com>

thanks for sharing information  , Liming








At 2017-08-22 16:45:33, "Gao, Liming" <liming.gao@intel.com> wrote:
>You can check OvmfPkg\build.sh. The default tool chain is GCC5, not GCC46. 
>
>Your build uses GCC46 tool chain with GCC62, which is wrong. 
>
>>-----Original Message-----
>>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>>wang xiaofeng
>>Sent: Tuesday, August 22, 2017 4:26 PM
>>To: edk2-devel@lists.01.org
>>Subject: [edk2] fail to build OVMF with GCC62 in Ubuntu
>>
>>Hello,
>>    I just try to build OVMF with GCC62 in Ubuntu. The following errors shows:
>>
>>GenFw: ERROR 3000: Invalid
>>
>>
>>/home/jerry/EDKII/edk2/Build/OvmfIa32/DEBUG_GCC46/IA32/OvmfPkg/Sec
>>/SecMain/DEBUG/SecMain.dll unsupported ELF EM_386 relocation 0x4.
>>
>>  From tools_def.txt it seems the latest support GCC by basetools is GCC 5?
>>And the default is GCC4.6?
>>
>>  So I need to install a lower revision of GCC?
>>
>>
>>
>>
>>
>>_______________________________________________
>>edk2-devel mailing list
>>edk2-devel@lists.01.org
>>https://lists.01.org/mailman/listinfo/edk2-devel
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel

      parent reply	other threads:[~2017-08-22  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22  8:26 fail to build OVMF with GCC62 in Ubuntu wang xiaofeng
     [not found] ` <4A89E2EF3DFEDB4C8BFDE51014F606A14D774239@shsmsx102.ccr.corp.intel.com>
2017-08-22  8:55   ` wang xiaofeng [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-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=6ead7a5e.8108.15e09275c40.Coremail.winggundum82@163.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