Hi, On Thu, Aug 25, 2011 at 11:51 AM, Stephen Rothwell <s...@canb.auug.org.au> wrote: > Hi Timur, > > On Thu, 25 Aug 2011 10:22:05 -0500 Timur Tabi <ti...@freescale.com> wrote: >> >> Is there some trick to building allyesconfig on PowerPC? When I do try >> that, I >> get all sorts of weird build errors, and it dies long before it gets to my >> driver. I get stuff like: >> >> LD arch/powerpc/sysdev/xics/built-in.o >> WARNING: arch/powerpc/sysdev/xics/built-in.o(.text+0x1310): Section mismatch >> in >> reference from the function .icp_native_init() to the function >> .init.text:.icp_native_init_one_node() >> The function .icp_native_init() references >> the function __init .icp_native_init_one_node(). >> This is often because .icp_native_init lacks a __init >> annotation or the annotation of .icp_native_init_one_node is wrong. > > We get lots of those in many builds. :-( Just a warning. > If you could provide an exhaustive list of them, I'd be interested. Do you account/reference them in the report you make on each new -next tree ?
- Arnaud >> and >> >> AS arch/powerpc/kernel/head_64.o >> arch/powerpc/kernel/exceptions-64s.S: Assembler messages: >> arch/powerpc/kernel/exceptions-64s.S:1151: Error: attempt to move .org >> backwards >> arch/powerpc/kernel/exceptions-64s.S:1160: Error: attempt to move .org >> backwards > > There is a patch for that pending with either the kvm guys or the powerpc > guys. > >> I guess I don't have the right compiler. > > Yours seems to be OK. If you pass -k to make it will get further. Or > you could configure it and then just try building your driver rather than > the whole tree. > >> Anyway, I think I know how to fix the break that Stephen is seeing. I will >> post >> a v4 patch in a few minutes. > > Thanks. > -- > Cheers, > Stephen Rothwell s...@canb.auug.org.au > http://www.canb.auug.org.au/~sfr/ > _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
