Messages in this thread | | | From | Daniel Hazelton <> | Subject | Re: Strange linux-next build error | Date | Sat, 3 May 2008 12:10:02 -0400 |
| |
On Saturday 03 May 2008 02:40:57 Sam Ravnborg wrote: > On Sat, May 03, 2008 at 03:52:52PM +1000, Stephen Rothwell wrote: > > Just adding some cc's ... it is worth cc'ing linux-next for bugs in > > linux-next (instead, or as well, as me personally) since people who are > > interested are probably subscribed there.
Ah, yes - I'm not very good at remembering fine details like that :)
> > On Sat, 3 May 2008 01:21:38 -0400 Daniel Hazelton <dhazelton@enter.net> wrote: > > > After updating my local tree to the latest linux-next and starting a > > > clean build I see this error *ONLY* the first time I start a "make > > > bzImage" > > > > > > CC arch/x86/kernel/acpi/sleep.o > > > LDS arch/x86/kernel/acpi/realmode/wakeup.lds > > > cc1: fatal error: opening output file > > > arch/x86/kernel/acpi/realmode/wakeup.lds: Permission denied > > > compilation terminated. > > > make[4]: *** [arch/x86/kernel/acpi/realmode/wakeup.lds] Error 1 > > > make[3]: *** [arch/x86/kernel/acpi/realmode/wakeup.bin] Error 2 > > > make[2]: *** [arch/x86/kernel/acpi] Error 2 > > > make[1]: *** [arch/x86/kernel] Error 2 > > > make: *** [bzImage] Error 2 > > Hi Daniel. > > It looks like we visit arch/x86/kernel/acpi/realmode/Makefile > twice in parallel as we have both make[4] and make[3] in play here. > Or maybe we have a dependency bug in the Makefile. > > Can you try to do a: > make V=1 and post the output a few screen fulls before and until > the bug triggers. > They I will see if I can work out what is happening. > > Thanks, > Sam
Will do. I'll run a "make mrproper" and then rebuild the kernel with V=1
DRH
-- Dialup is like pissing through a pipette. Slow and excruciatingly painful.
| |