All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Wilson <msw@amazon.com>
To: "cyberhawk001@gmail.com" <cyberhawk001@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: fsimage - no such file
Date: Sat, 23 Jun 2012 13:56:01 -0700	[thread overview]
Message-ID: <20120623205601.GG2640@US-SEA-R8XVZTX> (raw)
In-Reply-To: <4FE62585.10600@gmail.com>

On Sat, Jun 23, 2012 at 01:22:29PM -0700, cyberhawk001@gmail.com wrote:
> >> On Tue, Jun 19, 2012 at 04:19:27AM -0700, Mohammad Hedayati wrote:
> >>>> # Node ID 6eabee6807b48c72bcc35a28170f0729500def85
> >>>> # Parent  80c0677f0f8370a4542aab81ab93380b0dab25db
> >>>> imported patch debian-lib-dir.patch
> >>>>
> >>>> diff -r 80c0677f0f83 -r 6eabee6807b4 config/StdGNU.mk
> >>>> --- a/config/StdGNU.mk  Wed Jun 13 09:27:53 2012 +0100
> >>>> +++ b/config/StdGNU.mk  Wed Jun 13 09:27:53 2012 +0100
> >>>> @@ -34,7 +34,7 @@ BINDIR = $(PREFIX)/bin
> >>>>   INCLUDEDIR = $(PREFIX)/include
> >>>>   LIBLEAFDIR = lib
> >>>>   LIBLEAFDIR_x86_32 = lib
> >>>> -LIBLEAFDIR_x86_64 ?= lib64
> >>>> +LIBLEAFDIR_x86_64 ?= lib
> >>>>   LIBDIR = $(PREFIX)/$(LIBLEAFDIR)
> >>>>   LIBDIR_x86_32 = $(PREFIX)/$(LIBLEAFDIR_x86_32)
> >>>>   LIBDIR_x86_64 = $(PREFIX)/$(LIBLEAFDIR_x86_64)
> >>>>
> 
> SOOO, just wondering, in the above patch, should these:
> 
> -LIBLEAFDIR_x86_64 ?= lib64
> +LIBLEAFDIR_x86_64 ?= lib
> 
> 
> be also changed if installing the latest Xen 4.2-unstable on like Debian 
> Wheezy? OR is this something that is not important that important?

Ultimately the LIBLEAFDIR bits should go away entirely. The person
building Xen should specify where libraries live at ./configure time
with, for example, --libdir=/usr/lib64 (for 64-bit OSs like Fedora,
RHEL, OpenSUSE and SLES) or --libdir=/usr/lib/x86_64-linux-gnu (for
64-bit systems like Ubuntu 12.04). More specifically, on Debian based
multiarch platforms, you'd use:
 ./configure --libdir=/usr/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH)

> Just curious since even in the latest Xen 4.2-unstable rev-25494, it 
> still has the
> 
> LIBLEAFDIR_x86_32 = lib
> LIBLEAFDIR_x86_64 ?= lib64
> 
> 
> in the StdGNU.mk file.

Right, nothing has been committed while I've been working through the
feedback on the patch. I'll post v3 in just a moment which hopefully
has addressed all concerns.

Matt

  reply	other threads:[~2012-06-23 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 22:24 fsimage - no such file Mohammad Hedayati
2012-06-19  8:35 ` Thanos Makatos
2012-06-19 10:57   ` Ian Campbell
2012-06-19 11:19     ` Mohammad Hedayati
2012-06-19 16:10       ` Matt Wilson
2012-06-19 16:36         ` Ian Campbell
2012-06-23 20:22           ` cyberhawk001
2012-06-23 20:56             ` Matt Wilson [this message]
2012-06-19 15:58     ` Matt Wilson
2012-06-19 16:13       ` Ian Campbell
2012-06-19 16: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=20120623205601.GG2640@US-SEA-R8XVZTX \
    --to=msw@amazon.com \
    --cc=cyberhawk001@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.