From: "Alex Bennée" <alex.bennee@linaro.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libgc: add Boehm-Demers-Weiser gc library
Date: Tue, 08 Apr 2014 11:20:51 +0100 [thread overview]
Message-ID: <87wqf03yws.fsf@linaro.org> (raw)
In-Reply-To: <20140407202610.GB3215@free.fr>
Yann E. MORIN <yann.morin.1998@free.fr> writes:
> Alex, Alex, All,
>
> On 2014-04-07 12:00 +0100, Alex Benn?e spake thusly:
>> This is needed for applications like Zile
>>
>> Signed-off-by: Alex Benn?e <alex.bennee@linaro.org>
>> Signed-off-by: Alex Benn?e <alex@bennee.com>
>
> Woot! It's not that often with have a schizophrenic contributor! ;-)
Yeah I blame format-patch for that one!
>
> [--SNIP--]
>> diff --git a/package/libgc/libgc.mk b/package/libgc/libgc.mk
>> new file mode 100644
>> index 0000000..e5c4609
>> --- /dev/null
>> +++ b/package/libgc/libgc.mk
>> @@ -0,0 +1,23 @@
>> +################################################################################
>> +#
>> +# Boehm-Demers-Weiser's GC
>> +#
>> +################################################################################
>> +
>> +LIBGC_VERSION = 7.4.0
>> +LIBGC_SOURCE = gc-${LIBGC_VERSION}.tar.gz
>
> Use parenthesis when evaluating variables, not curly-braces:
> LIBGC_SOURCE = gc-$(LIBGC_VERSION).tar.gz
>
>> +LIBGC_SITE = http://www.hboehm.info/gc/gc_source/
>> +LIBGC_EXTRA_DOWNLOADS = libatomic_ops-${LIBGC_VERSION}.tar.gz
>
> Ditto, parenthesis.
>
>> +LIBGC_LICENSE = GPLv1+
>> +LIBGC_LICENSE_FILES = COPYING
>> +LIBGC_INSTALL_STAGING = YES
>> +
>> +define LIBGC_POST_EXTRACT_INC_LIBATOMIC
>> + env
>
> This is not needed.
>
>> + mkdir -p $(@D)/libatomic_ops
>> + tar -xvf ${BR2_DL_DIR}/libatomic_ops-${LIBGC_VERSION}.tar.gz --strip-components=1 -C $(@D)/libatomic_ops
>> +endef
>> +
>> +LIBGC_POST_EXTRACT_HOOKS += LIBGC_POST_EXTRACT_INC_LIBATOMIC
>
> I know this is how upstream suggests building, but I can refrain from
> finding this really ugly... Yuck! :-(
>
> Anyway: can't use you use something like:
>
> LIBGC_LIBATOMIC_OPS = libatomic_ops-${LIBGC_VERSION}.tar.gz
> LIBGC_EXTRA_DOWNLOADS = $(LIBGC_LIBATOMIC_OPS)
>
> define LIBGC_POST_EXTRACT_INC_LIBATOMIC
> $(INSTALL) -d -m 0755 $(LSOF_DIR)/libatomic_ops && \
> $(call suitable-extractor,$(LIBGC_LIBATOMIC_OPS)) $(DL_DIR)/$(LIBGC_LIBATOMIC_OPS) |\
> $(TAR) $(TAR_STRIP_COMPONENTS)=1 -C $(LSOF_DIR)/libatomic_opsi $(TAR_OPTIONS) -
> endef
> LIBGC_POST_EXTRACT_HOOKS += LIBGC_POST_EXTRACT_INC_LIBATOMIC
>
> Note LIBGC_LIBATOMIC_OPS is not strictly required, but I find it cleaner
> to use, rather than call suitabel-extract on _EXTRA_DOWNLOADS, which is
> a plual and could contain more than one file. That's purely for
> aesthetics.
I'll look at using the buildroot defined one.
>
>> +$(eval $(autotools-package))
>
> Regards,
> Yann E. MORIN.
--
Alex Benn?e
next prev parent reply other threads:[~2014-04-08 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:00 [Buildroot] [PATCH 0/2] Add lightweight Zile editor Alex Bennée
2014-04-07 11:00 ` [Buildroot] [PATCH 1/2] package/libgc: add Boehm-Demers-Weiser gc library Alex Bennée
2014-04-07 20:26 ` Yann E. MORIN
2014-04-08 10:20 ` Alex Bennée [this message]
2014-04-07 21:39 ` Thomas Petazzoni
2014-04-07 11:00 ` [Buildroot] [PATCH 2/2] package/zile: add Zile is Lossy Emacs editor Alex Bennée
2014-04-07 20:33 ` Yann E. MORIN
2014-04-08 10:19 ` Alex Bennée
2014-04-08 16:16 ` Yann E. MORIN
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=87wqf03yws.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--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