From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Should EXTRA_FIRMWARE include full path to output directory?
Date: Sat, 17 Jan 2009 21:26:15 +0300 [thread overview]
Message-ID: <200901172126.29358.arvidjaar@mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
{pts/1}% LC_ALL=C make -C ~/src/linux-git O=$HOME/build/linux-2.6.29
make: Entering directory `/home/bor/src/linux-git'
Using /home/bor/src/linux-git as source for kernel
ln -fsn /home/bor/src/linux-git source
GEN /home/bor/build/linux-2.6.29/Makefile
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CALL /home/bor/src/linux-git/scripts/checksyscalls.sh
CHK include/linux/compile.h
/home/bor/src/linux-git/firmware/Makefile:156: warning: overriding commands
for target `firmware/e100/d101m_ucode.bin.gen.S'
/home/bor/src/linux-git/firmware/Makefile:153: warning: ignoring old
commands for target `firmware/e100/d101m_ucode.bin.gen.S'
AS firmware/e100/d101m_ucode.bin.gen.o
firmware/e100/d101m_ucode.bin.gen.S: Assembler messages:
firmware/e100/d101m_ucode.bin.gen.S:5: Error: file not found:
/home/bor/src/linux-git/firmware/e100/d101m_ucode.bin
make[2]: *** [firmware/e100/d101m_ucode.bin.gen.o] Error 1
make[1]: *** [firmware] Error 2
make: *** [sub-make] Error 2
make: Leaving directory `/home/bor/src/linux-git'
{pts/1}% grep e100 ~/build/linux-2.6.29/.config
CONFIG_EXTRA_FIRMWARE="e100/d101m_ucode.bin"
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2009-01-17 18:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200901172126.29358.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®