From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Thibault <sthibault@debian.org>
Subject: Re: On distro packaging of stub domains (Re: Notes from
 Xen BoF at Debconf15)
Date: Tue, 8 Sep 2015 19:09:13 +0200
Message-ID: <20150908170913.GA3288@var.home>
References: <1441704296.24450.24.camel@citrix.com>
	<1441705309.24450.35.camel@citrix.com>
	<55EEF8DE.9040807@rumpkernel.org>
	<1441728940.24450.192.camel@citrix.com>
	<20150908162625.GX2610@var.bordeaux.inria.fr>
	<1441730241.24450.207.camel@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72) (envelope-from
	<SRS0=ntQY=JO=ens-lyon.org=samuel.thibault@bounce.ens-lyon.org>)
	id 1ZZMOT-00073o-SW
	for xen-devel@lists.xenproject.org; Tue, 08 Sep 2015 17:09:17 +0000
Content-Disposition: inline
In-Reply-To: <1441730241.24450.207.camel@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>, George.Dunlap@citrix.com, Antti Kantee <pooka@rumpkernel.org>, rumpkernel-users <rumpkernel-users@freelists.org>, xen-devel <xen-devel@lists.xenproject.org>
List-Id: xen-devel@lists.xenproject.org

Ian Campbell, le Tue 08 Sep 2015 17:37:21 +0100, a =E9crit :
> On Tue, 2015-09-08 at 18:26 +0200, Samuel Thibault wrote:
> > Ian Campbell, le Tue 08 Sep 2015 17:15:40 +0100, a =E9crit :
> > > Is it at all possible (even theoretically) to take a shared library
> > > (which
> > > is relocatable as required) and to do a compile time static linking
> > > pass on
> > > it? i.e. use libfoo.so but still do static linking?
> > =

> > =A4 gcc test.c -o libtest.so -shared -Wl,--relocatable
> > /usr/bin/ld.bfd.real: -r and -shared may not be used together
> =

> Sorry, my suggestion was a bit garbled, to say the least... I meant more
> "link an application against it statically even though it is a shared
> library":
> =

> $ gcc main.c -o myapp.elf -static libfoo.so =


Yes, that's what I understood, but the answer is the same: AIUI, once
the library is linked, you can not link again with it, because the code
has already been specialized.

Samuel