From: "Christoph Böhmwalder" <christoph@boehmwalder.at>
To: tuxic@posteo.de,Gentoo <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Need help to compile a minimal wine
Date: Sat, 23 Sep 2017 20:33:49 +0200 [thread overview]
Message-ID: <D0C2FBDF-C428-4339-BD56-9154CA6CDED1@boehmwalder.at> (raw)
In-Reply-To: <20170923182145.obtuqoti3txp36l4@solfire>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Hi Meino,
I haven't tried this, but may I ask why you're not using the ATmel AVR Toolchain [0] that's readily available for Linux?
[0] http://www.atmel.com/tools/atmelavrtoolchainforlinux.aspx
--
Regards,
Christoph
Am 23. September 2017 20:21:45 MESZ schrieb tuxic@posteo.de:
>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:
>
>avrasm2.exe: PE32 executable (console) Intel 80386, for MS Windows
>
>Most GENTOO related tutorials on how to compile/install wine were
>made for those of us who want to use wine as kind a "bootloader" for
>games (NO pune intended!).
>
>I tried to compile wine ... but all end with an compilation error.
>
>To save time and hassle:
>Is there any wine version out there, which is currentlu compilable
>and/or recommended?
>
>Is there any tutorial which covers my intended use case for wine?
>
>(My system is not multilib.)
>
>Thanks a lot for any help in advance!
>Cheers
>Meino
[-- Attachment #2: Type: text/html, Size: 1620 bytes --]
next prev parent reply other threads:[~2017-09-23 18:34 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 [this message]
2017-09-23 18:39 ` R0b0t1
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=D0C2FBDF-C428-4339-BD56-9154CA6CDED1@boehmwalder.at \
--to=christoph@boehmwalder.at \
--cc=gentoo-user@lists.gentoo.org \
--cc=tuxic@posteo.de \
/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