public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH v2 3/4] x86: break gas dependency on libopcodes
Date: Fri, 18 Nov 2022 10:13:24 +0100	[thread overview]
Message-ID: <fad783e7-e00a-c3c1-cb6d-89b70816a737@suse.com> (raw)
In-Reply-To: <7a1ee76a-5b54-32a6-6301-a1741b5c1883@suse.com>

gas doesn't use anything from libopcodes anymore - suppress linking in
that library.
---
v2: New, split off from larger earlier patch.

--- a/gas/configure
+++ b/gas/configure
@@ -12263,7 +12263,7 @@ _ACEOF
 
     # Do we need the opcodes library?
     case ${cpu_type} in
-      vax | tic30)
+      vax | tic30 | i386)
 	;;
 
       *)
--- a/gas/configure.ac
+++ b/gas/configure.ac
@@ -420,7 +420,7 @@ changequote([,])dnl
 
     # Do we need the opcodes library?
     case ${cpu_type} in
-      vax | tic30)
+      vax | tic30 | i386)
 	;;
 
       *)


  parent reply	other threads:[~2022-11-18  9:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  9:10 [PATCH v2 0/4] " Jan Beulich
2022-11-18  9:12 ` [PATCH v2 1/4] x86: instantiate i386_{op,reg}tab[] in gas instead of in libopcodes Jan Beulich
2022-11-18  9:13 ` [PATCH v2 2/4] x86: remove i386-opc.c Jan Beulich
2022-11-18  9:13 ` Jan Beulich [this message]
2022-11-21 16:26   ` [PATCH v2 3/4] x86: break gas dependency on libopcodes H.J. Lu
2022-11-21 16:32     ` Jan Beulich
2022-11-21 16:43       ` H.J. Lu
2022-11-21 16:52         ` Jan Beulich
2022-11-21 17:04           ` H.J. Lu
2022-11-22  7:15             ` Jan Beulich
2022-11-22 16:38               ` H.J. Lu
2022-11-22 17:05                 ` Jan Beulich
2022-11-22 18:21                   ` H.J. Lu
2022-11-18  9:14 ` [PATCH v2 4/4] x86: drop sentinel from i386_optab[] Jan Beulich

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=fad783e7-e00a-c3c1-cb6d-89b70816a737@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.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).