Updating src tree:
P src/common/lib/libc/arch/arm/features.c
P src/crypto/external/bsd/openssl/dist/crypto/arm_arch.h
P src/crypto/external/bsd/openssl.old/dist/crypto/arm_arch.h
P src/distrib/sparc/miniroot/Makefile.inc
P src/doc/TODO.clang
P src/etc/mtree/NetBSD.dist.base
P
On Fri, 2 Aug 2019, Manuel Bouyer wrote:
On Fri, Aug 02, 2019 at 07:44:05AM -0700, Hisashi T Fujinaka wrote:
[...]
Nothing in the logs, no core files, nothing in the console. Just a
reboot.
Ooh, wait, I got one this time.
[ 1055.9565284] panic: pr_find_pagehead: [npfcn4pl] item 0xc25db2dc
On Fri, 2 Aug 2019, Robert Swindells wrote:
> I would argue that this is a pkgsrc issue, mail/spamd should use
> different pathnames from the older version that was in base.
Seems like the right answer for this case.
> >The "fontconfig"-related files/links ARE part of the base system build.
>
"John D. Baker" wrote:
>On Fri, 2 Aug 2019, Robert Swindells wrote:
>
>> > /var/chroot/spamd
>>
>
>> If you have local changes to your source tree then the files under
>> src/distrib/sets/lists need to match that.
>>
>> If the two files that are being removed are from outside your NetBSD
>>
On Fri, Aug 02, 2019 at 07:44:05AM -0700, Hisashi T Fujinaka wrote:
> [...]
> Nothing in the logs, no core files, nothing in the console. Just a
> reboot.
>
> Ooh, wait, I got one this time.
>
> [ 1055.9565284] panic: pr_find_pagehead: [npfcn4pl] item 0xc25db2dc poolid
> 173 != 172
This one is
On Fri, 2 Aug 2019, Michael van Elst wrote:
ht...@twofifty.com (Hisashi T Fujinaka) writes:
Oh, duh, I think I remember that the real issue is that you can't run as
many $JOBS. Before it would be better about throttling things.
Nothing is ever throttled :)
Can you be a bit more verbose
On Fri, 2 Aug 2019, Robert Swindells wrote:
> > /var/chroot/spamd
>
> If you have local changes to your source tree then the files under
> src/distrib/sets/lists need to match that.
>
> If the two files that are being removed are from outside your NetBSD
> source tree then it might be worth
"John D. Baker" wrote:
>Recent-ish updates to 'postinstall' now cause more grief with local
>configuration than before.
>
>Specifially, in the past the "obsolete" check would declare
>
> /var/chroot/spamd
Things get declared as obsolete when they are removed from the build,
the examples you
"John D. Baker" writes:
> Recent-ish updates to 'postinstall' now cause more grief with local
> configuration than before.
>
> Specifially, in the past the "obsolete" check would declare
>
> /var/chroot/spamd
>
> obsolete and remove it if re-run with the "fix obsolete" command. This
> is
Recent-ish updates to 'postinstall' now cause more grief with local
configuration than before.
Specifially, in the past the "obsolete" check would declare
/var/chroot/spamd
obsolete and remove it if re-run with the "fix obsolete" command. This
is normally only a problem the first time a
ht...@twofifty.com (Hisashi T Fujinaka) writes:
>Oh, duh, I think I remember that the real issue is that you can't run as
>many $JOBS. Before it would be better about throttling things.
Nothing is ever throttled :)
Can you be a bit more verbose about what "crashes" means?
panic ?
uvm fault ?
ht...@twofifty.com (Hisashi T Fujinaka) writes:
>Wow. So far, it's been a disaster for me. I remember saying the memory
>management seemed iffy but being told to get a real machine with more
>memory. My i386 machine w/1G of RAM and ~4G of swap kept crashing while
>trying to compile things in
Lately, perhaps the last 4-5 Firefox and rust builds, I have never had a
single failure. Also I haven’t seen yet a llvm build failure on this
machine.
It’s a 20gb laptop, but I always use make_jobs 1. So perhaps it is indeed a
resource problem.
On Fri, 2 Aug 2019 at 09:31, Chavdar Ivanov
I used to get this a lot weeks or months ago
On Fri, 2 Aug 2019 at 09:07, Martin Husemann wrote:
> On Thu, Aug 01, 2019 at 04:27:29PM -0700, Hisashi T Fujinaka wrote:
> > Oh, duh, I think I remember that the real issue is that you can't run as
> > many $JOBS. Before it would be better about
On Thu, Aug 01, 2019 at 04:27:29PM -0700, Hisashi T Fujinaka wrote:
> Oh, duh, I think I remember that the real issue is that you can't run as
> many $JOBS. Before it would be better about throttling things.
If you have a concrete example (like: on netbsd-8 I can build rust with
MAKE_JOBS=12 on
15 matches
Mail list logo
