linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Hollis Blanchard" <hollis@penguinppc.org>
To: "Paul Mackerras" <paulus@samba.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux kernel <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: build failure on powerpc with current -git
Date: Wed, 22 Oct 2008 10:19:31 -0500	[thread overview]
Message-ID: <fb412d760810220819o1a15d47ej198f6e15c3e63f15@mail.gmail.com> (raw)
In-Reply-To: <18686.42209.47915.184451@cargo.ozlabs.ibm.com>

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

On Tue, Oct 21, 2008 at 10:58 PM, Paul Mackerras <paulus@samba.org> wrote:

> Stephen Rothwell writes:
>
> > On Tue, 21 Oct 2008 16:33:10 +1100 Paul Mackerras <paulus@samba.org>
> wrote:
> > >
> > > It's a bug in older versions of ld (including 2.16.1) that's fixed in
> > > the current version (2.18).  However, this patch appears to work
> > > around the problem - at least, it let me build a 32-bit kernel with a
> > > cross-toolchain including a 2.16.1 ld.  Let me know if this gets it
> > > working for you.
> >
> > With that patch applied I got these errors for a powerpc ppc64_defconfig
> > build (linux-next).
> >
> > /usr/bin/objcopy: Warning: '/dev/null' is not an ordinary file
>
> Hmmm, so do I, and in fact the arch/powerpc/boot/wrapper change now
> seems to be unnecessary with my cross-compile setup (which has ld
> 2.16.1), whereas yesterday I'm sure it got errors.  Weird.
>
> Chris, could you try just the following change (my previous patch
> without the arch/powerpc/boot/wrapper change) and let me know if it
> fixes things with the ld you use?
>

Works for me.

binutils 2.16.1 is the most recent binutils that will build with crosstool,
so IMHO it's worth supporting. :)

-Hollis

[-- Attachment #2: Type: text/html, Size: 1704 bytes --]

  reply	other threads:[~2008-10-22 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 19:32 build failure on powerpc with current -git Chris Friesen
2008-10-18  6:49 ` Grant Likely
2008-10-21  5:33 ` Paul Mackerras
2008-10-21  8:13   ` Stephen Rothwell
2008-10-22  3:58     ` Paul Mackerras
2008-10-22 15:19       ` Hollis Blanchard [this message]
2008-10-22 17:50         ` Chris Friesen
2008-10-23  0:19           ` Josh Boyer
2008-10-22 15:21       ` Hollis Blanchard
2008-10-22 17:49       ` Chris Friesen

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=fb412d760810220819o1a15d47ej198f6e15c3e63f15@mail.gmail.com \
    --to=hollis@penguinppc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).