All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	seabios@seabios.org
Subject: Re: [SeaBIOS] seabios build failure in xen tree
Date: Thu, 9 Feb 2012 11:25:19 +0100	[thread overview]
Message-ID: <4F339F0F.2090409@amd.com> (raw)
In-Reply-To: <20120209012818.GA476@morn.localdomain>

On 02/09/12 02:28, Kevin O'Connor wrote:
> On Wed, Feb 08, 2012 at 11:32:10AM +0100, Christoph Egger wrote:
>> On 02/08/12 02:18, Kevin O'Connor wrote:
>>> We can change the seabios makefile to call these scripts with an
>>> explicit $(PYTHON).
>>
>> Awesome!
>
> See the attached patch.
>
>>> That's quite odd.  This looks data related instead of python related.
>>> Try running a "make clean" and then "make" in just the seabios
>>> directory.  If you still see an issue, tar up the seabios "out/"
>>> directory and mail it to me.
>>
>> It failed the same way.
>> I sent you the tarball offlist due its size.
>
> Looks like your version of gcc is defining sections with
> .rodata.__PRETTY_FUNCTION__ - which is odd as that macro isn't used in
> the code.  Does the second attached patch fix it for you?
>
> -Kevin

Both patches work for me and there are no follow-up errors.
Thank you.

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

      reply	other threads:[~2012-02-09 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 13:35 seabios build failure in xen tree Christoph Egger
2012-02-08  1:18 ` Kevin O'Connor
2012-02-08 10:32   ` [SeaBIOS] " Christoph Egger
2012-02-09  1:28     ` Kevin O'Connor
2012-02-09 10:25       ` Christoph Egger [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-all 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=4F339F0F.2090409@amd.com \
    --to=christoph.egger@amd.com \
    --cc=kevin@koconnor.net \
    --cc=seabios@seabios.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.