public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Peter Seebach <peter.seebach@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pseudo: fix sqlite path and package missing files
Date: Mon, 04 Feb 2013 23:37:59 +0000	[thread overview]
Message-ID: <1360021079.14071.174.camel@ted> (raw)
In-Reply-To: <20130204172705.0e18d279@e6410-2>

On Mon, 2013-02-04 at 17:27 -0600, Peter Seebach wrote:
> On Mon, 4 Feb 2013 23:21:51 +0000
> Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
> > I suspect not since we don't always use "lib", we might use something
> > different in various multilib configurations for example. Using
> > ${baselib} in the target configurations will therefore give us less
> > problems.
> 
> Oh, point. Yeah, that's probably true.
> 
> I think the pseudo-itself changes are probably not needed (since they
> are basically the same as the with-static-sqlite), but the recipe
> changes may well be desireable, then. I think my --with-sqlite-lib=lib
> may need to be altered in the case where we're not using "lib". It's
> right for the *normal* bitbake native/sdk case, but possibly not for
> other cases.

Agreed. Can someone send me a patch which makes it all work please? :)

Cheers,

Richard




  reply	other threads:[~2013-02-04 23:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 11:33 [PATCH] pseudo: fix sqlite path and package missing files Constantin Musca
2013-02-04 18:23 ` Peter Seebach
2013-02-04 23:21   ` Richard Purdie
2013-02-04 23:27     ` Peter Seebach
2013-02-04 23:37       ` Richard Purdie [this message]
2013-02-04 23:50         ` Peter Seebach
2013-02-05  7:37           ` Constantin Musca
2013-02-05 19:15             ` Peter Seebach
2013-02-05 19:37               ` Saul Wold
2013-02-05 19:46                 ` Peter Seebach
2013-02-05 20:09                 ` Peter Seebach

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=1360021079.14071.174.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.seebach@windriver.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