All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Vehlow <lkml@jv-coder.de>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] configure.ac: Fix summary for disabled metadata
Date: Fri, 14 Jan 2022 15:27:38 +0100	[thread overview]
Message-ID: <f516568b-fa33-091c-3442-0316a78d96b1@jv-coder.de> (raw)
In-Reply-To: <YeGHV+Gnmo59SXeL@yuki>

Hi

Am 1/14/2022 um 3:23 PM schrieb Cyril Hrubis:
> The JSON metadata file is going to replace the runtest files some day,
> at least that is the longterm plan. Also the parser that extracts the
> metadata from the sources is rather fast, compared to the LTP build and
> it's self contained. There is really no reason to have a switch to
> disable the metadat extraction step.
> 
> The documentation build, on the other hand, is rather slow and requires
> asciidoc, which is the reason why there is a switch that can be used to
> disable that. The only problem here is that the name is a bit confusing
> now.
> 
Actually there is, that is where my interest in this flag comes from. We
don't use runtest files (at least not for execution), so we don't need
it and we had problems in out cross build environment, that were not
easily fixed. From looking at the source I am not sure what the problem
was and cannot spot it from looking at the source. But I know, that it
wasn't just fixed by setting the correct HOSTCC and HOST_CFLAGS. I have
a missing library in my head, but I can't see any.
All I know is that I gave up fixing the build and I don't give up easily
normally (a little easier if the functionality is not needed at all) :)

Joerg

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-01-14 14:27 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
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 [this message]
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=f516568b-fa33-091c-3442-0316a78d96b1@jv-coder.de \
    --to=lkml@jv-coder.de \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.