xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: libcacard is been installed to /usr/lib while libdir=/usr/lib64
Date: Tue, 20 May 2014 09:00:09 -0400	[thread overview]
Message-ID: <537B51D9.7070605@oracle.com> (raw)
In-Reply-To: <1400589649.6946.31.camel@kazak.uk.xensource.com>

[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]

On 05/20/2014 08:40 AM, Ian Campbell wrote:
> On Thu, 2014-05-15 at 11:54 -0400, Zhigang Wang wrote:
>> On 05/15/2014 11:10 AM, Ian Campbell wrote:
>>> On Mon, 2014-05-12 at 20:10 -0400, Zhigang Wang wrote:
>>>> Is this expected? I thought it should be installed into
>>>> /usr/lib64 as all other xen libs.
>>> 
>>> I think it depends on how you configured the Xen build -- what
>>> options did you use?
>>> 
>>>> Attached patch will change the behavior. Apply it if you think
>>>> it's what we want.
>>> 
>>> I think it probably is but I'll wait for confirmation of the
>>> options you used.
>> 
>> I think the problem is simple as this:
>> 
>> For xen:
>> 
>> ./configure --prefix=/usr --libdir=/usr/lib64
>> 
>> For qemu: we didn't pass the --libdir when we configure it, so it
>> uses the default one: $PREFIX/lib
> 
> Thanks. I think your patch is probably the correct one then. Please
> can you submit with a proper changelog.
> 
>> I use RPM %configure macro, and it translates to:
>> 
>> + ./configure --build=x86_64-redhat-linux-gnu
>> --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu
>> --program-prefix= --prefix=/usr --exec-prefix=/usr
>> --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
>> --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64
>> --libexecdir=/usr/libexec --localstatedir=/var
>> --sharedstatedir=/var/lib --mandir=/usr/share/man
>> --infodir=/usr/share/info
>> 
>> There are many other options has the same issue: they may different
>> for qemu and xen. I'm not sure what is the best way to handle it.
> 
> I wonder if we should be arranging to pass the full set of configure 
> optons we received down to the subconfigure. That's how projects
> which have subtree configures do things (including our own toplevel,
> tools, docs, stubdom configure). My concern would be that this is a
> 3rd party configure so the scenario is slightly different. TBH I'm no
> autoconf expert so I don't know...
> 
> Ian.
> 

Attached is the patch with some changelog.

Before we can think out the right way to pass all options, I think passing
prefix and libdir is good enough for now:

1. prefix is most widely used.
2. libdir becomes important as x86 and x86_64 get into the same system.
3. Default values for other options seems the same across build systems.

Thanks,

Zhigang

[-- Attachment #2: ovs-xen-qemu-upstream-libdir.patch --]
[-- Type: text/x-patch, Size: 773 bytes --]

tools: pass --libdir to qemu configure

On an x86_64 environment, when we configure xen using:

  ./configure --prefix=/usr --libdir=/usr/lib64
  
only --prefix=/usr is passed to qemu configure. Then qemu will use
$(PREFIX)/lib as libdir, which causes inconsistent with other xen tools.

Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com>
diff --git a/tools/Makefile b/tools/Makefile
index 3675515..93c79e7 100644
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -188,6 +188,7 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
 	$$source/configure --enable-xen --target-list=i386-softmmu \
 		$(QEMU_XEN_ENABLE_DEBUG) \
 		--prefix=$(PREFIX) \
+		--libdir=$(LIBDIR) \
 		--source-path=$$source \
 		--extra-cflags="-I$(XEN_ROOT)/tools/include \
 		-I$(XEN_ROOT)/tools/libxc \

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-05-20 13:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13  0:10 libcacard is been installed to /usr/lib while libdir=/usr/lib64 Zhigang Wang
2014-05-15 15:10 ` Ian Campbell
2014-05-15 15:54   ` Zhigang Wang
2014-05-20 12:40     ` Ian Campbell
2014-05-20 13:00       ` Zhigang Wang [this message]
2014-05-20 13:05         ` Olaf Hering
2014-05-20 13:02       ` Olaf Hering
2014-05-20 13:07         ` Andrew Cooper
2014-05-20 13:21           ` Zhigang Wang
2014-05-20 16:55             ` Zhigang Wang
2014-05-21  7:46               ` Olaf Hering
2014-05-21 10:25                 ` Ian Campbell
2014-05-21 10:50                   ` Olaf Hering
2014-05-21 13:52                     ` Zhigang Wang
2014-05-21 14:16                       ` Ian Campbell
2014-05-28 16:13                         ` Zhigang Wang
2014-06-02 14:40                           ` Ian Campbell
2014-06-02 14:49                             ` 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=537B51D9.7070605@oracle.com \
    --to=zhigang.x.wang@oracle.com \
    --cc=Ian.Campbell@citrix.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).