Michael Tokarev writes:
> 06.02.2019 13:58, Alex Bennée wrote:
> []
>>> What should the dependencies look like?
As per:
From: Helmut Grohne
Subject: Re: [PATCH] binutils: enable s390x/ppc64el on arm64 hosts
Message-ID: <20190213051906.ga24...@alf.mars>
The workaround is to use:
Hi,
The following bug has come up and we would like some input from the
multiarch and cross developers on how best to handle this case.
In an ideal world all cross compilers would be available on all release
architectures but I think it will be a while before we get there. My own
efforts to
06.02.2019 13:58, Alex Bennée wrote:
[]
What should the dependencies look like?
I'm not sure - it does seem weird that we are treating what is in effect
an s390x architecture blob as architecture independent. I guess QEMU is
good at generating weird exception cases.
Actually _all_ firmware
Michael Tokarev writes:
> Control: reassign -1 src:qemu
> Control: tag -1 + moreinfo
>
> 05.02.2019 22:12, Alex Bennée wrote:
>> Package: qemu-system-common
>> Version: 1:3.1+dfsg-2+b1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> This is a problem when running:
>>
>>apt build-dep qemu
Control: reassign -1 src:qemu
Control: tag -1 + moreinfo
05.02.2019 22:12, Alex Bennée wrote:
Package: qemu-system-common
Version: 1:3.1+dfsg-2+b1
Severity: normal
Dear Maintainer,
This is a problem when running:
apt build-dep qemu
On a arm64 host. I also ran into other failures while
Package: qemu-system-common
Version: 1:3.1+dfsg-2+b1
Severity: normal
Dear Maintainer,
This is a problem when running:
apt build-dep qemu
On a arm64 host. I also ran into other failures while trying:
apt build-dep -a arm64 qemu
On a multiarch setup. The root reason is that the s390 cross
6 matches
Mail list logo
