Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] git: updated to 1.8.0.2
Date: Mon, 24 Dec 2012 14:46:06 -0800	[thread overview]
Message-ID: <50D8DB2E.4040800@linux.intel.com> (raw)
In-Reply-To: <1356097300-25337-1-git-send-email-bogdan.a.marinescu@intel.com>

On 12/21/2012 05:41 AM, Bogdan Marinescu wrote:
> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
> ---
>   meta/recipes-devtools/git/{git_1.7.7.bb => git_1.8.0.2.bb} |    6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>   rename meta/recipes-devtools/git/{git_1.7.7.bb => git_1.8.0.2.bb} (63%)
>
This update seems to introduce a dependency on gettext's msgfmt and on 
libtinfo, I saw a couple of failures on the autobuild due to these not 
being build for git-native.

You might verify if your host has gettext installed, that might mask 
this issue, as seen on the autobuilder, ab02 does not have gettext 
installed.

A clean re-build, or cleaning gettext-native and rebuilding should show 
this issue if you do not have a host gettext installed (verify by 
looking for /usr/bin/msgfmt).

See (msgfmt failure):
http://autobuilder.yoctoproject.org:8010/builders/nightly-x86/builds/846/steps/shell_29/logs/stdio
and (tinfo failure)
http://autobuilder.yoctoproject.org:8010/builders/nightly-x86/builds/847/steps/shell_29/logs/stdio

Note that it builds OK in the atom-pc case, because those natives are 
now build and available for git to use.

It may require some DEPENDS changes, use caution here, we want to keep 
this part of the startup path as short as possible, so watch the 
dependency chains.

Thanks

Sau!

> diff --git a/meta/recipes-devtools/git/git_1.7.7.bb b/meta/recipes-devtools/git/git_1.8.0.2.bb
> similarity index 63%
> rename from meta/recipes-devtools/git/git_1.7.7.bb
> rename to meta/recipes-devtools/git/git_1.8.0.2.bb
> index 6b6e04b..1726317 100644
> --- a/meta/recipes-devtools/git/git_1.7.7.bb
> +++ b/meta/recipes-devtools/git/git_1.8.0.2.bb
> @@ -1,10 +1,10 @@
>   require git.inc
>
> -PR = "r3"
> +PR = "r0"
>
>   SRC_URI = "http://git-core.googlecode.com/files/git-${PV}.tar.gz"
> -SRC_URI[md5sum] = "5d645884e688921e773186783b65ce33"
> -SRC_URI[sha256sum] = "5a977bc01e4989b9928345e99aab15ce896cf5897c6e32eb449538574df377f6"
> +SRC_URI[md5sum] = "1aca109d4a719fe5bc43d25927fbc7d9"
> +SRC_URI[sha256sum] = "c06d5d29389e90583d16ec41d5be931593196f6842f9b14e910a0b5781c10e07"
>
>   EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no ac_cv_c_c99_format=yes \
>                    ac_cv_fread_reads_directories=${ac_cv_fread_reads_directories=yes} \
>



      reply	other threads:[~2012-12-24 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 13:41 [PATCH] git: updated to 1.8.0.2 Bogdan Marinescu
2012-12-24 22:46 ` Saul Wold [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=50D8DB2E.4040800@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=bogdan.a.marinescu@intel.com \
    --cc=openembedded-core@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