public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH 1/2] gdb: use update-alternatives for sframe-spec.info
Date: Fri, 21 Apr 2023 14:06:15 +0800	[thread overview]
Message-ID: <1682057176-19939-1-git-send-email-wangmy@fujitsu.com> (raw)

From: Wang Mingyu <wangmy@fujitsu.com>

binutils also uses the doc 'sframe-spec.info'.

binutils has a priority of 100.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 meta/recipes-devtools/gdb/gdb-common.inc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/meta/recipes-devtools/gdb/gdb-common.inc b/meta/recipes-devtools/gdb/gdb-common.inc
index 925b0c2f80..338d1650d2 100644
--- a/meta/recipes-devtools/gdb/gdb-common.inc
+++ b/meta/recipes-devtools/gdb/gdb-common.inc
@@ -53,6 +53,12 @@ do_configure () {
 
 # we don't want gdb to provide bfd/iberty/opcodes, which instead will override the
 # right bits installed by binutils.  Same for bfd.info -- also from binutils.
+inherit update-alternatives
+
+ALTERNATIVE_PRIORITY = "50"
+ALTERNATIVE:${PN}-doc = "sframe-spec"
+ALTERNATIVE_LINK_NAME[sframe-spec] = "${infodir}/sframe-spec.info"
+
 do_install:append() {
 	rm -rf ${D}${libdir}
 	rm -rf ${D}${includedir}
-- 
2.34.1



             reply	other threads:[~2023-04-21  6:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21  6:06 wangmy [this message]
2023-04-21  6:06 ` [OE-core] [PATCH 2/2] binutils: use update-alternatives for sframe-spec.info wangmy
2023-04-21  6:19 ` [OE-core] [PATCH 1/2] gdb: " Khem Raj

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=1682057176-19939-1-git-send-email-wangmy@fujitsu.com \
    --to=wangmy@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