From: bob@kunk.jriver.com
To: linuxppc-dev@lists.linuxppc.com
Subject: 2.2.17pre7 Ramdisk compile failure
Date: Tue, 27 Jun 2000 17:18:23 -0500 (CDT) [thread overview]
Message-ID: <20000627221948.10637.qmail@kunk.jriver.com> (raw)
rd.c:115: `CONFIG_BLK_DEV_RAM_SIZE' undeclared here (not in a function)
BTW, I got this from a fresh rsync from Pauls stable tree. I've been noticing
odd behavior with these rsync images ocassionally. It seems like
older files are not always replaced and I ran into a missing autoconf.h this
afternoon.
Are there known issues with rsync?
rsync version 2.4.1 Copyright Andrew Tridgell and Paul Mackerras
Bob
--
Robert E. Brose II N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-06-27 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-27 22:18 bob [this message]
[not found] <395925FD.97C131C5@erols.com>
2000-06-28 2:15 ` 2.2.17pre7 Ramdisk compile failure bob
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=20000627221948.10637.qmail@kunk.jriver.com \
--to=bob@kunk.jriver.com \
--cc=linuxppc-dev@lists.linuxppc.com \
/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).