Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Nitin A Kamble <nitin.a.kamble@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] avoid absolute pathnames for general utils in libtool scripts
Date: Mon, 21 Feb 2011 17:55:43 +0000	[thread overview]
Message-ID: <1298310943.11289.3189.camel@rex> (raw)
In-Reply-To: <cover.1298053136.git.nitin.a.kamble@intel.com>

On Fri, 2011-02-18 at 10:21 -0800, Nitin A Kamble wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> 
> The builthost specific absolute pathnames were not working on other hosts
> with the nativesdk libtool package. This commit fixes that.
> 
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>   Branch: nitin/misc
>   Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
> 
> Thanks,
>     Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
> 
> 
> Nitin A Kamble (1):
>   libtool: avoid absolute pathnames of general utils
> 
>  meta/recipes-devtools/libtool/libtool-cross_2.4.bb |    2 +-
>  .../recipes-devtools/libtool/libtool-native_2.4.bb |    2 +-
>  .../libtool/libtool-nativesdk_2.4.bb               |    2 +-
>  meta/recipes-devtools/libtool/libtool.inc          |    3 +-
>  .../avoid_absolute_paths_for_general_utils.patch   |   37 ++++++++++++++++++++
>  meta/recipes-devtools/libtool/libtool_2.4.bb       |    2 +-
>  6 files changed, 43 insertions(+), 5 deletions(-)
>  create mode 100644 meta/recipes-devtools/libtool/libtool/avoid_absolute_paths_for_general_utils.patch

Merged to master, thanks.

Richard




      parent reply	other threads:[~2011-02-21 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 18:21 [PATCH 0/1] avoid absolute pathnames for general utils in libtool scripts Nitin A Kamble
2011-02-18 18:21 ` [PATCH 1/1] libtool: avoid absolute pathnames of general utils Nitin A Kamble
2011-02-18 19:07 ` [PATCH 0/1] avoid absolute pathnames for general utils in libtool scripts Scott Garman
2011-02-21 17:55 ` Richard Purdie [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=1298310943.11289.3189.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=nitin.a.kamble@intel.com \
    --cc=poky@yoctoproject.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