From: Dodji Seketeli <dodji@seketeli.org>
To: tangmeng <tangmeng@uniontech.com>
Cc: libabigail@sourceware.org
Subject: Re: [PATCH v2] abicompat: Add prompt message for abnormal operation
Date: Tue, 02 Nov 2021 10:18:27 +0100 [thread overview]
Message-ID: <871r3yapb0.fsf@seketeli.org> (raw)
In-Reply-To: <20211029092343.32219-1-tangmeng@uniontech.com> (tangmeng@uniontech.com's message of "Fri, 29 Oct 2021 17:23:43 +0800")
Hello,
tangmeng <tangmeng@uniontech.com> a écrit:
> When using abicompat, if the user configures the
> lib2 path while using the xxx option, the configuration
> of lib2 is not actually processed in the command
> execution process, and there is no prompt message.
> It will cause lib2 to be considered to have been processed,
> so a warning is added here to prompt the user.
Thanks! I have just re-worded this introduction a little bit.
[...]
> -/// An description of a change of the type of a function. It contains
> +/// An description of a change of the type of a function. It contains
It's a common pattern we use throughout the code to add one extra space
after the dot. This is convention used in the code of GNU projects and
we kept it for historical reasons. So it's not a problem. I changed
the "An description" into "A description", however.
So, here is the patch that was applied to the master branch of the Git
repository.
Thanks!
From ba18218ec2b8cf32b86aef4c4b539411ef0bd645 Mon Sep 17 00:00:00 2001
From: tangmeng <tangmeng@uniontech.com>
Date: Fri, 29 Oct 2021 17:23:43 +0800
Subject: [PATCH] abicompat: Add prompt message for abnormal operation
When using abicompat, if the uses the --weak-mode option and also
provides a lib2 path on the command line, the lib2 path is silently
ignored.
This patch provides a warning to notify the user that the lib2 path is
ignored in that case.
* tools/abicompat.cc (main): Notify the user when the path to
the second library is ignored because the --weak-mode option
was provided. Also, fix comment.
Signed-off-by: tangmeng <tangmeng@uniontech.com>
Signed-off-by: Dodji Seketeli <dodji@redhat.com>
---
tools/abicompat.cc | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tools/abicompat.cc b/tools/abicompat.cc
index 60cd794f..cf944a49 100644
--- a/tools/abicompat.cc
+++ b/tools/abicompat.cc
@@ -390,7 +390,7 @@ perform_compat_check_in_normal_mode(options& opts,
return status;
}
-/// An description of a change of the type of a function. It contains
+/// A description of a change of the type of a function. It contains
/// the declaration of the function we are interested in, as well as
/// the differences found in the type of that function.
struct fn_change
@@ -638,6 +638,13 @@ main(int argc, char* argv[])
return 0;
}
+ if (opts.weak_mode && !opts.lib2_path.empty())
+ {
+ emit_prefix(argv[0], cout)
+ << "WARNING: The \'--weak-mode\' option is used. The "
+ << opts.lib2_path << " will be ignored automatically\n";
+ }
+
ABG_ASSERT(!opts.app_path.empty());
if (!abigail::tools_utils::check_file(opts.app_path, cerr, opts.prog_name))
return abigail::tools_utils::ABIDIFF_ERROR;
--
2.32.0
--
Dodji
next prev parent reply other threads:[~2021-11-02 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 9:23 tangmeng
2021-11-02 9:18 ` Dodji Seketeli [this message]
2021-11-05 9:38 tangmeng
2021-11-09 10:18 ` Dodji Seketeli
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=871r3yapb0.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=libabigail@sourceware.org \
--cc=tangmeng@uniontech.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).