all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add Wine.
Date: Mon, 17 Nov 2014 14:30:10 +0100	[thread overview]
Message-ID: <871tp20xb1.fsf@gnu.org> (raw)
In-Reply-To: <87d28mc8fi.fsf@gmail.com> ("宋文武"'s message of "Mon, 17 Nov 2014 20:34:25 +0800")

宋文武 <iyzsong@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> 宋文武 <iyzsong@gmail.com> skribis:
>>
>>> I can't get tests working, so leave them disabled.
>>
>> It’s OK to do that so we can move forward, but please leave a comment
>> that explains the situation, above #:tests? #f.  The goal remains to
>> have tests running, eventually.
> By run it manually, it seem to me that many tests of wine are known to failed.

OK, well leave this as a comment.

>>> +    (arguments
>>> +     `(#:system "i686-linux"
>>
>> No, that’s not possible.  :-)
>> People should be able to use Wine regardless of their platform.
>>
>> What is the reason behind it?
> The goal is to have 32bit version wine for x86_64-linux.
> IMO, it's what most people want: to run 32bit windows applications.
>
> Yeah, for pure 64bit system `x86_64-linux', we can add wine64, which can run
> 64bit windows applications.

But can’t the 64-bit Wine run 32-bit Windows applications?  Is there any
loss of functionality by building it as x86_64 code?

> I have not try `mips64el-linux', but it sound mostly not working to me.

Yeah it probably doesn’t make much sense.

>> If some platforms are inherently not supported by Wine, then please add
>> a ‘supported-platforms’ field (there are examples in other files.)
> By set #:system to `i686-linux', I assunme it's same as:
>   `(supported-systems '("i686-linux" "x86_64-linux"))'

It’s not the same.  ‘supported-systems’ is required if we assume that
Wine only runs on Intel.  #:system is only needed if there’s a strong
reason to force i686 builds.

Thanks,
Ludo’.

  reply	other threads:[~2014-11-17 13:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15 14:41 [PATCH] gnu: Add Wine 宋文武
2014-11-15 14:45 ` John Darrington
2014-11-15 15:05   ` Bruno Félix Rezende Ribeiro
2014-11-15 15:48     ` John Darrington
2014-11-15 16:47       ` Bruno Félix Rezende Ribeiro
2014-11-15 17:01         ` John Darrington
2014-11-15 15:10   ` 宋文武
2014-11-15 15:02 ` 宋文武
2014-11-15 18:15   ` Ludovic Courtès
2014-11-15 16:39 ` 宋文武
2014-11-15 18:21 ` Ludovic Courtès
2014-11-16  3:00   ` 宋文武
2014-11-16 17:27     ` Ludovic Courtès
2014-11-17 12:34       ` 宋文武
2014-11-17 13:30         ` Ludovic Courtès [this message]
2014-11-18 21:32     ` Ludovic Courtès
2014-11-19 11:38       ` 宋文武

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=871tp20xb1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.