On Sun, 14 Feb 2021 at 10:56, Andreas Tille wrote:
> Since it would to "experimental" to me I have not choosen this option
> since I wanted to be quick. The fact that my upload had successfully
> built on i386 meanwhile makes me optimistic, that we can ask for a
> migration to testing hint.
I do
On Fri, Feb 12, 2021 at 04:56:20PM -0500, Aaron M. Ucko wrote:
> > fail to see why exactly i386 is failing. Is this possibly an effect of
> > bug #917851?
>
> Probably not; dropping the bug to a Bcc. Experimentation in an i386
> chroot reveals the problem to be specifically with yara_mapper, whi
Hi Aaron,
On Fri, Feb 12, 2021 at 04:56:20PM -0500, Aaron M. Ucko wrote:
> Andreas Tille writes:
>
> > But other 32bit architectures like armel and armhf are passing[2]. So I
> > fail to see why exactly i386 is failing. Is this possibly an effect of
> > bug #917851?
>
> Probably not; dropping
Andreas Tille writes:
> But other 32bit architectures like armel and armhf are passing[2]. So I
> fail to see why exactly i386 is failing. Is this possibly an effect of
> bug #917851?
Probably not; dropping the bug to a Bcc. Experimentation in an i386
chroot reveals the problem to be specific
On Fri, Feb 12, 2021 at 04:30:48PM +0500, Andrey Rahmatullin wrote:
> On Fri, Feb 12, 2021 at 11:21:38AM +0100, Hilmar Preuße wrote:
> > > But other 32bit architectures like armel and armhf are passing[2]. So I
> > > fail to see why exactly i386 is failing. Is this possibly an effect of
> > > bug
On Fri, Feb 12, 2021 at 11:21:38AM +0100, Hilmar Preuße wrote:
> > > You can't adjust anything to get more than 4GB virtual memory on 32-bit
> > > architectures.
> > > You can try adjusting compilation/linking parameters to make the
> > > compiler/linker use less memory though (not sure if the sugg
Hi Hilmar,
On Fri, Feb 12, 2021 at 11:21:38AM +0100, Hilmar Preuße wrote:
> > But other 32bit architectures like armel and armhf are passing[2]. So I
> > fail to see why exactly i386 is failing. Is this possibly an effect of
> > bug #917851?
> >
> Maybe the memory of the whole builder is exhaus
Am 12.02.2021 um 11:01 teilte Andreas Tille mit:
On Fri, Feb 12, 2021 at 02:39:25PM +0500, Andrey Rahmatullin wrote:
Hi,
You can't adjust anything to get more than 4GB virtual memory on 32-bit
architectures.
You can try adjusting compilation/linking parameters to make the
compiler/linker use
Hi,
On Fri, Feb 12, 2021 at 02:39:25PM +0500, Andrey Rahmatullin wrote:
> > I wonder whether this could be simply solved by adjusting the hardware /
> > emulation parameters of the according autobuilder.
> >
> > Am I missing something?
> You can't adjust anything to get more than 4GB virtual memo
On Fri, Feb 12, 2021 at 10:17:06AM +0100, Andreas Tille wrote:
> in the build log[1] I found
>
>virtual memory exhausted: Operation not permitted
>
> I wonder whether this could be simply solved by adjusting the hardware /
> emulation parameters of the according autobuilder.
>
> Am I missing
Hi,
in the build log[1] I found
virtual memory exhausted: Operation not permitted
I wonder whether this could be simply solved by adjusting the hardware /
emulation parameters of the according autobuilder.
Am I missing something?
Kind regards
Andreas.
[1]
https://buildd.debian.org/
11 matches
Mail list logo