Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] bdwgc: new recipe for autogen
Date: Tue, 17 Jan 2012 13:43:47 -0800	[thread overview]
Message-ID: <4F15EB93.9090301@linux.intel.com> (raw)
In-Reply-To: <b042b10b86d6e28290a64e42e1e23de81621630b.1326831402.git.nitin.a.kamble@intel.com>

On 01/17/2012 12:30 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>
> This recipe is needed by guile.
> And guile is needed for autogen.
>
> Signed-off-by: Nitin A Kamble<nitin.a.kamble@intel.com>
> ---
>   meta/recipes-support/bdwgc/bdwgc_20110107.bb |   38 ++++++++++++++++++++++++++
>   1 files changed, 38 insertions(+), 0 deletions(-)
>   create mode 100644 meta/recipes-support/bdwgc/bdwgc_20110107.bb
>
> diff --git a/meta/recipes-support/bdwgc/bdwgc_20110107.bb b/meta/recipes-support/bdwgc/bdwgc_20110107.bb
> new file mode 100644
> index 0000000..1aaa5b8
> --- /dev/null
> +++ b/meta/recipes-support/bdwgc/bdwgc_20110107.bb
> @@ -0,0 +1,38 @@
> +SUMMARY = "A garbage collector for C and C++"
> +
> +DESCRIPTION = "The Boehm-Demers-Weiser conservative garbage collector can be\
> + used as a garbage collecting replacement for C malloc or C++ new. It allows\
> + you to allocate memory basically as you normally would, without explicitly\
> + deallocating memory that is no longer useful. The collector automatically\
> + recycles memory when it determines that it can no longer be otherwise\
> + accessed.\
> +  The collector is also used by a number of programming language\
> + implementations that either use C as intermediate code, want to facilitate\
> + easier interoperation with C libraries, or just prefer the simple collector\
> + interface.\
> +  Alternatively, the garbage collector may be used as a leak detector for C\
> + or C++ programs, though that is not its primary goal.\
> +  Empirically, this collector works with most unmodified C programs, simply\
> + by replacing malloc with GC_malloc calls, replacing realloc with GC_realloc\
> + calls, and removing free calls."
> +
> +HOMEPAGE = "http://www.hpl.hp.com/personal/Hans_Boehm/gc/"
> +SECTION = "devel"
> +LICENSE = "custom"
What's custom?  Is this the correct LICENSE name to use here?
Beth comments?

Sau!

> +LIC_FILES_CHKSUM = "file://README.QUICK;md5=9b9dd874f6940641b6ab19893ee8f1cc"
> +
> +SRC_URI = "http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/bdwgc-7_2alpha5-20110107.tar.bz2"
> +
> +SRC_URI[md5sum] = "4f3c130fc71ff23584edaa19a37739ee"
> +SRC_URI[sha256sum] = "1f57b959ae1144e1e5fa59d52d7cb4ed626fd74cf47da1c9c119b8b46ae2722d"
> +
> +PR = "r0"
> +
> +S = "${WORKDIR}/bdwgc"
> +
> +do_install_append (){
> +	rm -f ${D}${datadir}/${PN}
> +}
> +
> +inherit autotools
> +BBCLASSEXTEND = "native nativesdk"



  reply	other threads:[~2012-01-17 21:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 20:28 [PATCH 0/5] Recipes for fixing the grub-efi issue properly nitin.a.kamble
2012-01-17 20:30 ` [PATCH 1/5] bdwgc: new recipe for autogen nitin.a.kamble
2012-01-17 21:43   ` Saul Wold [this message]
2012-01-17 22:20     ` Flanagan, Elizabeth
2012-01-17 22:27       ` Kamble, Nitin A
2012-01-17 22:52       ` Richard Purdie
2012-01-17 22:59         ` Flanagan, Elizabeth
2012-01-17 23:22   ` Khem Raj
2012-01-18  1:28     ` Kamble, Nitin A
2012-01-18  1:33       ` Kamble, Nitin A
2012-01-18  5:46         ` Khem Raj
2012-01-18 16:52           ` Kamble, Nitin A
2012-01-17 20:30 ` [PATCH 2/5] libunistring: " nitin.a.kamble
2012-01-17 20:30 ` [PATCH 3/5] guile: " nitin.a.kamble
2012-01-18  9:54   ` Koen Kooi
2012-01-18 21:09     ` Kamble, Nitin A
2012-01-18 23:34       ` Kamble, Nitin A
2012-01-17 20:30 ` [PATCH 4/5] autogen-native: new recipe for grub-efi-native nitin.a.kamble
2012-01-17 20:30 ` [PATCH 5/5] grub-efi-native: fix errors with automake 1.11.2 nitin.a.kamble
2012-01-17 21:45   ` Saul Wold
2012-01-17 22:08     ` Kamble, Nitin A

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=4F15EB93.9090301@linux.intel.com \
    --to=sgw@linux.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