public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Richardson, Brian" <brian.richardson@intel.com>
To: "Shragai, Yaron" <yshragai@draper.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: build failure trying to build gcc cross-compiler
Date: Mon, 12 Dec 2016 23:29:59 +0000	[thread overview]
Message-ID: <80AC2BAA3152784F98F581129E5CF5AF664EDF59@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <6C71D887621F9645B5F35F45F555909CEE0750@mbx2.draper.com>

Actually, you should have ended up here ...
https://github.com/tianocore/tianocore.github.io/wiki/Common-instructions 

The Ubuntu instructions link to 'Common instructions for Linux' (not UNIX). I will make some wiki edits to clarify this.

Thanks ... br
---
Brian Richardson, Senior Technical Marketing Engineer, Intel Software
brian.richardson@intel.com -- @intel_Brian (Twitter & WeChat)
https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson 


-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Shragai, Yaron
Sent: Monday, December 12, 2016 6:10 PM
To: edk2-devel@lists.01.org
Subject: Re: [edk2] build failure trying to build gcc cross-compiler

Thanks.  Note that the instructions at that link - differentiated by flavor of Linux - all end with a link to the instructions that I referenced ("The remaining instructions are common for most UNIX-like systems").  I did follow the special Ubuntu notes on the page you referenced before going on to the page I referenced.

Thanks,
Yaron

-----Original Message-----
From: Richardson, Brian [mailto:brian.richardson@intel.com]
Sent: Monday, December 12, 2016 6:05 PM
To: Shragai, Yaron <yshragai@draper.com>; edk2-devel@lists.01.org
Subject: RE: build failure trying to build gcc cross-compiler

The instructions you referenced are intended for non-Linux UNIX systems. Please try these instructions for Ubuntu LTS ...
https://github.com/tianocore/tianocore.github.io/wiki/Using-EDK-II-with-Native-GCC

I have recently updated these instructions for GCC5 on Ubuntu 16.04 LTS.

Thanks ... br
---
Brian Richardson, Senior Technical Marketing Engineer, Intel Software brian.richardson@intel.com -- @intel_Brian (Twitter & WeChat) https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson

-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Shragai, Yaron
Sent: Monday, December 12, 2016 3:55 PM
To: edk2-devel@lists.01.org
Subject: [edk2] build failure trying to build gcc cross-compiler

Hello,
I am trying to build the Tianocore source from https://github.com/tianocore/edk2, as per the instructions here: https://github.com/tianocore/tianocore.github.io/wiki/Common-instructions-for-Unix

I am runnin on a Virtualbox VM running Ubuntu Desktop LTS.

I get as far as the "Build gcc x64 UEFI cross compiler" section.
The script mingw-gcc-build.py contains hardcoded references to download binutils and gcc.
In the case of binutils, it references a version that no longer exists in the archive (version 2.20.51.0.5).
In the case of gcc, it references version 4.3.0, on ftpmirror.gnu.org/gcc/, which redirects to other mirror sites, many of which are blocked by my firewall.
I tried getting around this by downloaded the files myself, and commented out the part of the script that downloads the sources (the call to sources.GetAll() - lines 553-558).
I downloaded binutils version 2.24.51.0.2, and gcc vesion 2.24.51.0.2.
It appears that binutils built, but gcc is not building.
Any advice?
Is there an updated version of mingw-gcc-build.py?

Extracting ./src/gcc-4.3.0.tar.bz2:
Extracting ./src/binutils-2.24.51.0.2.tar.bz2:
binutils [config] ... [done]
binutils [build] ... [done]
binutils [install] ... [done]
binutils module is now built and installed gcc [config] ... [done] gcc [build] ... [failed!] Traceback (most recent call last):
  File "./mingw-gcc-build.py", line 564, in <module>
    App()
  File "./mingw-gcc-build.py", line 562, in __init__
    Builder(sources, config).Build()
  File "./mingw-gcc-build.py", line 426, in Build
    self.BuildModule('gcc')
  File "./mingw-gcc-build.py", line 473, in BuildModule
    self.RunCommand(cmd, module, 'build')
  File "./mingw-gcc-build.py", line 511, in RunCommand
    'See output log at %s' % self.config.Relative(logFile)
Exception: Failed to build gcc
See output log at ./build/log.txt

Thanks,
Yaron Shragai
yshragai@draper.com

  ________________________________
Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email.
  ________________________________
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
________________________________
 Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email.
________________________________
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2016-12-12 23:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 20:54 build failure trying to build gcc cross-compiler Shragai, Yaron
2016-12-12 21:45 ` Bill Paul
2016-12-12 23:04 ` Richardson, Brian
2016-12-12 23:09   ` Shragai, Yaron
2016-12-12 23:29     ` Richardson, Brian [this message]
2016-12-12 23:34       ` Shragai, Yaron

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=80AC2BAA3152784F98F581129E5CF5AF664EDF59@ORSMSX114.amr.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