Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "Purdie, Richard" <richard.purdie@intel.com>,
	"yocto-builds@yoctoproject.org" <yocto-builds@yoctoproject.org>,
	Paul Eggleton <paul.eggleton@linux.intel.com>,
	'Patches and discussions about the oe-core layer'
	<openembedded-core@lists.openembedded.org>
Subject: Re: Glib-2.0 cross-compile issue Was: Master Failures
Date: Tue, 17 Jul 2012 17:57:29 -0700	[thread overview]
Message-ID: <500609F9.3040609@linux.intel.com> (raw)
In-Reply-To: <20120718005221.GG22569@jama.jama.net>

On 07/17/2012 05:52 PM, Martin Jansa wrote:
> On Wed, Jul 18, 2012 at 02:38:50AM +0200, Martin Jansa wrote:
>> On Tue, Jul 17, 2012 at 05:26:48PM -0700, Saul Wold wrote:
>>> On 07/17/2012 02:58 PM, Saul Wold wrote:
>>>>
>>>> Folks,
>>>>
>>>> I am seeing a crop of failures on Master, this is not any failure I have
>>>> seen recently on any of my MUT builds. It appears to be 2 failures,
>>>> possibly related.
>>>
>>> Not related, I just confirmed this.
>>>
>>> The "ls: cannot access" are coming from license.bbclass, seems to be a
>>> timing issue related to the last patch here, not sure what triggered it
>>> here (I am not seeing it on other builds!)
>>>
>>> Paul's Change:
>>>
>>> http://git.openembedded.org/openembedded-core-contrib/log/?h=sgw%2Fstage&qt=grep&q=license
>>>
>>>>
>>>> First seems to be missing pkgdata/runtime files, followed by a failed
>>>> dependency by libglib-2.0-utils on the native python (from the native
>>>> sysroot).
>>>>
>>> This seems to be related to the glib update and package split out of the
>>> gdbus-codegen, looks like an auto tools substitution is happening for
>>> @PYTHON@ in the script and getting the native sysroot python.
>>
>> gdbus-codegen was in separate package before I've just moved package
>> definition from .bb to .inc.
>>
>> And buildhistory diff doesn't show anything weird:
>> http://git.shr-project.org/git/?p=buildhistory.git;a=commitdiff;h=00de88a123842b159de1d206e3d0d5775ed90a1e#patch2
>>
>> I don't see it here, but I'm not using RPM packaging with this check..
>>
>> Will try more tomorrow..
>
> It's probably caused by this
> http://permalink.gmane.org/gmane.comp.gnome.svn/604029
>
> which isn't very cross-compile friendly.. maybe we can just add patch
> reverting this change in 2.32.4?
>
Yup, that the change, I was just digging deeper, maybe just doing a sed 
in a configure_prepend to change it the $(PYTHON) -> "/usr/bin/env 
python" in the Makefile.am would be better

We have seen that kind of code before.

Sau!


> Cheers,
>
>>
>> Cheers,
>>
>>>
>>> Martin's 2 changes may need so work:
>>>
>>> http://git.openembedded.org/openembedded-core/commit/?id=85a930188300152bc9a1bbf640a2441f3177e26f
>>>
>>> and
>>> http://git.openembedded.org/openembedded-core/commit/?id=b070eb22372ad1ef5b21162d832772e560184cf8
>>>
>>> Please look at the autobuild failures and see if they can help you fix
>>> these issues.
>>>
>>> Thanks
>>> 	Sau!
>>>
>>>> I am just starting to dig into it, but if anyone has better ideas:
>>>>
>>>> Thanks
>>>>       Sau!
>>>>
>>>>
>>>>> | ls: cannot access
>>>>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-arm/build/build/tmp/pkgdata/*/runtime/dbus-1:
>>>>> No such file or directory

<snip>

>> --
>> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
>
>
>




  reply	other threads:[~2012-07-18  1:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 21:58 Master Failures Saul Wold
2012-07-18  0:26 ` Saul Wold
2012-07-18  0:38   ` Martin Jansa
2012-07-18  0:52     ` Glib-2.0 cross-compile issue Was: " Martin Jansa
2012-07-18  0:57       ` Saul Wold [this message]
2012-07-18  1:01       ` Colin Walters
2012-07-18  1:05         ` Martin Jansa
2012-07-18  9:17           ` [PATCH] glib-2.0: revert one commit in target recipe Martin Jansa
2012-07-18 21:25             ` Richard Purdie
2012-07-18  9:25   ` Master Failures Paul Eggleton
2012-07-18  9:36 ` Burton, Ross

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=500609F9.3040609@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=richard.purdie@intel.com \
    --cc=yocto-builds@yoctoproject.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