From: Richard Chan <rspchan@starhub.net.sg>
To: linux-kernel@vger.kernel.org
Subject: [KBUILD] md/raid6 breaks separate source/object tree
Date: Sat, 24 Jan 2004 20:10:25 +0800 [thread overview]
Message-ID: <401260B1.7090909@starhub.net.sg> (raw)
md/raid6 is using an in-tree perl script to generate a C file.
This breaks kbuild separate src/obj tree.
CC [M] drivers/md/raid6main.o
CC [M] drivers/md/raid6algos.o
CC [M] drivers/md/raid6recov.o
HOSTCC drivers/md/mktables
drivers/md/mktables > drivers/md/raid6tables.c || ( rm -f
drivers/md/raid6tables.c && exit 1 )
CC [M] drivers/md/raid6tables.o
perl drivers/md/unroll.pl 1 <
/usr/src/linux-2.6.2-rc1.1.A/drivers/md/raid6int.uc >
drivers/md/raid6int1.c || ( rm -f drivers/md/raid6int1.c && exit 1 )
Can't open perl script "drivers/md/unroll.pl": No such file or directory
Somehow the src in $(PERL) $(src)/drivers/md/unroll.pl is not getting
substituted.
Still trying to figure it out...
next reply other threads:[~2004-01-24 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 12:10 Richard Chan [this message]
2004-01-24 21:32 ` [KBUILD] md/raid6 breaks separate source/object tree Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-01-24 12:26 sam
2004-01-24 20:44 ` 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=401260B1.7090909@starhub.net.sg \
--to=rspchan@starhub.net.sg \
--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