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 21:59:43 +0200 [thread overview]
Message-ID: <20100728195943.GA29909@mx.loc> (raw)
In-Reply-To: <i2q0sv$5tc$1@dough.gmane.org>
On Wed, Jul 28, 2010 at 09:37:03PM +0200, Koen Kooi wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-July/021641.html
this is rather ugly and counter intuitive for i'll have to change the
PREFERRED_GCC_VERSION whenever someone decides to change that "4.6+svnr",
but ok, i'll drop the PR hunk :(
thanks,
>On 28-07-10 19:39, Bernhard Reutner-Fischer wrote:
>> 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,
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.5 (Darwin)
>
>iD8DBQFMUIbfMkyGM64RGpERAoPYAJ9rxqMp47aGQnPjE6R7GTIMx7CQpgCgmuIa
>7su2ka+K0cQBaopKy11SRtk=
>=1Jf8
>-----END PGP SIGNATURE-----
>
>
>_______________________________________________
>Openembedded-devel mailing list
>Openembedded-devel@lists.openembedded.org
>http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-07-28 20:00 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
2010-07-28 19:37 ` Koen Kooi
2010-07-28 19:59 ` Bernhard Reutner-Fischer [this message]
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=20100728195943.GA29909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox