From: Samuel Thibault <sthibault@debian.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>
Subject: Re: On distro packaging of stub domains (Re: Notes from Xen BoF at Debconf15)
Date: Tue, 8 Sep 2015 19:09:13 +0200 [thread overview]
Message-ID: <20150908170913.GA3288@var.home> (raw)
In-Reply-To: <1441730241.24450.207.camel@citrix.com>
Ian Campbell, le Tue 08 Sep 2015 17:37:21 +0100, a écrit :
> On Tue, 2015-09-08 at 18:26 +0200, Samuel Thibault wrote:
> > Ian Campbell, le Tue 08 Sep 2015 17:15:40 +0100, a écrit :
> > > 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?
> >
> > € 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
next prev parent reply other threads:[~2015-09-08 17:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 9:24 Notes from Xen BoF at Debconf15 Ian Campbell
2015-09-08 9:41 ` On distro packaging of stub domains (Re: Notes from Xen BoF at Debconf15) Ian Campbell
2015-09-08 15:03 ` Antti Kantee
2015-09-08 16:15 ` Ian Campbell
2015-09-08 16:26 ` Samuel Thibault
2015-09-08 16:37 ` Ian Campbell
2015-09-08 17:09 ` Samuel Thibault [this message]
2015-09-08 18:38 ` Antti Kantee
2015-09-09 11:15 ` Ian Campbell
2015-09-09 13:42 ` Antti Kantee
2015-09-08 9:47 ` Notes from Xen BoF at Debconf15 Jan Beulich
2015-09-08 10:15 ` Lars Kurth
2015-09-08 10:15 ` Ian Campbell
2015-09-08 10:39 ` Jan Beulich
2015-09-08 10:49 ` Ian Jackson
2015-09-08 10:55 ` Jan Beulich
2015-09-08 14:52 ` Doug Goldstein
2015-09-08 14:49 ` Doug Goldstein
2015-09-08 15:24 ` Ian Campbell
2015-09-17 10:06 ` George Dunlap
2015-09-16 13:20 ` Ian Campbell
2015-10-05 15:37 ` Ian Campbell
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=20150908170913.GA3288@var.home \
--to=sthibault@debian.org \
--cc=George.Dunlap@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=pkg-xen-devel@lists.alioth.debian.org \
--cc=pooka@rumpkernel.org \
--cc=rumpkernel-users@freelists.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 NNTP newsgroup(s).