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:21:51 +0000 [thread overview]
Message-ID: <1360020111.14071.172.camel@ted> (raw)
In-Reply-To: <20130204122309.12582d0b@e6410-2>
On Mon, 2013-02-04 at 12:23 -0600, Peter Seebach wrote:
> On Mon, 4 Feb 2013 13:33:26 +0200
> Constantin Musca <constantinx.musca@intel.com> wrote:
>
> > - replace --enable-sqlite-static with --with-sqlite-static=.. in order
> > to pass ${baselib} to configure (/lib doesn't work for the multilib
> > lib32 build)
>
> This looks eerily similar to, yet subtly different from, the changes I
> made for pseudo-1.4.2/1.4.3. I'd spelled that as
> "--with-static-sqlite=" for specifying an exact path to libsqlite.a,
> but I eventually changed it to --with-sqlite-lib to allow an override
> because bitbake's design seems to want libsqlite3.a to always be in
> (host sysroot)/usr/lib, regardless of whether that's 64-bit or 32-bit.
>
> > - use ${exec_prefix}/lib instead of ${libdir} because pseudo always
> > uses /usr/lib
>
> This seems right, but I hadn't done it in the recent submission of
> 1.4.3, and things were working anyway. So now I want to know why...
>
> Anyway, I think these changes are probably redundant with the changes I
> submitted over the weekend.
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.
Cheers,
Richard
next prev parent reply other threads:[~2013-02-04 23:38 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 [this message]
2013-02-04 23:27 ` Peter Seebach
2013-02-04 23:37 ` Richard Purdie
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=1360020111.14071.172.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 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.