From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: James <wireless@tampabay.rr.com>
Subject: Re: [gentoo-user] Re: Gentoo Live 11.0
Date: Thu, 17 Mar 2011 09:24:28 -0700 [thread overview]
Message-ID: <AANLkTi=bm9YiVNyi7D0OaHfyei4CmKA6y0BXTUemfdst@mail.gmail.com> (raw)
In-Reply-To: <loom.20110317T170122-495@post.gmane.org>
On Thu, Mar 17, 2011 at 9:05 AM, James <wireless@tampabay.rr.com> wrote:
> Walter Dnes <waltdnes <at> waltdnes.org> writes:
>
>
>> WINE, which runs some Windows apps, will not build on a 64-bit system
>> without multilib support. I found that out "the hard way" after
>> installing pure 64-bit on my machine. Rather than wipe+reinstall, I
>> ended up installing a 32-bit Gentoo guest under qemu-kvm, and installed
>> WINE on that.
>
>
> Walter,
> You have confused me. First you indicate that multilib is
> needed for WINE. Then you indicate that you had to use the
> 32 bit mixed mode (no multilib).... under qemu-kvm, and
> and then install WINE under the 32 bit qemu.
>
> So if you were installing a system, just to run wine, would it
> be multilib or hybrid (64 and 32 bit) ?
>
>
> James
James,
1) Wine is 32-bit
2) Walter had a 64-bit only system
3) Walter had 2 choices:
a) Wipe the system and start over making it a multi-lib system
b) Create a 32-bit chroot
He chose b).
It's not possible to 'install a system to ONLY run Wine', but if you
want to run Windows apps you have 3 choices:
1) Install 32-bit Gentoo on your 64-bit hardware. Not very interesting to me.
2) Install 64-bit Gentoo with multi-lib support. This is what I do,
although I don't run Wine anymore as I use Vbox & VMware.
3) Install 64-bit Gentoo without multi-lib support and run which in a
32-bit chroot. Double the Gentoo maintenance because you are now
required to keep both the 32-bit & 64-bit installs up-to-date.
Hope this help.
next prev parent reply other threads:[~2011-03-17 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 16:19 [gentoo-user] Gentoo Live 11.0 James
2011-03-14 16:30 ` Mark Knecht
2011-03-15 14:55 ` [gentoo-user] " James
2011-03-15 15:22 ` Mark Knecht
2011-03-15 15:40 ` Neil Bothwick
2011-03-15 23:52 ` James
2011-03-16 23:36 ` Walter Dnes
2011-03-17 16:05 ` James
2011-03-17 16:24 ` Mark Knecht [this message]
2011-03-17 16:37 ` Neil Bothwick
2011-03-17 16:51 ` Mark Knecht
2011-03-17 17:59 ` James
2011-03-17 18:41 ` Mark Knecht
2011-03-17 20:36 ` Bill Longman
2011-03-17 18:42 ` Neil Bothwick
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='AANLkTi=bm9YiVNyi7D0OaHfyei4CmKA6y0BXTUemfdst@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=wireless@tampabay.rr.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox