[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
re: port-i386/53881: Error building spidermonkey52 from pkgsrc
The following reply was made to PR port-i386/53881; it has been noted by GNATS.
From: Marcus Esdohr <esdohr%marcusesdohr.de@localhost>
Subject: re: port-i386/53881: Error building spidermonkey52 from pkgsrc
Date: Wed, 16 Jan 2019 14:28:03 +0100
I will try the PAE.
My problem is that I run NetBSD on an much older machine which take days
to compile anything like llvm. So I set up a NetBSD in a virtualbox on a
machine with much more power just to build some programs and use them on
the old one.
Am 2019-01-16 11:35, schrieb matthew green:
> The following reply was made to PR port-i386/53881; it has been noted
> by GNATS.
> From: matthew green <mrg%eterna.com.au@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc: port-i386-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
> netbsd-bugs%netbsd.org@localhost, esdohr%marcusesdohr.de@localhost
> Subject: re: port-i386/53881: Error building spidermonkey52 from pkgsrc
> Date: Wed, 16 Jan 2019 21:30:05 +1100
> > The branch of pkgsrc is current. The kernel and the rest of the
> > is a standard 8.0 freshly installed and without any modifications.
> so you probably only have 3.5GB of ram available.
> you could upgrade to amd64 or try the GENERIC_PAE kernel instead,
> which supports upto 64GB of ram on i386 port.
> does 'dmesg' have anything interesting? i'm going to disagree
> with martin here and say that SIGSEGV indicates compiler bug or
> bad ram, but SIGKILL (not seen here) indicates out of ram, and
> it seems unlikely that 3.5GB + 7GB swap would be a problem.
Main Index |
Thread Index |