From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote Date: Thu, 31 Jul 2008 16:29:15 +0100 Message-ID: <20080731152915.GR4678@implementation.uk.xensource.com> References: <18577.55125.163478.822929@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <18577.55125.163478.822929@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: Aron Griffis , xen-devel@lists.xensource.com, xen-ia64-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ian Jackson, le Thu 31 Jul 2008 16:16:37 +0100, a =E9crit : > Aron Griffis writes ("[Xen-devel] [PATCH 2 of 2] cross-build fixes in i= oemu-remote"): > > - Don't call install -s; it uses the host strip program which > > doesn't understand cross-built binaries. This same change was > > in the legacy ioemu dir. >=20 > I think this should be fixed by the build environment, or possibly > $(INSTALL), being arranged to not have this bug. If $(INSTALL) -s > doesn't work then this should be fixed. Options include putting a > symlink to /bin/true on the path somewhere under the name `strip', or > overriding INSTALL somehow to a more clever program. I have the same issue when cross-compiling some other projects. I wonder how install would be able to know which strip command it should use. Samuel