Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/8] siteinfo: Move certain db entries to common-linux
Date: Mon, 25 Jul 2011 17:05:35 +0100	[thread overview]
Message-ID: <1311609936.30326.248.camel@phil-desktop> (raw)
In-Reply-To: <4E2D93D3.7030505@mentor.com>

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".

p.






  reply	other threads:[~2011-07-25 16:09 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 [this message]
2011-07-25 16:22         ` Tom Rini
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=1311609936.30326.248.camel@phil-desktop \
    --to=philb@gnu.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox