On 2021-04-22 21:23, Sam James wrote:
Such pkg_setups are best avoided if possible because they can be
confusing and we have other tools to handle it, so I’m glad you asked!
I’d provide a USE flag for this tool and mask it on non-multilib amd64
profiles (or mask everywhere and unmask on the
Ah, looks like attachment isn't attached, post my ebuild in plain text.
EAPI=7
inherit multilib toolchain-funcs
DESCRIPTION="Open source assembly language compiler"
HOMEPAGE="https://flatassembler.net;
SRC_URI="https://flatassembler.net/${P}.tgz;
LICENSE="MIT"
SLOT="0"
KEYWORDS="amd64 x86"
> On 22 Apr 2021, at 22:07, Nekun wrote:
>
> Hi all,
>
Hi!
> Working on the fasm ebuild, have some questions:
>
> 1. fasm is written on itself and has two variants: self-contained binary for
> x86 and amd64 and linked with libc only for x86. Also, there are tools for
> working with the
Hi all,
Working on the fasm ebuild, have some questions:
1. fasm is written on itself and has two variants: self-contained binary
for x86 and amd64 and linked with libc only for x86. Also, there are
tools for working with the proprietary symbolic information format which
is libc-linked and
