From: Daniel Hazelton <dhazelton@enter.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Strange linux-next build error
Date: Sat, 3 May 2008 01:21:38 -0400 [thread overview]
Message-ID: <200805030121.39831.dhazelton@enter.net> (raw)
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
Restarting the build brings it through to completion. I've checked and there
is no reason that this error should occur.
madman@strider:~/linux/linux-git/Documentation$ gcc --version
gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
(I'll be booting this kernel tomorrow to test it - previous -next kernels have
all faulted during boot)
DRH
--
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
next reply other threads:[~2008-05-03 5:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 5:21 Daniel Hazelton [this message]
2008-05-03 5:52 ` Stephen Rothwell
2008-05-03 6:40 ` Sam Ravnborg
2008-05-03 16:10 ` Daniel Hazelton
2008-05-03 22:25 ` Daniel Hazelton
2008-05-03 22:40 ` Ingo Molnar
2008-05-04 1:37 ` Daniel Hazelton
2008-05-04 5:36 ` Sam Ravnborg
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=200805030121.39831.dhazelton@enter.net \
--to=dhazelton@enter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®