linux-kernel - Re: Strange linux-next build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200805031825.50914.dhazelton@enter.net>
Date:	Sat, 3 May 2008 18:25:48 -0400
From:	Daniel Hazelton <dhazelton@...er.net>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Pavel Machek <pavel@...e.cz>, linux-next@...r.kernel.org
Subject: Re: Strange linux-next build error

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.
> >
> > On Sat, 3 May 2008 01:21:38 -0400 Daniel Hazelton <dhazelton@...er.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

I've been unable to trigger it with "make V=1 bzImage" - does the verbosity 
change, somehow, the default number of makes that get run ?

If it does, I could try adding -j2 or similar  to see if that causes it to 
trigger.

DRH

-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/