Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Sven Ebenfeld" <sven.ebenfeld@gmail.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH v2] mongodb: 2.6.0 -> 3.3.0 and remove	from pnblacklist
Date: Sun, 31 Jan 2016 17:13:58 +0100	[thread overview]
Message-ID: <005501d15c42$649442d0$2dbcc870$@gmail.com> (raw)
In-Reply-To: <CAMKF1sqD+vsprAKVV97YxXdbApfzkZCKKpdLQzZ40hqOoir=iQ@mail.gmail.com>

> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On
> Behalf Of Khem Raj
> Sent: Sunday, January 31, 2016 5:02 PM
> To: openembeded-devel <openembedded-
> devel@lists.openembedded.org>
> Subject: Re: [oe] [meta-oe][PATCH v2] mongodb: 2.6.0 -> 3.3.0 and remove
> from pnblacklist
> 
> On Sun, Jan 31, 2016 at 7:42 AM, Sven Ebenfeld <sven.ebenfeld@gmail.com>
> wrote:
> > -DEPENDS = "openssl libpcre boost libpcap"
> > -# Mongo uses tcmalloc on x86_64, which is provided by gperftools
> > -DEPENDS_append_x86-64 = " gperftools"
> > +DEPENDS = "openssl libpcre libpcap zlib"
> 
> why is gperftools dep dropped ?

gperftools dependency is added by PACKAGECONFIG[tcmalloc] if the parameters
require it.

> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel



  reply	other threads:[~2016-01-31 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 15:42 [meta-oe][PATCH v2] mongodb patch Sven Ebenfeld
2016-01-31 15:42 ` [meta-oe][PATCH v2] mongodb: 2.6.0 -> 3.3.0 and remove from pnblacklist Sven Ebenfeld
2016-01-31 16:01   ` Khem Raj
2016-01-31 16:13     ` Sven Ebenfeld [this message]
2016-01-31 17:27       ` Khem Raj

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='005501d15c42$649442d0$2dbcc870$@gmail.com' \
    --to=sven.ebenfeld@gmail.com \
    --cc=openembedded-devel@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