From: Dulloor <dulloor@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: linker error with xen-tools (tip)
Date: Thu, 1 Apr 2010 02:01:42 -0400 [thread overview]
Message-ID: <r2x940bcfd21003312301t6b76c71x688163dfe8346c07@mail.gmail.com> (raw)
In-Reply-To: <u2o940bcfd21003312257he8a1ce7aracf1bf27ac0598e1@mail.gmail.com>
Also, "make clean" doesn't help either. The error goes away only on a
(trial and error) reordering of my patch set.
-dulloor
On Thu, Apr 1, 2010 at 1:57 AM, Dulloor <dulloor@gmail.com> wrote:
> With my modifications to libxc(adding/modifying a few files), I get
> the following error, but only intermittently. There are no compilation
> errors in my code. And, also interestingly when I add back the same
> changes piece-meal and in a different order, this linker error
> disappears. What could be the reason ?
>
> gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99
> -Wall -Wstrict-prototypes -Wno-unused-value
> -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF
> .loadpolicy.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wall -g
> -Werror -I../../../tools/libxc -I../../../tools/include
> -I../../../tools/flask/libflask/include -I. -c -o loadpolicy.o
> loadpolicy.c
> gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99
> -Wall -Wstrict-prototypes -Wno-unused-value
> -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF
> .flask-loadpolicy.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wall
> -g -Werror -I../../../tools/libxc -I../../../tools/include
> -I../../../tools/flask/libflask/include -I. -L../../../tools/libxc
> -L../../../tools/flask/libflask loadpolicy.o -L. -lflask
> -L../../../tools/libxc -lxenctrl -o flask-loadpolicy
> ../../../tools/libxc/libxenctrl.so: undefined reference to `xc_dom_printf'
> collect2: ld returned 1 exit status
> make[5]: *** [flask-loadpolicy] Error 1
> make[5]: Leaving directory
> `/data/devel/xen-devel/xen-unstable-numa-tip.hg/tools/flask/utils'
> make[4]: *** [subdir-install-utils] Error 2
> make[4]: Leaving directory
> `/data/devel/xen-devel/xen-unstable-numa-tip.hg/tools/flask'
> make[3]: *** [subdirs-install] Error 2
> make[3]: Leaving directory
> `/data/devel/xen-devel/xen-unstable-numa-tip.hg/tools/flask'
> make[2]: *** [subdir-install-flask] Error 2
> make[2]: Leaving directory
> `/data/devel/xen-devel/xen-unstable-numa-tip.hg/tools'
> make[1]: *** [subdirs-install] Error 2
> make[1]: Leaving directory
> `/data/devel/xen-devel/xen-unstable-numa-tip.hg/tools'
> make: *** [install-tools] Error 2
>
next prev parent reply other threads:[~2010-04-01 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 5:57 linker error with xen-tools (tip) Dulloor
2010-04-01 6:01 ` Dulloor [this message]
2010-04-01 6:32 ` Dulloor
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=r2x940bcfd21003312301t6b76c71x688163dfe8346c07@mail.gmail.com \
--to=dulloor@gmail.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).