linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux PPC Mailing List <linuxppc-dev@ozlabs.org>
Subject: Re: "make ARCH=ppc defconfig" fails looking for common_defconfig
Date: Mon, 18 Feb 2008 06:43:11 -0600	[thread overview]
Message-ID: <20080218064311.737307a6@zod.rchland.ibm.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802180430100.10518@localhost.localdomain>

On Mon, 18 Feb 2008 04:32:24 -0500 (EST)
"Robert P. J. Day" <rpjday@crashcourse.ca> wrote:

> 
>   (AIUI, the entire ppc/ architecture is going away, yes?  which means
> i probably shouldn't care about any errors within.  is that correct?
> even so, build errors should probably still be avoided for now.)

Yes, it's going away.  There's really no longer support for anything
"common" in it now anyway.  CHRP, POWER3 and POWER4 have been removed.
So have 83xx and 85xx.

Just let it go.

josh

      reply	other threads:[~2008-02-18 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18  9:32 "make ARCH=ppc defconfig" fails looking for common_defconfig Robert P. J. Day
2008-02-18 12:43 ` Josh Boyer [this message]

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=20080218064311.737307a6@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rpjday@crashcourse.ca \
    /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).