From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Mark Asselstine <mark.asselstine@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] gtk-doc: update to 1.27
Date: Thu, 8 Feb 2018 08:44:02 +0200 [thread overview]
Message-ID: <00d7531e-b773-536e-ad5b-e19f8f993dbf@linux.intel.com> (raw)
In-Reply-To: <3144211.9qXzQgCZpO@yow-masselst-lx1>
On 02/07/2018 11:34 PM, Mark Asselstine wrote:
> Alexander. When things move to python you can almost always bet on them
> requiring additional libraries and as such the lack of RDEPENDS here is a bit
> surprising. As you can see from the top of some of the py files in gtk-doc we
> have:
>
> import logging
> import os
> import re
> import subprocess
> import sys
> import six
> import codecs
>
> Some of which are python stdlibs but others are external modules, such as
> 'six'. As such I am now getting a build failure:
>
> -- Installing ../../../libunique-1.1.6/doc/reference/html/up.png
> Traceback (most recent call last):
> File "/home/mark/build/overc/tmp/work/core2-64-overc-linux/libunique/
> 1.1.6-r7/recipe-sysroot-native/usr/bin/gtkdoc-rebase", line 28, in
> <module>
> from gtkdoc import common, config, rebase
> File "/home/mark/build/overc/tmp/work/core2-64-overc-linux/libunique/
> 1.1.6-r7/recipe-sysroot-native/usr/share/gtk-doc/python/gtkdoc/
> common.py", line 31, in <module>
> import six
> ImportError: No module named 'six'
>
> So we need to RDEPENDS on "python-six" here for starters. We do have a recipe
> for python-six but it is in meta-openembedded. So we either need to move this
> recipe there or the python-six recipe to oe-core or...
Thanks for the failure report Mark, but the diagnosis is way off :-)
First of all, for what purpose are you even building libunique? It's a
very old, unmaintained library for gtk 2.x apps from gnome stack (last
release: 2011), and here's what gnome has to say about it: "Unique is
now in maintenance mode and its usage is strongly discouraged".
It's coming from the gnome section of meta-oe, which is badly suffering
from lack of maintenance and general bitrot. I think much of it was
about to be removed a few months ago at last, but for some reason it
hasn't happened.
This specific failure is because libunique recipe neither inherits
gtk-doc class (which correctly sets things up) nor explicitly disables
gtk-doc. I'm now building the rest of meta-oe to check if anything else
needs to be fixed up, and will send a patch in a moment.
Alex
next prev parent reply other threads:[~2018-02-08 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 17:38 [PATCH 1/2] gtk-doc: update to 1.27 Alexander Kanavin
2018-02-02 17:38 ` [PATCH 2/2] libfm: add a patch to fix build errors with recent versions of gtk-doc Alexander Kanavin
2018-02-07 21:34 ` [PATCH 1/2] gtk-doc: update to 1.27 Mark Asselstine
2018-02-08 6:44 ` Alexander Kanavin [this message]
2018-02-08 22:13 ` Mark Asselstine
2018-02-09 7:03 ` Alexander Kanavin
2018-02-09 15:26 ` Mark Asselstine
2018-02-27 11:20 ` 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=00d7531e-b773-536e-ad5b-e19f8f993dbf@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=mark.asselstine@windriver.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