From: Olaf Hering <olaf@aepfle.de>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: xen-devel@lists.xensource.com, keir@xen.org, Ian.Campbell@citrix.com
Subject: Re: [PATCH 1/4] tools/flask: remove libflask
Date: Wed, 8 Feb 2012 14:36:45 +0100 [thread overview]
Message-ID: <20120208133645.GA2270@aepfle.de> (raw)
In-Reply-To: <20120207104446.GA31244@aepfle.de>
On Tue, Feb 07, Olaf Hering wrote:
After poking at this some more, isnt the patch removing the libflask
directory? I think it should have removed also all references to that
directory. setup.py (or python 2.6) in SLES11 can not cope with it,
while python 2.7 in openSuSE seems to ignore the remove directory.
I will send a tested patch which removes the references to libflask.
Olaf
> On Fri, Feb 03, Daniel De Graaf wrote:
>
> > This library has been deprecated since July 2010; remove the in-tree
> > users and library.
>
> > - ln -sf libflask.so.$(MAJOR) $(DESTDIR)$(LIBDIR)/libflask.so
>
> > +++ b/tools/python/setup.py
> > @@ -48,7 +48,7 @@ flask = Extension("flask",
> > include_dirs = [ PATH_XEN, PATH_LIBXC, "xen/lowlevel/flask",
> > "../flask/libflask/include" ],
> > library_dirs = [ PATH_LIBXC, "../flask/libflask" ],
> > - libraries = [ "xenctrl", "flask" ],
> > + libraries = [ "xenctrl" ],
> > depends = [ PATH_LIBXC + "/libxenctrl.so",
> > XEN_ROOT + "/tools/flask/libflask/libflask.so" ],
> > sources = [ "xen/lowlevel/flask/flask.c" ])
>
>
> For some reason this changeset does not cause buildfailures in automated
> testing. My xen-unstable rpm packages fail to build in SLES11, but not in
> openSuSE for some reason.
>
> Is there a chance that libflask.so is built after this python thing runs?
> In other words: Is there a makefile dependency missing?
>
> Olaf
>
> ...
> building 'flask' extension
> error: ../../tools/flask/libflask/libflask.so: No such file or directory
> make[3]: *** [install] Error 1
> make[3]: Leaving directory `/usr/src/packages/BUILD/xen-4.2.24701/non-dbg/tools/python'
> make[2]: *** [subdir-install-python] Error 2
> ...
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2012-02-08 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 15:12 [PATCH 0/4] Update flask_op hypercall interface Daniel De Graaf
2012-02-03 15:12 ` [PATCH 1/4] tools/flask: remove libflask Daniel De Graaf
2012-02-07 10:44 ` Olaf Hering
2012-02-08 13:36 ` Olaf Hering [this message]
2012-02-03 15:12 ` [PATCH 2/4] .gitignore/.hgignore: add missing output files Daniel De Graaf
2012-02-03 15:13 ` [PATCH 3/4] flask: Update flask_op hypercall structure Daniel De Graaf
2012-02-03 15:13 ` [PATCH 4/4] xen: Remove unused vsscanf/sscanf functions Daniel De Graaf
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=20120208133645.GA2270@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=keir@xen.org \
--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).