From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Need help to compile a minimal wine
Date: Sat, 23 Sep 2017 13:39:48 -0500 [thread overview]
Message-ID: <CAAD4mYh1qze75XU7cNFMgabpmEuE51QVaL2VMLbOfkYtx7tCsw@mail.gmail.com> (raw)
In-Reply-To: <20170923182145.obtuqoti3txp36l4@solfire>
On Sat, Sep 23, 2017 at 1:21 PM, <tuxic@posteo.de> wrote:
> Hi,
>
> I want to compile wine to execute a single commandline tool.
> That's it.
>
> The commandline tool is the AVR-assembler made by ATmel to recompile
> a FORTH interpreter for the AVR-line of microcontrollers of
> ATMEL/Micorchip:
>
Are you sure you need the assembler as released by Atmel? Most of
their development work seems to have gone to AVR-GCC. Is the syntax of
avrasm2 unique and are there any features that are not implemented in
GNU as?
> avrasm2.exe: PE32 executable (console) Intel 80386, for MS Windows
>
> [...]
>
> (My system is not multilib.)
>
As "WINE is Not an Emulator" it seems to me like you will either need
to reinstall as a multilib system, or set up an x86 chroot or
container to run the assembler.
There is a small possibility that WINE's WOW64 support (the thing that
runs Win32 executables on Win64) does not require multilib, but if so
then they would have needed to reimplement large parts of multilib and
certain kernel facilities. It does not seem likely that they would
have done this.
Looking at https://wiki.winehq.org/Building_Wine#Shared_WoW64 it seems
like there is an implicit dependency on a multlib system. Most Linux
distributions are multilib, likely because it is necessary to support
many closed source Linux programs.
Cheers,
R0b0t1
next prev parent reply other threads:[~2017-09-23 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 18:21 [gentoo-user] Need help to compile a minimal wine tuxic
2017-09-23 18:33 ` Christoph Böhmwalder
2017-09-23 18:39 ` R0b0t1 [this message]
2017-09-25 5:22 ` tuxic
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=CAAD4mYh1qze75XU7cNFMgabpmEuE51QVaL2VMLbOfkYtx7tCsw@mail.gmail.com \
--to=r030t1@gmail.com \
--cc=gentoo-user@lists.gentoo.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