Linux-Next discussions
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, paul.gortmaker@windriver.com,
	sparclinux@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: New build failures in sparc.
Date: Wed, 14 Mar 2012 15:01:02 +1100	[thread overview]
Message-ID: <20120314040102.GA26084@thor.bakeyournoodle.com> (raw)
In-Reply-To: <20120313.173741.18086192847996966.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 575 bytes --]

On Tue, Mar 13, 2012 at 05:37:41PM -0700, David Miller wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 14 Mar 2012 10:28:30 +1100
> 
> > Yeah, we updated our sparc64 toolchain yesterday ... Tony says he
> > will try applying the patch(es) from the bugzilla.
> 
> Meanwhile I'll add a workaround to the sparc makefiles, and
> push that to Linus.  This way it will work no matter what
> combination of tools someone has.

Thanks Dave, we may be hitting a related but different issue as gcc
4.6.3 seems to have that patch already.

Yours Tony

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-03-14  4:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 22:28 New build failures in sparc Paul Gortmaker
2012-03-13 22:48 ` David Miller
2012-03-13 23:28   ` Stephen Rothwell
2012-03-14  0:37     ` David Miller
2012-03-14  0:58       ` Stephen Rothwell
2012-03-14  4:01       ` Tony Breeds [this message]
2012-03-14  4:46         ` David Miller
2012-03-14  5:02           ` Stephen Rothwell
2012-03-13 23:31   ` Paul Gortmaker

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=20120314040102.GA26084@thor.bakeyournoodle.com \
    --to=tony@bakeyournoodle.com \
    --cc=davem@davemloft.net \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sparclinux@vger.kernel.org \
    /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