xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: rshriram@cs.ubc.ca
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 4 of 4 RFC] xl/remus: Add libnl3 dependency to autoconf scripts and libxl/Makefile
Date: Mon, 29 Jul 2013 16:41:20 +0100	[thread overview]
Message-ID: <51F68D20.9090400@citrix.com> (raw)
In-Reply-To: <CAP8mzPPTvTeY5=UydnswjiJyiGhpz07ExfmxGax6myiwVMh9zg@mail.gmail.com>

On 29/07/13 14:07, Shriram Rajagopalan wrote:
> On Mon, Jul 29, 2013 at 1:58 AM, Wen Congyang <wency@cn.fujitsu.com> wrote:
>>> If I use AC_CHECK_LIB and AC_CHECK_HEADERS, would it automatically add the
>>> include path to CFLAGS, such that I wouldnt have to manually specify
>>> -I flags in libxl/Makefile ?
>>
>> No. AC_CHECK_HEADERS can check if the header file is under the default directory.
>> If the header file is under the directory /usr/include, you can use it.
>> But why your header file is under the directory /usr/local/include?
>>
> 
> I think its because I installed libnl3 in /usr/local, from the sources.
> If there is a proper way to specify custom install directories for
> certain libraries,
> then I dont think we need that hard coded -I /usr/local/include/libnl3

You need to tell pkg-config where to find the .pc file.  I don't recall
the details for how to do this. PKG_CONFIG_PATH perhaps?

David

  reply	other threads:[~2013-07-29 15:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  7:09 [PATCH 0 of 4 RFC] xl - Remus network buffering support Shriram Rajagopalan
2013-07-25  7:09 ` [PATCH 1 of 4 RFC] xl/remus : Network buffering setup helper functions Shriram Rajagopalan
2013-07-29 15:42   ` Ian Campbell
2013-07-29 18:00     ` Shriram Rajagopalan
2013-07-30 10:44       ` Ian Campbell
2013-07-25  7:09 ` [PATCH 2 of 4 RFC] xl/remus: Network buffering cmdline switch, setup/teardown Shriram Rajagopalan
2013-07-29 15:49   ` Ian Campbell
2013-07-29 19:00     ` Shriram Rajagopalan
2013-07-30 10:50       ` Ian Campbell
2013-07-30 15:25         ` Shriram Rajagopalan
2013-07-30 15:39           ` Ian Campbell
2013-07-25  7:09 ` [PATCH 3 of 4 RFC] xl/remus: Control network buffering in remus callbacks Shriram Rajagopalan
2013-07-29 16:06   ` Ian Campbell
2013-08-07 15:41     ` Ian Jackson
2013-08-07 15:38   ` Ian Jackson
2013-08-07 21:51     ` Shriram Rajagopalan
2013-08-08 11:07       ` Ian Jackson
2013-07-25  7:09 ` [PATCH 4 of 4 RFC] xl/remus: Add libnl3 dependency to autoconf scripts and libxl/Makefile Shriram Rajagopalan
2013-07-26  9:44   ` Wen Congyang
2013-07-26 13:51     ` Shriram Rajagopalan
2013-07-26  9:56   ` David Vrabel
2013-07-26 13:56     ` Shriram Rajagopalan
2013-07-29  5:58       ` Wen Congyang
2013-07-29 13:07         ` Shriram Rajagopalan
2013-07-29 15:41           ` David Vrabel [this message]
2013-07-30 16:11 ` [PATCH 0 of 4 RFC] xl - Remus network buffering support Roger Pau Monné
2013-07-31  8:33   ` 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=51F68D20.9090400@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=rshriram@cs.ubc.ca \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wency@cn.fujitsu.com \
    --cc=xen-devel@lists.xen.org \
    /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).