On Wed, Sep 19, 2007 at 04:27:03AM -0400, Daniel Veillard wrote:
> On Wed, Sep 19, 2007 at 03:31:50AM +0100, Daniel P. Berrange wrote:
> > On Wed, Sep 19, 2007 at 12:30:18AM +0100, Daniel P. Berrange wrote:
> > > On Tue, Sep 18, 2007 at 02:29:50AM +0100, Daniel P. Berrange wrote:
> > > > Currently
On Wed, Sep 19, 2007 at 03:31:50AM +0100, Daniel P. Berrange wrote:
> On Wed, Sep 19, 2007 at 12:30:18AM +0100, Daniel P. Berrange wrote:
> > On Tue, Sep 18, 2007 at 02:29:50AM +0100, Daniel P. Berrange wrote:
> > > Currently if you have a configured working directory and you touch some
> > > file
On Wed, Sep 19, 2007 at 12:30:18AM +0100, Daniel P. Berrange wrote:
> On Tue, Sep 18, 2007 at 02:29:50AM +0100, Daniel P. Berrange wrote:
> > Currently if you have a configured working directory and you touch some
> > file that would cause autoconf to re-run configure it'll crash & burn with
> > an
On Tue, Sep 18, 2007 at 02:29:50AM +0100, Daniel P. Berrange wrote:
> Currently if you have a configured working directory and you touch some
> file that would cause autoconf to re-run configure it'll crash & burn with
> an error like
Here is an alternative version which makes the pkg-config check
On Tue, Sep 18, 2007 at 10:31:58PM +0100, Daniel P. Berrange wrote:
> Of the series of patches I sent we'll have libxml, gnutls, avahi and
> PolicyKit.
We have pc files for the first two. The second two we're still looking
at but I presume we'll be planning on .pc's for those too
cheers
john
-
On Tue, Sep 18, 2007 at 05:39:09PM +0100, John Levon wrote:
> On Tue, Sep 18, 2007 at 03:32:35AM -0400, Daniel Veillard wrote:
>
> > In the case of libvirt though we may conclude that we target only OSes
> > where pkg-config is set up, could someone clarify to me the status of
> > pkg-config (at
On Tue, Sep 18, 2007 at 03:32:35AM -0400, Daniel Veillard wrote:
> In the case of libvirt though we may conclude that we target only OSes
> where pkg-config is set up, could someone clarify to me the status of
> pkg-config (at least for libxml2) on:
> - Solaris (I guess yes)
We have .pc fi
On Tue, Sep 18, 2007 at 02:40:06PM +0100, Daniel P. Berrange wrote:
> On Tue, Sep 18, 2007 at 03:32:35AM -0400, Daniel Veillard wrote:
> > only if the OS integration decided to make it work. To me the goal of
> > configure
> > is to get maximum portability (otherwise honnestly, why bother with the
On Tue, Sep 18, 2007 at 03:32:35AM -0400, Daniel Veillard wrote:
> On Tue, Sep 18, 2007 at 02:29:50AM +0100, Daniel P. Berrange wrote:
> > Currently if you have a configured working directory and you touch some
> > file that would cause autoconf to re-run configure it'll crash & burn with
> > an er
On Tue, Sep 18, 2007 at 02:29:50AM +0100, Daniel P. Berrange wrote:
> Currently if you have a configured working directory and you touch some
> file that would cause autoconf to re-run configure it'll crash & burn with
> an error like
>
>
> $ make
> cd . && /bin/sh /home/berrange/src/xen/libvirt/
Currently if you have a configured working directory and you touch some
file that would cause autoconf to re-run configure it'll crash & burn with
an error like
$ make
cd . && /bin/sh /home/berrange/src/xen/libvirt/missing --run aclocal-1.9 -I m4
cd . && /bin/sh /home/berrange/src/xen/libvirt/mis
11 matches
Mail list logo
