From: Robert Yang <liezhi.yang@windriver.com>
To: Li Zhijian <lizhijian@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [Question] libxml: How about add --with-catalog to EXTRA_OECONF ?
Date: Fri, 30 Aug 2013 16:16:50 +0800 [thread overview]
Message-ID: <522054F2.3020306@windriver.com> (raw)
In-Reply-To: <522033C9.7050804@cn.fujitsu.com>
On 08/30/2013 01:55 PM, Li Zhijian wrote:
> libxml2 is built successfully with option of --with-catalog,and xmlcatalog
> work well
>
> Maybe I would send a patch to fix it.
>
Yes, that would be great, thanks.
// Robert
> Thanks
> Li
>
> at 2013-8-29 14:52, Robert Yang wrote:
>>
>> I took a look at the libxml's git log, didn't see the explicit reason
>> that why use the --without-catalog, so it seems reasonable to use the
>> --with-catalog which will make the xmlcatalog work (if it can be built
>> well with the option.)
>>
>> // Robert
>>
>> On 08/29/2013 09:46 AM, Li Zhijian wrote:
>>> Hi,
>>>
>>> I had build libxml and executed xmlcatalog
>>> It shows follow messages
>>> # xmlcatalog --help
>>> libxml was not compiled with catalog and output support
>>>
>>> meta/recipes-core/libxml/libxml2.inc: 32
>>> EXTRA_OECONF = "--without-python --without-debug --without-legacy
>>> --without-catalog --without-docbook --with-c14n --without-lzma
>>> --with-fexceptions"
>>>
>>> Is it reasonable to add --without-catalog EXTRA_OECONF ?
>>>
>>> Thanks
>>>
>>> Best regards.
>>> Li Zhijian
>>>
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>>
>>
>>
>
>
prev parent reply other threads:[~2013-08-30 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 1:46 [Question] libxml: How about add --with-catalog to EXTRA_OECONF ? Li Zhijian
2013-08-29 6:52 ` Robert Yang
2013-08-30 5:55 ` Li Zhijian
2013-08-30 8:16 ` Robert Yang [this message]
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=522054F2.3020306@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=lizhijian@cn.fujitsu.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