Updating src tree:
P src/external/cddl/osnet/dev/cyclic/cyclic.c
P src/sys/arch/amd64/amd64/cpufunc.S
P src/sys/arch/arm/acpi/acpipchb.c
P src/sys/arch/x86/include/cpu_counter.h
P src/sys/arch/x86/x86/cpu.c
P src/sys/arch/x86/x86/tsc.c
P src/sys/arch/x86/x86/x86_softintr.c
P
On Fri, May 08, 2020 at 08:54:32AM -0400, Greg Troxel wrote:
> Why do you need to know? It will almost certainly be less than a day.
> Is that going to cause you do try netbsd, or not try netbsd?
As others have said, it highly depends on your hard disk and amount of
ram installed. Our build
Thank you for pointing that out. I am updating now.
I downloaded the NetBSD-9.99.60-amd64-install.img (date stamped May 07,
2020) this morning and installed on my Lenovo X200. I did select the
option to download pkgsrc. I changed the path from stable to current and
that is what was pulled
On 08.05.2020 16:44, Ron Georgia wrote:
Installed current NetBSD 9.99.60 (GENERIC) #0 and pkgsrc current on
05/08/2020 at about 0900 EST. I tried to build dbus but got an error
when it tried to build perl5.
sh: 1: Syntax error: Word "/d"p" unexpected (expecting ")")
That was a bug in
Installed current NetBSD 9.99.60 (GENERIC) #0 and pkgsrc current on
05/08/2020 at about 0900 EST. I tried to build dbus but got an error
when it tried to build perl5.
sh: 1: Syntax error: Word "/d"p" unexpected (expecting ")")
*** Error code 2
Stop.
make[1]: stopped in /usr/pkgsrc/lang/perl5
On Fri, May 08, 2020 at 02:55:10PM +0200, Frank Kardel wrote:
> I checked to same kernel in an instance with memory=2048 and it just works.
>
> Using todays kernel also works woth memory=2048.
>
> Using memory=65536 for the xen instance gives a surprising familiar
>
> TEST-A# modload bpfjit
> [
I checked to same kernel in an instance with memory=2048 and it just works.
Using todays kernel also works woth memory=2048.
Using memory=65536 for the xen instance gives a surprising familiar
TEST-A# modload bpfjit
[ 97.4727034] kobj_load, 444: [%M/bpfjit/bpfjit.kmod]: linker error:
out of
nottobay writes:
> I have a 5 year old a8 laptop. How can I figure out how long compiling the
> current source will take?
Actually compile it and report back.
Why do you need to know? It will almost certainly be less than a day.
Is that going to cause you do try netbsd, or not try netbsd?
On Fri, 8 May 2020, Benny Siegert wrote:
The short answer: It depends.
Slightly longer: Does the laptop have an SSD, an NVMe disk or a
spinning hard drive? Which build options do you choose -- for
instance, do you want to build X as well, do you want to build the
graphics acceleration stuff
The short answer: It depends.
Slightly longer: Does the laptop have an SSD, an NVMe disk or a
spinning hard drive? Which build options do you choose -- for
instance, do you want to build X as well, do you want to build the
graphics acceleration stuff (which requires building LLVM IIRC), etc.
pp.
I have a 5 year old a8 laptop. How can I figure out how long compiling the
current source will take?
On Thu, Apr 30, 2020 at 17:44 Constantine A. Murenin
wrote:
> On Sun, 26 Apr 2020 at 12:20, wrote:
>
>> On Sun, Apr 26, 2020 at 02:30:48PM +1000, Paul Ripke wrote:
>> > I switched away from cvsup a while back, but I now see that github
>> > NetBSD/src mirror is now 5 days old. Known issue?
>>
12 matches
Mail list logo
