From: Joerg Vehlow <lkml@jv-coder.de>
To: Petr Vorel <pvorel@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] configure.ac: Fix summary for disabled metadata
Date: Fri, 14 Jan 2022 14:12:31 +0100 [thread overview]
Message-ID: <52627525-6455-4e39-a969-12938e1df05e@jv-coder.de> (raw)
In-Reply-To: <20220114125513.895-1-pvorel@suse.cz>
Hi Petr,
Am 1/14/2022 um 1:55 PM schrieb Petr Vorel:
> Previously with --disable-metadata output didn't mention that metadata
> are disabled and printed config which was not used. Now>
> $ ./configure --disable-metadata
a bit out of context here, but still: The disable-metadata flag is
confusing, because it does not disable metadata entirely. We had to
patch the makefile, to disable build of mateparse. While this is
basically setup correctly for cross compilation, we had some problems,
if the HOSTCC version did not match the CC version.
I am not entirely sure what the problem was, only that we did not care,
because we don't need metaparse end disabling it was simpler than fixing
the build.
Long story short: "--disable-metadata" should completely disable
metadata parsing, not only document generation
Joerg
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-14 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 12:55 [LTP] [PATCH 1/1] configure.ac: Fix summary for disabled metadata Petr Vorel
2022-01-14 13:12 ` Joerg Vehlow [this message]
2022-01-14 14:12 ` Cyril Hrubis
2022-01-14 14:16 ` Joerg Vehlow
2022-01-14 14:23 ` Cyril Hrubis
2022-01-14 14:27 ` Joerg Vehlow
2022-01-14 14:51 ` Cyril Hrubis
2022-01-14 17:54 ` Petr Vorel
2022-01-14 17:44 ` Petr Vorel
2022-01-18 15:12 ` Cyril Hrubis
2022-01-18 15:49 ` Petr Vorel
2022-01-18 16:07 ` Cyril Hrubis
2022-01-18 16:47 ` Petr Vorel
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=52627525-6455-4e39-a969-12938e1df05e@jv-coder.de \
--to=lkml@jv-coder.de \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.