Re: build kernel from source

2014-09-21 Thread Alan Barrett
On Mon, 22 Sep 2014, bycn82 wrote: On 9/22/14 1:12, Mindaugas Rasiukevicius wrote: make: stopped in /usr/src/usr.sbin/npf/npfctl I suspect that you have a corrupted source tree. Please take this to current-users, not tech-kern. Unlikely. I think he is just trying to build -current code on 6.

daily CVS update output

2014-09-21 Thread NetBSD source update
Updating src tree: P src/etc/rc.subr P src/etc/rc.d/network P src/lib/libpci/Makefile P src/lib/libpci/pci.h P src/share/misc/airport P src/sys/arch/amiga/amiga/disksubr.c P src/sys/arch/amiga/dev/siop.c P src/sys/arch/amiga/dev/siop2.c P src/sys/arch/arm/arm32/pmap.c P src/sys/arch/arm/iomd/iomd_

Re: a separate build of libc

2014-09-21 Thread Alan Barrett
On Sun, 21 Sep 2014, u-6...@aetey.se wrote: My goal is among others to be able to make a corresponding operation given just a running NetBSD kernel and nothing in the "standard paths". My common sense and experience say that the standard tools are not applicable. I am not sure that you under

Automated report: NetBSD-current/i386 build failure

2014-09-21 Thread NetBSD Test Fixture
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.21.15.07.19. An extract from the build.sh output follows: /tmp/bracket/build/2014.09.21.15.07.19-i386/src/s

Re: a separate build of libc

2014-09-21 Thread u-6hol
On Sun, Sep 21, 2014 at 03:59:28PM +0200, Martin Husemann wrote: > On Sun, Sep 21, 2014 at 11:25:36AM +0200, u-6...@aetey.se wrote: > > This is not a duplication but a separate effort with different goals. > > But we fail to understand your goals. Regrettably, this is somewhat hard to explain in

Re: a separate build of libc

2014-09-21 Thread Alan Barrett
On Sun, 21 Sep 2014, u-6...@aetey.se wrote: One of the assumptions in the NetBSD build system is that you have the entire source tree This is a quite large assumption :) Of course. It's "NetBSD", not "the libc from NetBSD". Another important assumption is that the build is run on a host wi

Re: a separate build of libc

2014-09-21 Thread u-6hol
On Sun, Sep 21, 2014 at 05:37:35PM +0200, Martin Husemann wrote: > On Sun, Sep 21, 2014 at 05:16:59PM +0200, u-6...@aetey.se wrote: > > I need also a standard NetBSD installation and several hundred MB sources, > > don't I? > > No, not the former. Any posix-ish system will do. I see. OTOH my syst

Re: a separate build of libc

2014-09-21 Thread u-6hol
On Sun, Sep 21, 2014 at 04:20:53PM +0200, Alan Barrett wrote: > On Sun, 21 Sep 2014, u-6...@aetey.se wrote: > >>might be some "restrictions/assumptions" nobody might have noticed or be > >>willing to fix? > > > >Exactly. More often than not I happen to notice arbitrary restrictions and > >assumptio

Re: a separate build of libc

2014-09-21 Thread Martin Husemann
On Sun, Sep 21, 2014 at 05:16:59PM +0200, u-6...@aetey.se wrote: > I need also a standard NetBSD installation and several hundred MB sources, > don't I? No, not the former. Any posix-ish system will do. But the second is true, you need the full source tree. Not everything of that will be used, an

Re: a separate build of libc

2014-09-21 Thread Alan Barrett
On Sun, 21 Sep 2014, u-6...@aetey.se wrote: might be some "restrictions/assumptions" nobody might have noticed or be willing to fix? Exactly. More often than not I happen to notice arbitrary restrictions and assumptions which people tend to perceive as natural. One of the assumptions in the

Re: a separate build of libc

2014-09-21 Thread Martin Husemann
On Sun, Sep 21, 2014 at 11:25:36AM +0200, u-6...@aetey.se wrote: > This is not a duplication but a separate effort with different goals. But we fail to understand your goals. All you need to do is: - build.sh tools - nbmake includes - cd lib/libc && nbmake obj dependall install or someth

Re: a separate build of libc

2014-09-21 Thread u-6hol
On Sat, Sep 20, 2014 at 05:22:59PM -0400, Thor Lancelot Simon wrote: > > The intention is to have an independent and self-contained toolchain, to > > avoid any explicit or implicit restrictions/assumptions of the existing > > building routines. > > I don't understand. You will work very, very har