From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matt Wilson <msw@amazon.com>
Subject: Re: fsimage - no such file
Date: Sat, 23 Jun 2012 13:56:01 -0700
Message-ID: <20120623205601.GG2640@US-SEA-R8XVZTX>
References: <CABA5EEuVTVOHSPD6j1TvHivL8wtmS=NudAL=5wcQOm99qPPvBw@mail.gmail.com>
	<4B45B535F7F6BE4CB1C044ED5115CDDEED66156583@LONPMAILBOX01.citrite.net>
	<1340103453.24176.7.camel@zakaz.uk.xensource.com>
	<CABA5EEtD32O+M2yA=WiHuGvBv0oF=VRd7WnisvpnHuau40Qj3Q@mail.gmail.com>
	<20120619161039.GB4296@US-SEA-R8XVZTX>
	<1340123764.24176.50.camel@zakaz.uk.xensource.com>
	<4FE62585.10600@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <4FE62585.10600@gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "cyberhawk001@gmail.com" <cyberhawk001@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

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