From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] wine: more hostarch
Date: Sun, 22 Mar 2015 16:19:36 +0100 [thread overview]
Message-ID: <550EDD88.7010607@dawncrow.de> (raw)
In-Reply-To: <550DAB91.6080603@mind.be>
Am 21.03.2015 um 18:34 schrieb Arnout Vandecappelle:
> On 21/03/15 16:38, Andr? Hentschel wrote:
>> The tools from host-wine build on those architectures.
>>
>> Signed-off-by: Andr? Hentschel <nerv@dawncrow.de>
>
> Do you also volunteer to provide an autobuilder on arm and aarch64? :-)
if someone guides me to set one up I?ll do it for ARM on an cubox-i4pro, but i'm not sure about how many packages would support that.
would that be useful?
>> ---
>> package/wine/Config.in | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/package/wine/Config.in b/package/wine/Config.in
>> index 26de143..d1510e1 100644
>> --- a/package/wine/Config.in
>> +++ b/package/wine/Config.in
>> @@ -2,7 +2,9 @@ config BR2_PACKAGE_WINE
>> bool "wine"
>> depends on BR2_TOOLCHAIN_USES_GLIBC
>> # Wine only builds on certain architectures
>> - depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
>> + depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" || \
>> + BR2_HOSTARCH = "powerpc" || BR2_HOSTARCH = "arm" || \
>
> powerpc but not powerpc64?
yes, powerpc64 is not supported yet
> Regards,
> Arnout
>
>> + BR2_HOSTARCH = "aarch64"
>> # Wine has much CPU specific code and mostly makes sense on x86
>> depends on BR2_i386
>> help
>>
>
>
prev parent reply other threads:[~2015-03-22 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 15:38 [Buildroot] [PATCH 4/4] wine: more hostarch André Hentschel
2015-03-21 17:34 ` Arnout Vandecappelle
2015-03-22 15:19 ` André Hentschel [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=550EDD88.7010607@dawncrow.de \
--to=nerv@dawncrow.de \
--cc=buildroot@busybox.net \
/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