From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/8] siteinfo: Move certain db entries to common-linux
Date: Mon, 25 Jul 2011 09:22:27 -0700 [thread overview]
Message-ID: <4E2D9843.2040409@mentor.com> (raw)
In-Reply-To: <1311609936.30326.248.camel@phil-desktop>
On 07/25/2011 09:05 AM, Phil Blundell wrote:
> On Mon, 2011-07-25 at 09:03 -0700, Tom Rini wrote:
>> On 07/25/2011 09:00 AM, Phil Blundell wrote:
>>> On Fri, 2011-07-22 at 09:28 -0700, Tom Rini wrote:
>>>> +db_cv_path_ar=${db_cv_path_ar=/usr/bin/ar}
>>>> +db_cv_path_chmod=${db_cv_path_chmod=/bin/chmod}
>>>> +db_cv_path_cp=${db_cv_path_cp=/bin/cp}
>>>> +db_cv_path_ln=${db_cv_path_ln=/bin/ln}
>>>> +db_cv_path_mkdir=${db_cv_path_mkdir=/bin/mkdir}
>>>> +db_cv_path_ranlib=${db_cv_path_ranlib=/usr/bin/ranlib}
>>>> +db_cv_path_rm=${db_cv_path_rm=/bin/rm}
>>>> +db_cv_path_sh=${db_cv_path_sh=/bin/sh}
>>>> +db_cv_path_strip=${db_cv_path_strip=/usr/bin/strip}
>>>
>>> Those contain assumptions about ${bindir} and ${base_bindir} which are
>>> not necessarily valid. I think db should probably be patched for those
>>> rather than putting them here,
>>
>> It's possible they simply aren't used anymore, if micro in oe.dev is
>> building / working with db.
>
> Yeah, could be. (I haven't checked recently but I don't recall any db
> breakage with micro in oe.dev.) It does seem a bit weird that db would
> want to use things like "strip".
As an aside, db is one of the things that makes me want to finish this
re-sync round so I can wipe out all of the site files and try again. As
I mention in the comments, we have a wrong and ignored bits for db since
it dates back to db3.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-07-25 16:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 16:28 [PATCH 0/8] Start consolidating siteinfo information Tom Rini
2011-07-22 16:28 ` [PATCH 1/8] siteinfo: Move certain samba entries to common-linux Tom Rini
2011-07-22 16:39 ` Kumar Gala
2011-07-22 16:50 ` Tom Rini
2011-07-25 16:02 ` Phil Blundell
2011-07-25 16:06 ` Tom Rini
2011-07-25 16:07 ` Phil Blundell
2011-07-22 16:28 ` [PATCH 2/8] siteinfo: Move certain bash " Tom Rini
2011-07-22 16:28 ` [PATCH 3/8] x86_64-linux siteinfo: Add bash info Tom Rini
2011-07-22 16:28 ` [PATCH 4/8] siteinfo: Move certain mysql entries to common-linux Tom Rini
2011-07-22 16:28 ` [PATCH 5/8] siteinfo: Move the rp-pppoe entry " Tom Rini
2011-07-22 16:28 ` [PATCH 6/8] siteinfo: Move certain db entries " Tom Rini
2011-07-25 16:00 ` Phil Blundell
2011-07-25 16:03 ` Tom Rini
2011-07-25 16:05 ` Phil Blundell
2011-07-25 16:22 ` Tom Rini [this message]
2011-07-22 16:28 ` [PATCH 7/8] siteinfo: Move general realloc/malloc values to common-$libc Tom Rini
2011-07-22 16:28 ` [PATCH 8/8] siteinfo: Move (getpgrp|setpgrp|setgrent|*get{pwuid, grgid}) to common-libc Tom Rini
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=4E2D9843.2040409@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@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 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.