All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/4] bdwgc: new package
Date: Sun, 23 Nov 2014 16:23:54 +0100	[thread overview]
Message-ID: <20141123152354.GA4210@free.fr> (raw)
In-Reply-To: <546E6154.6090509@paguilar.org>

Pedro, All,

On 2014-11-20 22:47 +0100, Pedro Aguilar spake thusly:
> On 18/11/2014 21:59, Yann E. MORIN wrote:
> >Pedro, All,
> >
> >On 2014-11-06 22:48 +0100, Pedro Aguilar spake thusly:
> >>bdwgc is a garbage collector for C and C++. The Boehm-Demers-Weiser
> >>conservative garbage collector can be used as a garbage collecting
> >>replacement for C 'malloc' or C++ 'new'.
> >>
> >>Signed-off-by: Pedro Aguilar <paguilar@paguilar.org>
> >
> >I've had a cursory look at configure.ac, and it seems it detects C++ and
> >threading model, and does not need LFS.
> 
> It installs C++ support only with the --enable-cplusplus option that is not
> enabled by default and not needed by Guile.
> 
> Yes, it detects a threading model depending on the platform.
> Should I add to the Config.in the following?
> 
> comment "bdwgc needs a toolchain w/ threads"
>     depends on BR2_TOOLCHAIN_HAS_THREADS

No, that's Ok as-is, because configure detects the presence or abscence
of C++ and threads, so we need not depend on _HAS_THREADS or anything
else.

If that was wrong, the autobuilders will tell us, since they build a lot
of different combinations.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-11-23 15:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 21:48 [Buildroot] [PATCH v4 0/4] package/guile: New package Pedro Aguilar
2014-11-06 21:48 ` [Buildroot] [PATCH v4 1/4] libatomic_ops: Add host-autotools-package Pedro Aguilar
2014-11-18 20:35   ` Yann E. MORIN
2014-11-06 21:48 ` [Buildroot] [PATCH v4 2/4] bdwgc: new package Pedro Aguilar
2014-11-18 20:59   ` Yann E. MORIN
2014-11-20 21:47     ` Pedro Aguilar
2014-11-23 15:23       ` Yann E. MORIN [this message]
2014-11-06 21:48 ` [Buildroot] [PATCH v4 3/4] libunistring: Add host-autotools-package Pedro Aguilar
2014-11-18 21:03   ` Yann E. MORIN
2014-11-06 21:48 ` [Buildroot] [PATCH v4 4/4] guile: new package Pedro Aguilar
2014-11-18 21:18   ` Yann E. MORIN
2014-11-20 23:02     ` Pedro Aguilar
2014-11-23 15:29       ` Yann E. MORIN
2014-11-23 19:20         ` Pedro Aguilar

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=20141123152354.GA4210@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.