Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Python-native dependency in libxml2
Date: Fri, 18 Mar 2011 10:47:49 +0100	[thread overview]
Message-ID: <ilv9o6$t5p$1@dough.gmane.org> (raw)
In-Reply-To: <20110318083802.GA17785@jama.jama.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18-03-11 09:38, Martin Jansa wrote:
> On Fri, Mar 18, 2011 at 08:41:40AM +0100, Ahsan, Noor wrote:
>> Hello Martin/Frans and Khem,
>> Any recommendation after following analysis that how should I proceed.
>> Should I send the patches to community?
> 
> Maybe koen will reply with more info about xml2po issue he found, imho
> it wasn't in xml2po build but while using xml2to to generate docs in some
> other recipe.

The issue I had that I needed xml2{t,p}o to work on the target as well
for native compilation. If that still works, Noors changes is fine by me.

regards,

Koen

>  
> IIRC I had similar issue in some other recipe, but unfortunatelly don't 
> remember which one.
> 
> Regards,
> 
>>
>> Regards,
>> Noor
>>
>> -----Original Message-----
>> From: openembedded-devel-bounces@lists.openembedded.org
>> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
>> Ahsan, Noor
>> Sent: Thursday, March 17, 2011 3:41 PM
>> To: openembedded-devel@lists.openembedded.org
>> Subject: Re: [oe] Python-native dependency in libxml2
>>
>> Hello,
>>
>> Today I got the fresh stuff and tried to build gnome-doc-utils-native
>> (to build xml2po package). I am building on Ubuntu host 9.10. First it
>> gave me an error that it could not find intltoolize command. You can see
>> the attached build log "build_intltool_error,log". So I added intltool
>> package in gnome-doc-utils-native DEPENDS so it built successfully. You
>> can see the build log "build_intltool_fix.log". Then I removed all the
>> build stuff from build DIR and commented DEPENDS_virtclass-native =
>> "python-native" and XPY_virtclass-native = "
>> --with-python=${PYTHON_DIR}" in libxml2.inc file. Rebuild
>> gnome-doc-utils-native. It built successfully again. The build log is
>> also attached "build_no_python.log". I think there is no need of python
>> dependency in libxml2 package. Kindly correct me if I am doing anything
>> wrong.
>>
>> We need to fix gnome-doc-utils-native recipe, so that it does not show
>> intltoolize error.
>>
>> Regards,
>> Noor
>>
>> -----Original Message-----
>> From: openembedded-devel-bounces@lists.openembedded.org
>> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
>> Ahsan, Noor
>> Sent: Wednesday, March 16, 2011 1:39 PM
>> To: openembedded-devel@lists.openembedded.org
>> Subject: Re: [oe] Python-native dependency in libxml2
>>
>> Hello,
>>
>> I made 2 changes, first one was to remove python-native from DEPENDS and
>> second was commented out XPY_virtclass-native = "
>> --with-python=${PYTHON_DIR}". Moreover I removed all the stuff from
>> build dir, so there were not python-native for me. After kicking this
>> build libxml2-native build fine.
>>
>> I was looking for xml2po recipe, I couldn't find it. Can you tell me how
>> to build xml2po package so that I can reproduce the problem.
>>
>> Regards,
>> Noor
>>
>> -----Original Message-----
>> From: openembedded-devel-bounces@lists.openembedded.org
>> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
>> Martin Jansa
>> Sent: Wednesday, March 16, 2011 1:05 PM
>> To: openembedded-devel@lists.openembedded.org
>> Subject: Re: [oe] Python-native dependency in libxml2
>>
>> On Wed, Mar 16, 2011 at 08:28:39AM +0100, Frans Meulenbroeks wrote:
>>> 2011/3/16 Khem Raj <raj.khem@gmail.com>:
>>>> On 3/15/2011 11:22 PM, Ahsan, Noor wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I was looking at the libxml2 package. While going through the
>> recipes I
>>>>> came to know that its native package depends on python-native
>> package as
>>>>> well. This dependency is defined in libxml2.inc file.
>>>>>
>>>>> DEPENDS_virtclass-native = "python-native"
>>>>>
>>>>> This package build fine after removing this dependency. I am not
>> clear
>>>>> why this dependency is being added in libxml2 package. Can somebody
>>>>> clear that to me. While looking at the git log I came to know that
>> this
>>>>> change is coming from libxml2-native.inc file. But I am not clear
>> why
>>>>> this dependency was added as this package build fine without it.
>>>>>
>>>>> Please help me in understanding this dependency. Thanks.
>>>>
>>>> Try to build this recipe from scratch and see if it still works then
>> we can
>>>> remove the dep
>>
>> That's not enough, libxml2-native builds fine.. but then xml2po
>> will fail if there isn't libxml2-native built with python support.
>>
>> see a25f07ca6159e1cd5b8a215ca5da8405fb1b9053
>>
>> So yes.. for such tests you should build recipe from scratch _and_ check
>> if resulting package/sysroot is still the same.
>>
>> Regards,
>>
>>> I'm not sure if that is the right way.
>>> It might well be that typically python-native is already there in a
>>> scratch build because some earlier package needed it (or even because
>>> of the scheduling of build steps.
>>>
>>> Probably a better way is to build with packaged staging (with staging
>>> dir outside TMPDIR) then rm TMPDIR and bake the package.
>>> Alternately peek into the package to see if it needs python. If it is
>>> needed then the DEPENDS should stay.
>>>
>>> Looking at the issue at hand maybe the best person to ask is Martin
>>> Jansa as he last touched that line according to git blame:
>>> 3cd9ddbf recipes/libxml/libxml2.inc  (Martin Jansa
>>> 2010-02-26 12:32:53 +0100  5) DEPENDS_virtclass-native =
>>> "python-native"
>>>
>>> The other thing is that further on in the .inc file I see:
>>> XPY_virtclass-native = " --with-python=${PYTHON_DIR}"
>>>
>>> This strongly suggests a hard dependency on python, so removing the
>>> DEPENDS "because it builds without it" does not seem to be a good plan
>>> to me.
>>>
>>> My strong feeling is that recipes should be self-contained (so should
>>> list all packages they need to build, minus the ones that are
>>> inherited from classes (and maybe a few implicit ones like maybe make)
>>>
>>> Frans
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>> -- 
>> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNgypFMkyGM64RGpERAka3AJ91Dpu6+SCx3MH0HtK6LUyEnaH7tACeM4EP
b0nPj51+QTs4wdONs4BCP7Y=
=Zxcy
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-03-18  9:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 11:04 [PATCH] net-snmp: disable libnl use Steffen Sledz
2011-03-11 13:05 ` Koen Kooi
2011-03-11 15:53   ` Steffen Sledz
2011-03-12  0:05     ` Khem Raj
2011-03-14  7:06       ` Steffen Sledz
2011-03-14 16:39         ` Khem Raj
2011-03-15  9:08 ` Eliminating dependency race-conditions (was Re: [PATCH] net-snmp: disable libnl use) Esben Haabendal
2011-03-15 22:03   ` Denys Dmytriyenko
2011-03-16  5:47     ` Eliminating dependency race-conditions Esben Haabendal
2011-03-16  6:22       ` Python-native dependency in libxml2 Ahsan, Noor
2011-03-16  7:08         ` Khem Raj
2011-03-16  7:28           ` Frans Meulenbroeks
2011-03-16  7:43             ` Khem Raj
2011-03-16  8:00               ` Frans Meulenbroeks
2011-03-16  8:05             ` Martin Jansa
2011-03-16  8:38               ` Ahsan, Noor
2011-03-17 10:40                 ` Ahsan, Noor
2011-03-18  7:41                   ` Ahsan, Noor
2011-03-18  8:38                     ` Martin Jansa
2011-03-18  9:47                       ` Koen Kooi [this message]
2011-03-18  9:01                     ` Frans Meulenbroeks
2011-03-16  6:35       ` Eliminating dependency race-conditions Frans Meulenbroeks
2011-03-15 23:15   ` Eliminating dependency race-conditions (was Re: [PATCH] net-snmp: disable libnl use) Graham Gower
2011-03-17 11:18   ` Phil Blundell
2011-03-17 14:43     ` Esben Haabendal
2011-03-17 14:52       ` Graeme Gregory
2011-03-17 15:24         ` Koen Kooi
2011-03-17 15:07       ` Phil Blundell
2011-03-17 17:52         ` Esben Haabendal
2011-03-17 18:05           ` Phil Blundell
2011-03-17 19:58             ` Esben Haabendal
2011-03-17 21:00               ` Phil Blundell
2011-03-18  5:29                 ` Esben Haabendal
2011-03-18 10:26                   ` Phil Blundell
2011-03-18 12:14                     ` Eliminating dependency race-conditions Esben Haabendal
2011-03-19  0:32                       ` Richard Purdie
2011-03-22  9:01                         ` Esben Haabendal
2011-03-23 20:31                           ` Frans Meulenbroeks
2011-03-19  0:18               ` Eliminating dependency race-conditions (was Re: [PATCH] net-snmp: disable libnl use) Richard Purdie
2011-03-22  9:00                 ` Eliminating dependency race-conditions Esben Haabendal

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='ilv9o6$t5p$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@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