From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][v2] gcc-cross: fix PV and make it compile
Date: Fri, 16 Jul 2010 23:39:29 +0200 [thread overview]
Message-ID: <20100716213929.GI23169@mx.loc> (raw)
In-Reply-To: <1279315934-8363-1-git-send-email-rep.dot.nop@gmail.com>
On Fri, Jul 16, 2010 at 11:32:14PM +0200, Bernhard Reutner-Fischer wrote:
>index 2e24d63..40b46d6 100644
>--- a/recipes/gcc/gcc-svn.inc
>+++ b/recipes/gcc/gcc-svn.inc
>@@ -1,7 +1,7 @@
> DEFAULT_PREFERENCE = "-999"
> ARM_INSTRUCTION_SET = "arm"
>
>-SRCREV = "158653"
>+SRCREV = "162223"
>
> require gcc-common.inc
>
>@@ -9,9 +9,9 @@ DEPENDS = "mpfr gmp libmpc"
> NATIVEDEPS = "mpfr-native gmp-native libmpc-native"
>
> BINV = "4.6.0"
>-PV = "4.6+svnr${SRCPV}"
>+PKGV = "4.6+svnr${SRCPV}"
>
>-FILESPATHPKG .= ":gcc-svn"
>+FILESPATHPKG .= ":gcc-${PV}"
If i don't munge PR then i will not rebuild if the revision changes.
With above we'll always end up with (e.g.) gcc-cross-svn-r0
which is rather inconvenient, no?
next prev parent reply other threads:[~2010-07-16 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 15:25 [PATCH 0/3] misc fixups Bernhard Reutner-Fischer
2010-07-15 15:25 ` [PATCH 1/3] minimal: commentary typo fix Bernhard Reutner-Fischer
2010-07-15 15:25 ` [PATCH 2/3] micro: get PREFERRED_BINUTILS from sane-toolchain Bernhard Reutner-Fischer
2010-07-15 15:25 ` [PATCH 3/3] gcc-cross: fix PV and make it compile Bernhard Reutner-Fischer
2010-07-15 15:48 ` Phil Blundell
2010-07-15 15:54 ` Martin Jansa
2010-07-16 21:32 ` [PATCH][v2] " Bernhard Reutner-Fischer
2010-07-16 21:39 ` Bernhard Reutner-Fischer [this message]
2010-07-28 17:14 ` [PATCH][v3] " Bernhard Reutner-Fischer
2010-07-28 17:16 ` Koen Kooi
2010-07-28 17:39 ` Bernhard Reutner-Fischer
2010-07-28 19:37 ` Koen Kooi
2010-07-28 19:59 ` Bernhard Reutner-Fischer
2010-07-29 6:18 ` Frans Meulenbroeks
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=20100716213929.GI23169@mx.loc \
--to=rep.dot.nop@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.