From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][v3] gcc-cross: fix PV and make it compile
Date: Wed, 28 Jul 2010 19:39:45 +0200 [thread overview]
Message-ID: <20100728173945.GD19135@mx.loc> (raw)
In-Reply-To: <i2pokl$7iu$1@dough.gmane.org>
On Wed, Jul 28, 2010 at 07:16:05PM +0200, Koen Kooi wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On 28-07-10 19:14, Bernhard Reutner-Fischer wrote:
>
>> -PV = "4.6+svnr${SRCPV}"
>> +PR = "4.6+svnr${SRCPV}"
>
>NAK, PV = "4.6+svnr${SRCPV}" is the right thing to do
ok what should i do then?
I want to use the svn version of gcc regardless of it being called
"1.2.3-svn" or "5.0.0-svn" so i put this into my local.conf:
#PREFERRED_GCC_VERSION = "4.4.4"
PREFERRED_GCC_VERSION = "svn"
But that obviously doesn't work with a PV of "4.6+svnr${SRCPV}" like
current git has.
I made up that "svn" intuitively, with the following reasoning:
i'm using the subversion version (_version_, hence PV)
with an arbitrary revision as Package Release that will sort correctly
iff a 4.6.0 release would be made.
Now how am i supposed to pick "svn" if not by using "svn"?
thanks for clarification,
next prev parent reply other threads:[~2010-07-28 17:40 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
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 [this message]
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=20100728173945.GD19135@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.