linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Judith Lebzelter <judith@osdl.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Judith Lebzelter <judith@osdl.org>
Subject: Re: 'make ARCH=ppc defconfig' failing for cross-compile
Date: Fri, 15 Sep 2006 12:22:42 -0700	[thread overview]
Message-ID: <20060915192242.GC10646@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1158203522.7305.14.camel@localhost.localdomain>

On Thu, Sep 14, 2006 at 01:12:01PM +1000, Michael Ellerman wrote:
> On Tue, 2006-09-12 at 10:48 -0700, Judith Lebzelter wrote:
> > On Tue, Sep 12, 2006 at 10:21:46AM -0700, Christian wrote:
> > > On Fri, 8 Sep 2006, Judith Lebzelter wrote:
> > > > I have been doing cross-compiles for ppc and powerpc on my i686 system.
> > > > In order to do this I generate the .config file like this:
> > > >
> > > > make ARCH=ppc defconfig
> > > > (or make ARCH=powerpc defconfig)
> > > 
> > > Seems like defconfig has been removed, because there are so many 
> > > sub-platforms for ppc:
> > 
> > I build these in OSDL's cross compile build farm (PLM) as a code check.
> > Our scripts are generalized to work for various architectures, so it is
> > disappointing that 'defconfig' no longer works for ppc the way it does 
> > in other achitectures.  Are there plans to make plain 'defconfig' work 
> > again, at least in the new 'powerpc' directory?  (The 'ppc64_defconfig' 
> > target looks good to me.:)
> 
> Perhaps you need to rework the scripts to cope for the fact that there
> are different platforms under the architecture? There will never be a
> defconfig for powerpc that builds all the code for all platforms, so to
> get full test coverage you'll need to build more than one config anyway.
> 

Yes, I do not get full code coverage, which would be the ideal.
However, I do run defconfig, allmodconfig, allyesconfig and allnoconfig
and have found issues doing this. There is value in running for a
few representative ppc architectures, which I do.  That is why 'defconfig'
is (was) handy for me. 

I additionally compile other architectures such as i386, ia64, x86_64, 
arm, sparc64.  People can submit their kernel patches to see how 
their code compiles, and usually this is more platforms than they would 
do at home.:)

Thanks,
Judith

> cheers
> 
> -- 
> Michael Ellerman
> OzLabs, IBM Australia Development Lab
> 
> wwweb: http://michael.ellerman.id.au
> phone: +61 2 6212 1183 (tie line 70 21183)
> 
> We do not inherit the earth from our ancestors,
> we borrow it from our children. - S.M.A.R.T Person

      reply	other threads:[~2006-09-15 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09  0:05 'make ARCH=ppc defconfig' failing for cross-compile Judith Lebzelter
2006-09-10  6:15 ` Christian
2006-09-12 17:48   ` Judith Lebzelter
2006-09-14  3:12     ` Michael Ellerman
2006-09-15 19:22       ` Judith Lebzelter [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=20060915192242.GC10646@shell0.pdx.osdl.net \
    --to=judith@osdl.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    /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).