From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/libgc: add Boehm-Demers-Weiser gc library
Date: Wed, 16 Apr 2014 19:05:47 +0200 [thread overview]
Message-ID: <20140416190547.14a2dc36@skate> (raw)
In-Reply-To: <1397225156-23112-3-git-send-email-alex.bennee@linaro.org>
Dear Alex Benn?e,
I applied your patch, but there were several problems to fix. See
below for details.
On Fri, 11 Apr 2014 15:05:55 +0100, Alex Benn?e wrote:
> diff --git a/package/libgc/Config.in b/package/libgc/Config.in
> new file mode 100644
> index 0000000..5bceb3d
> --- /dev/null
> +++ b/package/libgc/Config.in
> @@ -0,0 +1,10 @@
> +config BR2_PACKAGE_LIBGC
> + bool "libgc"
> + select BR2_PACKAGE_LIBATOMIC_OPS
When you select a package, you need to duplicate the dependencies of
that package. So here, you should have duplicate the dependencies of
the libatomic_ops package. To make this easier, I've made a small
change to the libatomic_ops package so that it provides a
BR2_PACKAGE_LIBATOMIC_OPS_ARCH_SUPPORTS Config.in option that other
packages can depend on.
> + help
> + 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.
> +
> + http://www.hboehm.info/gc/
> diff --git a/package/libgc/libgc.mk b/package/libgc/libgc.mk
> new file mode 100644
> index 0000000..e3c5bf1
> --- /dev/null
> +++ b/package/libgc/libgc.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# libgc
> +#
> +################################################################################
> +
> +LIBGC_VERSION = 7.4.0
> +LIBGC_SOURCE = gc-${LIBGC_VERSION}.tar.gz
We normally use $(...) to reference make variables, not ${...}.
> +LIBGC_SITE = http://www.hboehm.info/gc/gc_source/
> +LIBGC_DEPENDANCIES += libatomic_ops
It should have been DEPENDENCIES, and the += is unnecessary, = is
enough.
> +LIBGC_LICENSE = GPLv1+
libgc is apparently not under GPLv1+, but under some X11-like
permissive license.
> +LIBGC_LICENSE_FILES = COPYING
There was no file named COPYING, the copyright details are found in the
README.md file.
> +LIBGC_INSTALL_STAGING = YES
> +
> +$(eval $(autotools-package))
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-16 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 14:05 [Buildroot] [PATCH 0/3] Add lightweight Zile editor Alex Bennée
2014-04-11 14:05 ` [Buildroot] [PATCH 1/3] package/libatomic: mark as supporting aarch64 Alex Bennée
2014-04-12 21:19 ` Thomas Petazzoni
2014-04-11 14:05 ` [Buildroot] [PATCH 2/3] package/libgc: add Boehm-Demers-Weiser gc library Alex Bennée
2014-04-11 20:03 ` Thomas De Schampheleire
2014-04-11 22:22 ` Thomas Petazzoni
2014-04-16 17:05 ` Thomas Petazzoni [this message]
2014-04-11 14:05 ` [Buildroot] [PATCH 3/3] package/zile: add Zile is Lossy Emacs editor Alex Bennée
2014-04-11 15:39 ` Alex Bennée
2014-04-11 20:10 ` Thomas De Schampheleire
2014-04-17 11:44 ` Alex Bennée
2014-04-11 22:24 ` Thomas Petazzoni
2014-04-17 11:45 ` Alex Bennée
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=20140416190547.14a2dc36@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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