On Thu, 2019-04-11 at 15:11 -0500, Jason Wessel wrote:
> On 4/11/19 3:01 PM, Alexander Kanavin wrote:
> > Yes, I agree.
> >
> > Alex
> >
> > > On 11 Apr 2019, at 21.59, Richard Purdie <
> > > richard.pur...@linuxfoundation.org> wrote:
> > >
> > > > On Thu, 2019-04-11 at 11:36 -0500, Jason
On 4/11/19 3:01 PM, Alexander Kanavin wrote:
> Yes, I agree.
>
> Alex
>
>> On 11 Apr 2019, at 21.59, Richard Purdie
>> wrote:
>>
>>> On Thu, 2019-04-11 at 11:36 -0500, Jason Wessel wrote:
>>>
>>> It all appears to work fine without the need to patch anything in
>>> master-next.
>>>
>>> Thank
Yes, I agree.
Alex
> On 11 Apr 2019, at 21.59, Richard Purdie
> wrote:
>
>> On Thu, 2019-04-11 at 11:36 -0500, Jason Wessel wrote:
>>> On 4/11/19 10:35 AM, Alexander Kanavin wrote:
>>> On Thu, 11 Apr 2019 at 17:25, Jason Wessel <
>>> jason.wes...@windriver.com> wrote:
> Generally because
On Thu, 2019-04-11 at 11:36 -0500, Jason Wessel wrote:
> On 4/11/19 10:35 AM, Alexander Kanavin wrote:
> > On Thu, 11 Apr 2019 at 17:25, Jason Wessel <
> > jason.wes...@windriver.com> wrote:
> > > > Generally because generating introspection data is disabled for
> > > > native
> > > > packages, as
On 4/11/19 10:35 AM, Alexander Kanavin wrote:
> On Thu, 11 Apr 2019 at 17:25, Jason Wessel wrote:
>>> Generally because generating introspection data is disabled for native
>>> packages, as a matter of policy (do not build something which is
>>> unused and untested).
>>>
>>> If you could add
>>>
On Thu, 11 Apr 2019 at 17:25, Jason Wessel wrote:
> > Generally because generating introspection data is disabled for native
> > packages, as a matter of policy (do not build something which is
> > unused and untested).
> >
> > If you could add
> > EXTRA_OEMESON_append_class-native = "
On 4/11/19 9:44 AM, Alexander Kanavin wrote:
> Generally because generating introspection data is disabled for native
> packages, as a matter of policy (do not build something which is
> unused and untested).
>
> If you could add
> EXTRA_OEMESON_append_class-native = " ${GI_DISABLE_FLAG}"
>
> to
Generally because generating introspection data is disabled for native
packages, as a matter of policy (do not build something which is
unused and untested).
If you could add
EXTRA_OEMESON_append_class-native = " ${GI_DISABLE_FLAG}"
to the gdk-pixbuf recipe, and re-test (without your fix, to be
Please understand I have no idea how gdk-pixbuf-native is supposed to compile.
Perhaps you can elaborate further as to why g-ir-scanner cannot be called in
this case. I did not observe any obvious way that the g-ir-scanner was
explicitly disabled for the build of the -native package with in
gdk-pixbuf-native should not be running g-ir-scanner at all, as we
explicitly disable this for native builds. Can you please look into
why it is happening, because the patch is really treating the symptom
rather than the problem.
Alex
On Wed, 10 Apr 2019 at 23:54, Jason Wessel wrote:
>
>
Investigation of an end user going over their quota in the user's home
directory showed that the gobject-instrospection is writing files into
the ~/.cache/g-ir-scanner when building -native packages. The test
package in this case was gdk-pixbuf-native.
Setting the GI_SCANNER_DISABLE_CACHE in the
11 matches
Mail list logo
