On Tue, 2009-11-24 at 09:28 +0000, Alan Jenkins wrote: > James Bottomley wrote: > > On Tue, 2009-11-24 at 11:27 +1030, Rusty Russell wrote: > > > >> On Tue, 24 Nov 2009 06:23:20 am Alex Chiang wrote: > >> > >>> Hi Alan, Rusty, > >>> > >> Hi Alex, > >> > >> > >>> In the meantime, while Alan is deciding the proper way to fix > >>> this, would it be possible to drop the offending patch series > >>> from linux-next? > >>> > >> Done. That takes the pressure off Alan, and makes sure he has time to get > >> it right. > >> > > > > That probably suits us on parisc too. I just checked out our build in > > linux-next: we don't pass __modpost ... it looks like we have all the > > module symbols undefined. Will investigate more. > > > > James > > > > I think parisc wants P'printk where ia64 uses @fptr(printk). > > It may also need ".import printk,code" or similar. I think if you have to make modpost architecture specific, there's something a bit wrong in the patch series. I can confirm that reverting this particular patch allows the parisc build to work again. It still won't boot because module symbols aren't resolved. James -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
