On Fri, Sep 19, 2014 at 09:25:52AM +0100, Matthias Scheler wrote:
tron@lyssa:~#installboot -v /dev/rwd0a /usr/mdec/bootxx_ffsv1
installboot: Opening file system `/dev/rwd0a' read-write: Device busy
This is fallout from the wedges auto-configuration changes.
You should be able (in
On Fri, Sep 19, 2014 at 10:33:59AM +0200, Martin Husemann wrote:
On Fri, Sep 19, 2014 at 09:25:52AM +0100, Matthias Scheler wrote:
tron@lyssa:~#installboot -v /dev/rwd0a /usr/mdec/bootxx_ffsv1
installboot: Opening file system `/dev/rwd0a' read-write: Device busy
This is fallout
Background:
building an independent/standalone toolchain able to produce binaries
runnable on NetBSD
(note, this is not the same as compiling or cross-compiling NetBSD)
The component:
libc
A small practical question:
Where does machine/asm.h come from, given the NetBSD source sets
= Background:
=
= building an independent/standalone toolchain able to produce binaries
= runnable on NetBSD
= (note, this is not the same as compiling or cross-compiling NetBSD)
=
= The component:
=
= libc
=
= A small practical question:
=
= Where does machine/asm.h come from, given the
In article 20140908120242.1123c17f...@rebar.astron.com,
Christos Zoulas chris...@zoulas.com wrote:
On Sep 8, 12:47pm, a...@absd.org (David Brownlee) wrote:
-- Subject: Re: Wedges sysinst (Was: Wedges enabled on -current)
| Its been three weeks since wedges mbr and disklabels was enabled in
|
On Fri, Sep 19, 2014 at 11:56:57AM -0400, g...@duzan.org wrote:
= A small practical question:
=
= Where does machine/asm.h come from, given the NetBSD source sets as
= the starting point?
The small question I can handle: see src/sys/arch/*/include/asm.h .
Thanks Gary!
Rune
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 2014.09.19.18.05.24.
An extract from the build.sh output follows:
obsolete_stand fix:
postinstall fixes passed:
On Fri, Sep 19, 2014 at 04:04:34PM +0200, u-6...@aetey.se wrote:
Background:
building an independent/standalone toolchain able to produce binaries
runnable on NetBSD
Why don't you just run build.sh -m machine tools and use the result?
Thor
Updating src tree:
P src/build.sh
U src/common/lib/libc/arch/riscv/atomic/Makefile.inc
U src/common/lib/libc/arch/riscv/atomic/atomic_add_32.S
U src/common/lib/libc/arch/riscv/atomic/atomic_add_64.S
U src/common/lib/libc/arch/riscv/atomic/atomic_and_32.S
U
