From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from picard.linux.it (picard.linux.it [213.254.12.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8D036C433F5 for ; Fri, 14 Jan 2022 17:54:58 +0000 (UTC) Received: from picard.linux.it (localhost [IPv6:::1]) by picard.linux.it (Postfix) with ESMTP id 877F53C9534 for ; Fri, 14 Jan 2022 18:54:56 +0100 (CET) Received: from in-5.smtp.seeweb.it (in-5.smtp.seeweb.it [217.194.8.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by picard.linux.it (Postfix) with ESMTPS id 6D7F33C1020 for ; Fri, 14 Jan 2022 18:54:46 +0100 (CET) Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by in-5.smtp.seeweb.it (Postfix) with ESMTPS id E7F07600F28 for ; Fri, 14 Jan 2022 18:54:45 +0100 (CET) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 072C7219AA; Fri, 14 Jan 2022 17:54:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1642182885; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5BmWVh/4ZKY0zpNfko93bTzamDDpc2VZFa1gOD3qAF4=; b=ek7fjYRYYeNLoiG2UErMkOXKHiOmq73u9azZx3rdJXkcCsYoB/mNZY8DurEj4Vg5uBAbLr ROzDXzDzN8oE9mFixqrbRvaERexlaatb0oCMNPPcnY2x+ChxPEpyvn2GnsaGbHnF6biozr Z0/5gdJf+N9GyHi1F90uqMXuQLa91gk= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1642182885; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5BmWVh/4ZKY0zpNfko93bTzamDDpc2VZFa1gOD3qAF4=; b=MpG+NnKA2nKgpNLWgcTmWXftwQHYl8Kx+KINSk/ZpygpElxkxLQvcVQPIbvQuZedwGu8qm Hgeei+6wPVyRp7Cw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 978B213BB8; Fri, 14 Jan 2022 17:54:44 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id RRSeIuS44WHoGAAAMHmgww (envelope-from ); Fri, 14 Jan 2022 17:54:44 +0000 Date: Fri, 14 Jan 2022 18:54:42 +0100 From: Petr Vorel To: Cyril Hrubis Message-ID: References: <20220114125513.895-1-pvorel@suse.cz> <95394feb-6474-d1ca-13d8-3d1c35e781b9@jv-coder.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Virus-Scanned: clamav-milter 0.102.4 at in-5.smtp.seeweb.it X-Virus-Status: Clean Subject: Re: [LTP] [PATCH 1/1] configure.ac: Fix summary for disabled metadata X-BeenThere: ltp@lists.linux.it X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Test Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Petr Vorel Cc: ltp@lists.linux.it Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-bounces+ltp=archiver.kernel.org@lists.linux.it Sender: "ltp" > Hi! > > > 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. > That is really strange, there are practically no dependencies for the > metadata extractor. All that you have to have is a C compiler and libc. > > 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) :) > You should have reported that on the list. It's going to be really > cornerstone of the way how tests are executed so the build should get > fixed anyways. It's a question if it's a problem of building C or a problem of integrating LTP build to another build system. > I guess that we can add a flag that disables the metadata extraction > step, with a big red warning that describes the consequencies of the > choice. Let's see if we can solve the problem. If not, it might help also to others to have flag disabling all metadata build (probably named --disable-metadata and name current --disable-metadata functionality as --disable-docparse). Kind regards, Petr -- Mailing list info: https://lists.linux.it/listinfo/ltp