All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] add SONAME to libblktapctl.so
Date: Thu, 12 Aug 2010 11:42:38 +0200	[thread overview]
Message-ID: <20100812094238.GA13212@aepfle.de> (raw)
In-Reply-To: <19554.42879.224718.693010@mariner.uk.xensource.com>

On Wed, Aug 11, Ian Jackson wrote:

> > -libblktapctl.so: $(CTL_PICS)
> > -	$(CC) $(CFLAGS) -fPIC -shared -rdynamic $^ -o $@
> > +$(LIB_SHARED): $(CTL_PICS)
> > +	$(CC) $(CFLAGS) $(LDFLAGS) -fPIC  -Wl,$(SONAME_LDFLAG) -Wl,$(LIBSONAME) $(SHLIB_LDFLAGS) -rdynamic $^ -o $@
> 
> I'm not sure I understand why -fPIC appears here as a literal, rather
> than being included via some more general make variable.  And does it
> have any effect on the shared library creation link line anyway ?
> Other places that make shared libraries don't have -fPIC there.
> 
> Likewise they don't say -rdynamic.

Ian,

maybe someone has over-done things here. I'm sure libblktapctl is most
likely not different from all the other xen libraries. So I would just
drop -fPIC and -rdynamic from the options.

The gcc manual states that linking should be done with the same options
used to compile the individual objects, to get predictable results. So
if for example -fPIC wasnt there before (in CFLAGS), it wont make the
resulting lib any better.

Olaf

  reply	other threads:[~2010-08-12  9:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 15:23 libblktapctl.so is unversioned Olaf Hering
2010-07-28 15:31 ` Keir Fraser
2010-08-01  9:49   ` [PATCH] add SONAME to libblktapctl.so Olaf Hering
2010-08-11 13:37     ` Ian Jackson
2010-08-12  9:42       ` Olaf Hering [this message]
2010-08-12 13:42         ` Ian Jackson
2010-08-13 12:36           ` Ian Jackson

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=20100812094238.GA13212@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.