public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Jan Beulich via Binutils <binutils@sourceware.org>
Cc: "Potharla, Rupesh" <Rupesh.Potharla@amd.com>,
	 Jan Beulich <jbeulich@suse.com>,
	 "George, Jini Susan" <JiniSusan.George@amd.com>,
	"Parasuraman, Hariharan" <Hariharan.Parasuraman@amd.com>,
	 "Kumar N, Bhuvanendra" <Bhuvanendra.KumarN@amd.com>
Subject: Re: Need help buiding bfd shared library
Date: Thu, 04 Aug 2022 12:01:43 +0200	[thread overview]
Message-ID: <mvmfsicmins.fsf@suse.de> (raw)
In-Reply-To: <40329f23-48d8-9c43-f3ab-0021b7187b27@suse.com> (Jan Beulich via Binutils's message of "Thu, 4 Aug 2022 11:47:19 +0200")

On Aug 04 2022, Jan Beulich via Binutils wrote:

> No, I cannot. As said previously, all I ever use is --enable-shared
> (without any "=bfd").

AC_DISABLE_SHARED supports `--enable-shared=PKGS', but there are some
places that use `test "$enable_shared" = yes' instead of `test
"$enable_shared" != no'.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2022-08-04 10:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03  6:09 Potharla, Rupesh
2022-08-03  6:43 ` Jan Beulich
2022-08-03  6:49   ` Potharla, Rupesh
2022-08-03  6:58     ` Jan Beulich
2022-08-03 18:59       ` Potharla, Rupesh
2022-08-04  6:46         ` Jan Beulich
2022-08-04  9:45           ` Potharla, Rupesh
2022-08-04  9:47             ` Jan Beulich
2022-08-04 10:01               ` Andreas Schwab [this message]
2022-08-04 10:02               ` Errol Millios

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=mvmfsicmins.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=Bhuvanendra.KumarN@amd.com \
    --cc=Hariharan.Parasuraman@amd.com \
    --cc=JiniSusan.George@amd.com \
    --cc=Rupesh.Potharla@amd.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.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).