From: Dan Callaghan <dan.callaghan@opengear.com>
To: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH v2] firewalld: update to 0.7.1
Date: Fri, 04 Oct 2019 11:34:06 +1000 [thread overview]
Message-ID: <1570152616-sup-1637@galangal.danc.bne.opengear.com> (raw)
In-Reply-To: <CAMKF1srXJ6OA4sUCqJVOoAC7inNGS38UwWgY7TAdEPdMdj5nJg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
Excerpts from Khem Raj's message of 2019-09-30 20:21:38 -07:00:
> Fails in configure
>
> https://errors.yoctoproject.org/Errors/Details/272275/
>
> perhaps xmlto-native docbook-xml-dtd4-native
> docbook-xsl-stylesheets-native deps are needed
Hmm. The recipe already has docbook-xsl-stylesheets-native and
xmlto-native in DEPENDS, which should be sufficient.
The recipe I posted in v2 of my patch builds successfully in our distro,
which is based on Thud. The recipe sysroot has /etc/xml/catalog.xml in
it, and it contains the Docbook XML stuff as expected.
But when I build the recipe in YOE master, I can see that the Docbook
XML is present in the recipe sysroot XML catalog... but the catalog file
is called /etc/xml/catalog, not /etc/xml/catalog.xml.
I wonder if it has changed since Thud, or if there is some other reason
why the name is different in our distro...
--
Dan Callaghan <dan.callaghan@opengear.com>
Software Engineer
Opengear <https://opengear.com/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2019-10-04 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 7:35 [meta-networking][PATCH] firewalld: update to 0.7.1 Dan Callaghan
2019-09-25 16:47 ` Khem Raj
2019-09-30 22:11 ` [meta-networking][PATCH v2] " Dan Callaghan
2019-10-01 3:21 ` Khem Raj
2019-10-04 1:34 ` Dan Callaghan [this message]
2019-10-04 3:11 ` Dan Callaghan
2019-10-04 3:12 ` [meta-networking][PATCH v3] " Dan Callaghan
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=1570152616-sup-1637@galangal.danc.bne.opengear.com \
--to=dan.callaghan@opengear.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.