From: Ian Campbell <ian.campbell@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
xen-devel@lists.xenproject.org
Cc: wei.liu2@citrix.com
Subject: Re: [PATCH] Add Libc multiarch package as build prerequisites on 64-bit platforms to the README
Date: Wed, 7 Oct 2015 14:26:44 +0100 [thread overview]
Message-ID: <1444224404.1410.39.camel@citrix.com> (raw)
In-Reply-To: <1444150705-555-1-git-send-email-linux@eikelenboom.it>
On Tue, 2015-10-06 at 18:58 +0200, Sander Eikelenboom wrote:
> When building on 64-bit platforms this prevents build errors for
> 32-bit components which are enabled on a default build.
>
> Signed-off-by: Sander Eikelenboom <linux@eikelenboom.it>
> ---
> README | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/README b/README
> index a7d0033..1324c7c 100644
> --- a/README
> +++ b/README
> @@ -56,6 +56,9 @@ provided by your OS distributor:
> * GNU gettext
> * 16-bit x86 assembler, loader and compiler (dev86 rpm or bin86 &
> bcc debs)
> * ACPI ASL compiler (iasl)
> + * Libc multiarch package (e.g. libc6-dev-i386 / glibc-devel.i686).
BTW, to be completely pedantic these are "biarch" packages.
Under Debian the "multiarch" package would be libc6-dev:i386 and you would
need to have run "dpkg --add-architecture=i386" at some point.
libc6-dev:i386 is the actual dev package from the i386 repository as
opposed to a special libc6-dev-i386 in the amd64 repository.
I don't believe the RPM world has anything equivalent to multiarch.
I'm not proposing we change anything though and I think libc6-dev-i386 is
the right thing to be recommending for the time being.
Ian.
prev parent reply other threads:[~2015-10-07 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 16:58 [PATCH] Add Libc multiarch package as build prerequisites on 64-bit platforms to the README Sander Eikelenboom
2015-10-07 10:16 ` Wei Liu
2015-10-07 11:52 ` Ian Campbell
2015-10-07 13:06 ` Sander Eikelenboom
2015-10-07 13:10 ` Wei Liu
2015-10-07 13:26 ` Ian Campbell [this message]
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=1444224404.1410.39.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=linux@eikelenboom.it \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).