Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Khem Raj : gnu-config: Add recipe for git version.
Date: Wed, 16 Jun 2010 15:32:59 +0200	[thread overview]
Message-ID: <hvajqb$i26$1@dough.gmane.org> (raw)
In-Reply-To: <hv9seb$ks1$1@dough.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16-06-10 08:54, Dmitry Eremin-Solenikov wrote:
> git version control wrote:
> 
>> Module: openembedded.git
>> Branch: org.openembedded.dev
>> Commit: 473cd5f616190739550abd8bf71629a87036730b URL:   
>> http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=473cd5f616190739550abd8bf71629a87036730b
>>
>> Author: Khem Raj <raj.khem@gmail.com>
>> Date:   Tue Jun 15 13:52:40 2010 -0700
>>
>> gnu-config: Add recipe for git version.
>>
>> * Rename gnu-config to files folder.
>>
>> Signed-off-by: Khem Raj
>> <raj.khem@gmail.com>
> 
> Unless I have git-native in ASSUME-PROVIDED, this breaks builds with:
> ERROR: Unbuildable tasks were found.
> These are usually caused by circular dependencies and any circular dependency chains found will be printed below. Increase the debug level to see a list of unbuildable tasks.

I changed it to fetch a snapshot instead, dep loop gone. Hopefully Khem
will learn from this and not but tons of stuff in ASSUME_PROVIDED on his
machine anymore...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMGNKKMkyGM64RGpERAhdpAKCZ168m2LEhxCKeztxTHfxJij4pqwCfRfnT
UXL1IuquynfLR31RcQ6i5t8=
=qmMV
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-06-16 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1OOdAL-0005Tc-Dn@melo.openembedded.org>
2010-06-16  6:54 ` Khem Raj : gnu-config: Add recipe for git version Dmitry Eremin-Solenikov
2010-06-16 13:32   ` Koen Kooi [this message]
2010-06-16 14:17     ` Khem Raj
2010-06-16 20:39     ` Koen Kooi
2010-06-16 20:53       ` Khem Raj

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='hvajqb$i26$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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