From: Lu Jingdong <jingdong.lu@windriver.com>
To: Saul Wold <saul.wold@intel.com>
Cc: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: [PULL]Fix adding GDBM_File module for perl
Date: Wed, 24 Nov 2010 13:05:25 +0800 [thread overview]
Message-ID: <1290575125.1858.99.camel@eric-desktop> (raw)
In-Reply-To: <4CEAB2F0.2030700@intel.com>
On Mon, 2010-11-22 at 10:14 -0800, Saul Wold wrote:
> On 11/01/2010 03:22 AM, Lu Jingdong wrote:
> > Note:<commit_id> parameter assumed as 'HEAD'
> >
> > meta/recipes-devtools/perl/perl-5.8.8/config.sh | 8
> > meta/recipes-devtools/perl/perl-5.8.8/perl-enable-gdbm.patch | 17 +
> > meta/recipes-devtools/perl/perl_5.8.8.bb | 2
> >
> Jingdong,
>
> We have not forgotten about your changes, we are trying to determine the
> impact of the changes you are suggesting. Can you please let us know
> what the size difference would of perl by adding this change? Is it
> just a simple perl module? What additional dependencies occur when you
> add this patch and their impact on size.
>
> Sau!
Saul,
I think there is less influence on perl by enabling gdbm except that we
get a dynamic extend module. We compiled perl with gdbm enabled, we can
get "perl-module-gdbm-file" package and it provides the following files:
/usr/lib/perl/5.8.8/GDBM_File.pm
/usr/lib/perl/5.8.8/auto
/usr/lib/perl/5.8.8/auto/GDBM_File
/usr/lib/perl/5.8.8/auto/GDBM_File/GDBM_File.bs
/usr/lib/perl/5.8.8/auto/GDBM_File/GDBM_File.so
I add dependency of perl "+DEPENDS += "gdbm", because compiling gdbm
module of perl needs the "gdbm.h" provided by gdbm-dev.
--
Lu Jingdong
jingdong.lu@windriver.com
China, Wind River
prev parent reply other threads:[~2010-11-24 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 10:22 [PULL]Fix adding GDBM_File module for perl Lu Jingdong
2010-11-01 18:19 ` Saul Wold
2010-11-01 19:32 ` Mark Hatle
2010-11-05 13:34 ` Richard Purdie
2010-11-05 16:14 ` Mark Hatle
2010-11-22 18:14 ` Saul Wold
2010-11-24 5:05 ` Lu Jingdong [this message]
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=1290575125.1858.99.camel@eric-desktop \
--to=jingdong.lu@windriver.com \
--cc=poky@pokylinux.org \
--cc=saul.wold@intel.com \
/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