From: "Robert M. Fuhrer" <rmf@asgard.cs.columbia.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Compile errors on kernel source from ppc.samba.org::linux-pmac-stable
Date: Fri, 22 Sep 2000 23:10:55 -0400 [thread overview]
Message-ID: <200009230310.XAA08258@asgard.cs.columbia.edu> (raw)
I rsync'ed twice from ppc.samba.org, and although it clearly got many
files (the first time around), the source wouldn't compile. The first of
many batches of errors cropped up in
drivers/block/ll_rw_blk.c
which sees no definition of the type 'elevator_t', as well as a few other
"elevator"-related types.
Granted, I rsync'ed on top of an existing 2.2.15pre9 source tree, but I
gave rsync the "--delete" and "-u" flags, which I thought should have
given me a fairly clean and up-to-date tree. No?
The precise rsync cmd I used was
rsync -avuz ppc.samba.org::linux-pmac-stable .
If my rsync cmd was ok, am I wrong in expecting the linux-pmac-stable
tree to compile cleanly?
Or, failing all of the above, what's wrong?
-------------------------------------------------------------------------
> "Smooth Jazz" is no jazz at all... <
> Dr. Robert M. Fuhrer rfuhrer@watson.ibm.com <
> Computer Music Center IBM T.J. Watson Research Center <
-------------------------------------------------------------------------
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-09-23 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-23 3:10 Robert M. Fuhrer [this message]
2000-09-24 22:37 ` Compile errors on kernel source from ppc.samba.org::linux-pmac-stable Paul Mackerras
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=200009230310.XAA08258@asgard.cs.columbia.edu \
--to=rmf@asgard.cs.columbia.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rmf@cs.columbia.edu \
/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;
as well as URLs for NNTP newsgroup(s).