linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, Greg Kroah-Hartman <gregkh@suse.de>,
	maximilian attems <max@stro.at>,
	Paul Mackerras <paulus@au.ibm.com>
Subject: Re: ppc64 vecemu compile failure
Date: Wed, 30 Jan 2008 12:39:25 +1100	[thread overview]
Message-ID: <1201657165.15799.0.camel@concordia> (raw)
In-Reply-To: <20080130005607.GA32622@lixom.net>

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


On Tue, 2008-01-29 at 18:56 -0600, Olof Johansson wrote:
> Hi,
> 
> On Wed, Jan 30, 2008 at 01:03:37AM +0100, maximilian attems wrote:
> > on latest git since driver subsys merge on powerpc64:
> > 
> > arch/powerpc/kernel/built-in.o: In function `fphalf':
> > vecemu.c:(.toc+0x1360): undefined reference to `devices_subsys'
> > make[3]: *** [.tmp_vmlinux1] Error 1

> It's a known problem, fixed by:
> 
> http://patchwork.ozlabs.org/linuxppc/patch?id=16491

But begs the question, why is the linker lying to use about vecemu.c
using devices_subsys?

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-01-30  1:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  0:03 ppc64 vecemu compile failure maximilian attems
2008-01-30  0:40 ` Greg KH
2008-01-30  0:56 ` Olof Johansson
2008-01-30  1:39   ` Michael Ellerman [this message]
2008-01-30  1:55     ` Olof Johansson

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=1201657165.15799.0.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=gregkh@suse.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=max@stro.at \
    --cc=olof@lixom.net \
    --cc=paulus@au.ibm.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 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).