From: "Mark A. Greer" <mgreer@mvista.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: If not CONFIG_ALL_PPC, you're broken
Date: Mon, 16 Oct 2000 16:08:23 -0700 [thread overview]
Message-ID: <39EB8A67.E2F9C023@mvista.com> (raw)
I've haven't been paying attention to this but it seems as though any
platform that doesn't fit in CONFIG_ALL_PPC doesn't build anymore.
I've intentionally stayed back from the bleeding edge so I don't run
into these types of problems. However, now I'm ready to bring some
things up to the latest version and release to the world. Problem is,
some of the stuff I depend on is broken and has been for some time as I
understand it.
I guess I was hoping that enough people were tracking the latest changes
that things wouldn't stay broken for too long. Yes, I know, I am lazy
and should contribute more. Anyway, I think we all need to pay closer
attention to the changes that are being put in, including me.
What's the best way to get the other platforms working again?
Mark
--
Mark A. Greer (mgreer@mvista.com; 480-517-0287)
MontaVista Software, Inc.
2141 E. Broadway Road, Suite 108
Tempe, AZ 85282
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-10-16 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-16 23:08 Mark A. Greer [this message]
2000-10-17 4:57 ` If not CONFIG_ALL_PPC, you're broken Dan Malek
2000-10-17 11:17 ` Matt Porter
2000-10-17 15:28 ` Dan Malek
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=39EB8A67.E2F9C023@mvista.com \
--to=mgreer@mvista.com \
--cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).