xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Nathan March <nathan@gt.net>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.1.0 RC2 released,
Date: Fri, 28 Jan 2011 11:22:58 -0800	[thread overview]
Message-ID: <4D431792.2040303@gt.net> (raw)
In-Reply-To: <1296241979.20804.88.camel@localhost.localdomain>

On 1/28/2011 11:12 AM, Ian Campbell wrote:
> Can you try moving the $(DLOPEN_LIBS) in the libxenctrl rule in
> tools/libxc/Makefile to the end, e.g. before or after the
> $(PTHREAD_LIBS)?
>
> Ian.

Moving it to the end fixed it:

-       $(CC) $(CFLAGS) $(LDFLAGS) -Wl,$(SONAME_LDFLAG) 
-Wl,libxenctrl.so.$(MAJOR) $(DLOPEN_LIBS) $(SHLIB_LDFLAGS) -o $@ $^ 
$(PTHREAD_LIBS)
+       $(CC) $(CFLAGS) $(LDFLAGS) -Wl,$(SONAME_LDFLAG) 
-Wl,libxenctrl.so.$(MAJOR) $(SHLIB_LDFLAGS) -o $@ $^ $(PTHREAD_LIBS) 
$(DLOPEN_LIBS)

But I'm still running into issues, this time with libvhd:

gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g 
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD 
-MF .vhd-util.d  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -Werror 
-Wno-unused -I../include -D_GNU_SOURCE -fPIC -Wp,-MD,.vhd-util.d    -o 
vhd-util vhd-util.o -Llib -lvhd -luuid
lib/libvhd.so: undefined reference to `uuid_generate'
lib/libvhd.so: undefined reference to `uuid_copy'
lib/libvhd.so: undefined reference to `uuid_is_null'
lib/libvhd.so: undefined reference to `uuid_unparse'
lib/libvhd.so: undefined reference to `uuid_clear'
lib/libvhd.so: undefined reference to `uuid_compare'
collect2: ld returned 1 exit status

The line that built libvhd.so was:

gcc  -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g 
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD 
-MF .libvhd.o.d  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -Werror 
-Wno-unused -I../../include -D_GNU_SOURCE -fPIC -g -Wp,-MD,.libvhd.o.d 
-c -o libvhd.o libvhd.c

- Nathan

  reply	other threads:[~2011-01-28 19:22 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 [this message]
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
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=4D431792.2040303@gt.net \
    --to=nathan@gt.net \
    --cc=Ian.Campbell@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 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).