public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Potharla, Rupesh" <Rupesh.Potharla@amd.com>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>,
	"Parasuraman, Hariharan" <Hariharan.Parasuraman@amd.com>,
	"Kumar N, Bhuvanendra" <Bhuvanendra.KumarN@amd.com>,
	"Potharla, Rupesh via Binutils" <binutils@sourceware.org>
Subject: Re: Need help buiding bfd shared library
Date: Wed, 3 Aug 2022 08:43:32 +0200	[thread overview]
Message-ID: <29cd6b36-a86c-3a5c-9338-1657a35b4901@suse.com> (raw)
In-Reply-To: <DM6PR12MB42195F0F19743C8DBA7B650BE79C9@DM6PR12MB4219.namprd12.prod.outlook.com>

On 03.08.2022 08:09, Potharla, Rupesh via Binutils wrote:
> I am working on building bfd shared library for my code changes. I tried with "configure --enable-shared=bfd" but BFD is creating static library only even with -enable-shared option .  Did I miss something ? Can someone help me with the instructions to build bfd shared library?

Did you try --enable-shared without "=bfd"? So far I wasn't aware of
that form as an option, and at least a quick inspection of the
configure script also doesn't suggest that form might exist. But I
may be entirely wrong ...

Jan

  reply	other threads:[~2022-08-03  6:43 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 [this message]
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
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=29cd6b36-a86c-3a5c-9338-1657a35b4901@suse.com \
    --to=jbeulich@suse.com \
    --cc=Bhuvanendra.KumarN@amd.com \
    --cc=Hariharan.Parasuraman@amd.com \
    --cc=JiniSusan.George@amd.com \
    --cc=Rupesh.Potharla@amd.com \
    --cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).