From: Christoph Egger <Christoph.Egger@amd.com>
To: Matt Wilson <msw@amazon.com>
Cc: Olaf Hering <olaf@aepfle.de>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: LIBDIR not set during xen build
Date: Thu, 12 Jul 2012 10:36:18 +0200 [thread overview]
Message-ID: <4FFE8C82.4070605@amd.com> (raw)
In-Reply-To: <20120711163614.GA5064@US-SEA-R8XVZTX>
On 07/11/12 18:36, Matt Wilson wrote:
> On Wed, Jul 11, 2012 at 01:26:07AM -0700, Olaf Hering wrote:
>>
>> How is LIBDIR in xen/Makefile supposed to be set? During 'make xen' all
>> the fine efi stuff is installed in /efi instead of /usr/lib64/efi.
>> And: is /usr/lib64/efi the correct place anyway?
>
> Are you noticing new broken behavior? Ian C. recently committed a
> change I made to honor ./configure --libdir=... for tools targets [1],
> but that shouldn't have affected the xen subtree.
>
> I've not been building with a compiler that supports __ms_abi__, so
> I've never noticed this.
Does this patch help:
http://lists.xen.org/archives/html/xen-devel/2012-07/msg00511.html
Christoph
> Matt
>
> [1] http://xenbits.xen.org/hg/xen-unstable.hg/rev/ad08cd8e7097
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2012-07-12 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 8:26 LIBDIR not set during xen build Olaf Hering
2012-07-11 16:36 ` Matt Wilson
2012-07-11 16:51 ` Olaf Hering
2012-07-11 17:44 ` Matt Wilson
2012-07-12 8:36 ` Christoph Egger [this message]
2012-07-12 8:46 ` Olaf Hering
2012-07-12 9:05 ` David Vrabel
2012-07-12 15:56 ` 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=4FFE8C82.4070605@amd.com \
--to=christoph.egger@amd.com \
--cc=msw@amazon.com \
--cc=olaf@aepfle.de \
--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.