Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: dbus-native --with-x
Date: Thu, 2 Jun 2011 10:04:26 -0700	[thread overview]
Message-ID: <4DE7C29A.2030609@mentor.com> (raw)
In-Reply-To: <1307005695.2529.164.camel@phil-desktop>

On 06/02/2011 02:08 AM, Phil Blundell wrote:
> On Wed, 2011-06-01 at 15:22 -0700, Tom Rini wrote:
>> On 06/01/2011 03:07 PM, Henning Heinold wrote:
>>> On Wed, Jun 01, 2011 at 03:00:37PM -0700, Tom Rini wrote:
>>>> On 06/01/2011 01:22 PM, Phil Blundell wrote:
>>>>> On Wed, 2011-06-01 at 11:58 -0500, Mark Hatle wrote:
>>>>>> It "should" be as simple and adding --without-perl and --without-python to the
>>>>>> configuration line...  but I haven't tried it.
>>>>>
>>>>> Turns out that rpm-native already does this, but (like the dbus case)
>>>>> there is no matching logic to get the DEPENDS right.
>>>>>
>>>>> Another instance of a similar thing appears to be sqlite3-native, which
>>>>> DEPENDS on tcl-native even though it's configured --without-tcl.
>>>>
>>>> Since this keeps coming up, maybe it needs a comment.  sqlite3 needs
>>>> tcl-native (tclsh) to generate a header file.  No tclsh, no sqlite3.
>>>
>>> I thought that is diffrent with 3.7.x version of sqlite3.
>>
>> Nope.  That's what I checked this against.  In oe.dev
>> a2c3af2d608b1b713018d688b00e03873a538993 is where we set all of this right.
> 
> Actually, it looks to me like Henning is right.  In 3.7.6.2, which seems
> to be what we have in oe-core right now, I can't find any trace of the
> old tcl script that was being used for header generation.  Which file(s)
> did you find the tcl requirement in?

I guess I've just gone crazy (or crazier if you prefer) and I can't find
it anymore in 3.7.x.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-06-02 17:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 16:01 dbus-native --with-x Phil Blundell
2011-06-01 16:03 ` Phil Blundell
2011-06-01 16:11   ` Koen Kooi
2011-06-01 16:16     ` Phil Blundell
2011-06-01 16:48       ` Mark Hatle
2011-06-01 16:54         ` Phil Blundell
2011-06-01 16:58           ` Mark Hatle
2011-06-01 17:08             ` Phil Blundell
2011-06-01 18:55               ` rpmdeps, was " Mark Hatle
2011-06-01 19:00                 ` Koen Kooi
2011-06-01 21:14                   ` Mark Hatle
2011-06-01 20:02                 ` Phil Blundell
2011-06-01 21:17                   ` Mark Hatle
2011-06-02  9:18                     ` Phil Blundell
2011-06-01 20:22             ` Phil Blundell
2011-06-01 22:00               ` Tom Rini
2011-06-01 22:07                 ` Henning Heinold
2011-06-01 22:22                   ` Tom Rini
2011-06-01 22:38                     ` Mark Hatle
2011-06-02  9:08                     ` Phil Blundell
2011-06-02 17:04                       ` Tom Rini [this message]
2011-06-02 19:21                         ` Phil Blundell
2011-06-02 19:29                           ` Tom Rini
2011-06-02  7:12                 ` Phil Blundell
2011-06-01 16:10 ` Koen Kooi
2011-06-01 16:40   ` Phil Blundell

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=4DE7C29A.2030609@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox