From: John Dowd <jdowd@sympatico.ca>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Kernel Make files - a stupid question...
Date: Sat, 24 Feb 2001 14:36:23 -0500 [thread overview]
Message-ID: <01022414362300.18022@allo-moi> (raw)
I'm using Bitkeeper to manage a repository for my kernel source code. I'm
using the HardHat version of the kernel 2.4.x.
Since its been put under the bitkeeper manager each directory under the
repository has a directory called SCCS and the top one has a directory called
"Bitkeeper".
When I go to build the kernel, the make file walks into the SCCS directories
and tries to build the files there and I get all sorts of errors and warnings.
I had thought that gnu - Make knew about both RCS and SCCS repositories and
unless told otherwise, ignored them?
Does anyone have a solution for this?
Cheers!!
--
-----------------------------------------------------------------
"To Err is human, to forgive is not company policy!"
John Dowd
jdowd@sympatico.ca
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-02-24 19:36 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=01022414362300.18022@allo-moi \
--to=jdowd@sympatico.ca \
--cc=linuxppc-embedded@lists.linuxppc.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