From: Judith Lebzelter <judith@osdl.org>
To: Christian <evilninja@gmx.net>
Cc: linuxppc-dev@ozlabs.org, Judith Lebzelter <judith@osdl.org>
Subject: Re: 'make ARCH=ppc defconfig' failing for cross-compile
Date: Tue, 12 Sep 2006 10:48:14 -0700 [thread overview]
Message-ID: <20060912174814.GA29226@shell0.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0609100652160.16347@sheep.housecafe.de>
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.:)
>
> $ ls arch/ppc/configs/*defconfig | wc -l
> 56
>
> Just pick the defonfig for your platform, for my PReP that'd be:
I will do this as a work-around.
TFYR,
Judith
>
> $ make ARCH=ppc CROSS_COMPILE=powerpc-604-linux-gnu- prep_defconfig
>
>
> HTH,
> Christian.
> --
> BOFH excuse #383:
>
> Your processor has taken a ride to Heaven's Gate on the UFO behind Hale-Bopp's comet.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2006-09-12 17:48 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 [this message]
2006-09-14 3:12 ` Michael Ellerman
2006-09-15 19:22 ` Judith Lebzelter
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=20060912174814.GA29226@shell0.pdx.osdl.net \
--to=judith@osdl.org \
--cc=evilninja@gmx.net \
--cc=linuxppc-dev@ozlabs.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).