xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Nathan March <nathan@gt.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.1.0 RC2 released,
Date: Sat, 29 Jan 2011 10:45:36 +0000	[thread overview]
Message-ID: <1296297936.20804.123.camel@localhost.localdomain> (raw)
In-Reply-To: <4D43422A.80202@gt.net>

On Fri, 2011-01-28 at 22:24 +0000, Nathan March wrote: 
> On 1/28/2011 1:54 PM, Ian Campbell wrote:
> > Can you try adding $(LDLIBS_libxenctrl) and $(LDLIBS_libxenstore) to the
> > end of the link line for libxenlight.so
> 
> No luck. That resulted in this:
[...] 
> I also tried putting those two vars in at the beginning and just before 
> the -o, but didn't help.

Hrm. Same missing symbols as before?

Taking a step back, since I think this patch is becoming a little bit
too much for a 4.1.0-rc3, lets consider how we can disable as-needed for
Xen 4.1.0 and revisit the situation for 4.2 (with the possibility of a
back port for 4.1.1 as well).

I don't see any as-needed in your link lines so I presume it was enabled
as a compile time option in your ld. 

I just built Xen with the following patch and it didn't break on a
Debian system (i.e. without as-needed enabled by default). Can you try
it in your environment?

diff -r d2c7cf306687 config/StdGNU.mk
--- a/config/StdGNU.mk	Sat Jan 29 10:33:04 2011 +0000
+++ b/config/StdGNU.mk	Sat Jan 29 10:39:07 2011 +0000
@@ -65,6 +65,8 @@ SONAME_LDFLAG = -soname
 SONAME_LDFLAG = -soname
 SHLIB_LDFLAGS = -shared
 
+LDFLAGS += -Wl,--no-as-needed
+
 ifneq ($(debug),y)
 CFLAGS += -O2 -fomit-frame-pointer
 else

For 4.2 I was hoping to revisit the issue of libraries not being
correctly transitively linked (e.g. libxl is supposed to isolate users
from the need to know about libxenctrl and libxenstore so applications
which use only libxl should not be expected to have to link with
-lxenctrl and -lxenstore). I suspect that there will be a lot of overlap
with this and supporting --as-needed as the latter is essentially a
workaround for the lack of the former. 

Ian.

  reply	other threads:[~2011-01-29 10:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 23:05 Xen 4.1.0 RC2 released, Nathan March
2011-01-28  8:53 ` Ian Campbell
2011-01-28 19:09   ` Nathan March
2011-01-28 19:12     ` Ian Campbell
2011-01-28 19:22       ` Nathan March
2011-01-28 19:36         ` Ian Campbell
2011-01-28 21:19           ` Nathan March
2011-01-28 21:54             ` Ian Campbell
2011-01-28 22:24               ` Nathan March
2011-01-29 10:45                 ` Ian Campbell [this message]
2011-01-31 18:14                   ` Nathan March
2011-01-31 19:30                     ` Ian Campbell
2011-01-31 19:54                       ` Nathan March
2011-02-01 18:51                       ` Ian Jackson
2011-02-01 18:53                         ` Ian Campbell
2011-03-21 14:43                   ` Ian Campbell
2011-04-01 17:38                     ` Nathan March
2011-04-01 18:35                       ` 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=1296297936.20804.123.camel@localhost.localdomain \
    --to=ian.campbell@eu.citrix.com \
    --cc=nathan@gt.net \
    --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 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).