From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] qte: fixed do_configure() for powercpc
Date: Sat, 11 Dec 2010 01:05:51 -0800 [thread overview]
Message-ID: <20101211090551.GB8894@gmail.com> (raw)
In-Reply-To: <09D9BE2AC4AA764DABAA8C91E48D819ED3B1D61C@DEMCHP99E35MSX.ww902.siemens.net>
On (29/11/10 12:35), Aeschbacher, Fabrice wrote:
> Hi,
>
> Here is my 'git format-patch' again, after having run 'git rebase master'
still I have to apply this patch manually
>
> With kind regards,
> Fabrice
>
>
> Signed-off-by: Aeschbacher <fabrice.aeschbacher@siemens.com>
> ---
> recipes/qte/qte-common_2.3.10.inc | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/recipes/qte/qte-common_2.3.10.inc b/recipes/qte/qte-common_2.3.10.inc
> index 18811c7..2eed76d 100644
> --- a/recipes/qte/qte-common_2.3.10.inc
> +++ b/recipes/qte/qte-common_2.3.10.inc
> @@ -109,7 +109,7 @@ export SYSCONF_LFLAGS = "${LDFLAGS} -lts"
> export SYSCONF_MOC = "${STAGING_BINDIR_NATIVE}/moc"
> export SYSCONF_UIC = "${STAGING_BINDIR_NATIVE}/uic"
>
> -# generate uclibc and eabi configurations
> +# generate uclibc, eabi and powerpc configurations
> do_configure() {
> for f in ${S}/configs/linux-*-g++-shared; do
> sed -e 's,-linux-,-linux-uclibc-,g' < $f \
> @@ -119,6 +119,7 @@ do_configure() {
> sed -e 's,-linux-,-linux-uclibceabi-,g' < $f \
> > `dirname $f`/`basename $f | sed -e 's,linux-,linux-uclibceabi-,'`
> done
> + sed -e 's/arm/powerpc/' ${S}/configs/linux-arm-g++-shared > ${S}/configs/linux-powerpc-g++-shared
> echo yes | ./configure ${EXTRA_OECONF} || die "Configuring qte failed. EXTRA_OECONF was ${EXTRA_OECONF}"
> }
>
> --
> 1.5.6.5
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: openembedded-devel-bounces@lists.openembedded.org
> > [mailto:openembedded-devel-bounces@lists.openembedded.org] Im
> > Auftrag von Eric Bénard
> > Gesendet: Montag, 29. November 2010 11:37
> > An: openembedded-devel@lists.openembedded.org
> > Betreff: Re: [oe] [PATCH] qte: fixed do_configure() for powercpc
> >
> > Hi,
> >
> > On 29/11/2010 11:19, Aeschbacher, Fabrice wrote:
> > > Is this patch likely to be accepted and commited soon in
> > branch release-2010.12, or should I overlay?
> > >
> > the patch doesn't apply can you please rebase it against master ?
> >
> > Applying: qte: fixed do_configure() for powercpc
> > error: patch failed: recipes/qte/qte-common_2.3.10.inc:109
> > error: recipes/qte/qte-common_2.3.10.inc: patch does not apply
> > Patch failed at 0001 qte: fixed do_configure() for powercpc
> >
> > Eric
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-12-11 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 9:59 [PATCH] qte: fixed do_configure() for powercpc Aeschbacher, Fabrice
2010-11-29 10:19 ` Aeschbacher, Fabrice
2010-11-29 10:37 ` Eric Bénard
2010-11-29 11:35 ` Aeschbacher, Fabrice
2010-12-11 9:05 ` Khem Raj [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=20101211090551.GB8894@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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