dashdruid writes:
> Hello List,
>
> I keep getting this error whatever I try to build from pkgsrc on NetBSD9.1
> i386.
>
> Even if I follow the basic tutorial with figlet:
>
> https://wiki.netbsd.org/pkgsrc/how_to_use_pkgsrc/
>
> It's the same error for all packages.
what's the actual error?
> I
rhia...@falu.nl (Rhialto) writes:
>Indeed, there I misinterpreted the size of my 1G disk, and put sd0b
>waaay out of bounds. I tried again, with partition b in cyl 1-63 and a
>in 64-1023. I could not start b at 0; in that case the dd command
>claimed it was read-only.
The disklabel sector of a di
On Sat 10 Jul 2021 at 15:39:10 +0200, Rhialto wrote:
> How far did you get? I tried sun3, and I got to booting the ramdisk
> kernel from tape. But when I did the "dd bs=32k if=/dev/nrst0
> of=/dev/rsd0b" I got a core dump. Possibly I had not used edlabel
> correctly due to it not getting a geometry
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.07.10.13.22.01 martin src/tests/lib/libc/stdio/t_fmemopen.c,v 1.6
Logs can be found at:
http://releng.NetBSD.org/b5reports/i386/commits-2021.07.h
I have security.pax.mprotect.enabled=0 in the sysctl.conf of this
(VirtualBox guest) machine.
On Sat, 10 Jul 2021 at 16:02, Chavdar Ivanov wrote:
>
> On Sat, 10 Jul 2021 at 15:14, Rhialto wrote:
> >
> > On Sat 10 Jul 2021 at 16:05:31 +0200, Rhialto wrote:
> > > I also didn't succeed in powering
On Sat, 10 Jul 2021 at 15:14, Rhialto wrote:
>
> On Sat 10 Jul 2021 at 16:05:31 +0200, Rhialto wrote:
> > I also didn't succeed in powering up the sun4c. When I gave the command
> > "command board0 power up", nothing appeared to happen. The tmesh window
> > remained gray, I did not get the tmesh>
On Sat 10 Jul 2021 at 16:05:31 +0200, Rhialto wrote:
> I also didn't succeed in powering up the sun4c. When I gave the command
> "command board0 power up", nothing appeared to happen. The tmesh window
> remained gray, I did not get the tmesh> prompt back. (That happens for
> sun3).
In fact, any co
On Sat 10 Jul 2021 at 15:53:44 +0200, Martin Husemann wrote:
> But then (looking at the libs it actually uses) this is kinda unlikely,
> besides issues caused by the different compiler.
>
> I'd expect the set exact dependcies install would be more of an issue.
> I used pkgsrc-current from around t
On Sat, Jul 10, 2021 at 03:48:35PM +0200, Martin Husemann wrote:
> On Sat, Jul 10, 2021 at 03:46:46PM +0200, Rhialto wrote:
> > On Sat 10 Jul 2021 at 15:41:27 +0200, Martin Husemann wrote:
> > > On Sat, Jul 10, 2021 at 03:39:10PM +0200, Rhialto wrote:
> > > > How far did you get? I tried sun3, and
On Sat, Jul 10, 2021 at 03:46:46PM +0200, Rhialto wrote:
> On Sat 10 Jul 2021 at 15:41:27 +0200, Martin Husemann wrote:
> > On Sat, Jul 10, 2021 at 03:39:10PM +0200, Rhialto wrote:
> > > How far did you get? I tried sun3, and I got to booting the ramdisk
>
> Oh this is with NetBSD/amd64 9.2, not -
On Sat 10 Jul 2021 at 15:41:27 +0200, Martin Husemann wrote:
> On Sat, Jul 10, 2021 at 03:39:10PM +0200, Rhialto wrote:
> > How far did you get? I tried sun3, and I got to booting the ramdisk
Oh this is with NetBSD/amd64 9.2, not -current. I don't know if that
makes a difference.
-Olaf.
--
___ "
On Sat, Jul 10, 2021 at 03:39:10PM +0200, Rhialto wrote:
> How far did you get? I tried sun3, and I got to booting the ramdisk
> kernel from tape. But when I did the "dd bs=32k if=/dev/nrst0
> of=/dev/rsd0b" I got a core dump. Possibly I had not used edlabel
> correctly due to it not getting a geom
On Sat 10 Jul 2021 at 12:50:08 +0200, Martin Husemann wrote:
> Anyone feel like looking into that? The homepage has nice instructions and
> setup is very straight forward. I am mostly interested in sun2, sun3 and
> sun4c currently.
How far did you get? I tried sun3, and I got to booting the ramdis
On Sat, 10 Jul 2021 at 11:50, Martin Husemann wrote:
>
> The emulators/tme pkg is a nice, lightweight pkg allowing you to run
> various sun machines on amd64 (and others). I recently needed it for testing
> some openssl fallout in netbsd-9 (where qemu seems to only emulate machines
> for which it
The emulators/tme pkg is a nice, lightweight pkg allowing you to run
various sun machines on amd64 (and others). I recently needed it for testing
some openssl fallout in netbsd-9 (where qemu seems to only emulate machines
for which it works and that I also have as real hardware).
Unfortunately the
On Sat, Jul 10, 2021 at 09:00:37AM +, dashdruid wrote:
> Also LEX was not present in /usr/bin so I have installed flex and
> linked the flex binary to lex, idk if its a problem.
Assuming you actually mean /usr/bin/lex then this tells you that something
went wrong during installation of your sy
Hello List,
I keep getting this error whatever I try to build from pkgsrc on NetBSD9.1 i386.
Even if I follow the basic tutorial with figlet:
https://wiki.netbsd.org/pkgsrc/how_to_use_pkgsrc/
It's the same error for all packages.
I have tried with GCC10, 7, 5
Also LEX was not present in /usr/
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2021.07.10.07.50.33.
An extract from the build.sh output follows:
--- dependall-external ---
nbmake[6]: stopped
18 matches
Mail list logo
