--qDbXVdCdHGoSgWSk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Jan 21, 2004 at 12:52:13PM -0600, Richard Rauch wrote:
> On Wed, Jan 21, 2004 at 04:37:44PM +0100, Nicolas Joly wrote:
>  [...]
> > cd src/x11
> > make build
> > make install DESTDIR=/
> 
> ....
> rm -f SetSOwner.o.tmp
> #   compile  static/SetSOwner.po
> /usr/netbsd/current/src/obj.amd64/tooldir.NetBSD-1.6ZH-x86_64/bin/x86_64--netbsd-gcc -O2  -Werror    -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API  -DXNO_MTSAFE_PWDAPI -DUSE_NBSD_THREADLIB -I. -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -I/usr/X11R6/include   -nostdinc -isystem /usr/include -c    -pg /usr/netbsd/current/xsrc/xfree/xc/lib/X11/SetSOwner.c -o SetSOwner.po.tmp
> [1]   Segmentation fault (core dumped) make realall
> *** Error code 139

Gasp !

> > ...Some points to note:
> 
> I have a /usr/netbsd/xsrc (not src/x11) where I built everything successfully
> last night, and am running X from that build.
> 
> Second, the segfault happens at different times in the build, but is always
> accompanied by a stream of NFS errors about "server not responding"
> and "server alive again".  (Sources are on an NFS server since NetBSD does
> not yet know how to do DMA with the nVidia pciide controller.  NFS is
> almost exactly as fast as PIO for this machine, and has much lower CPU over-
> head, so I use NFS.  (^&)
> 
> Third: The NFS freezes seem to be systemic since upgrading to -current
> yesterday.  With the previous snapshot, hitting CapsLock would cause a
> ~1 second freeze of the entire system (as near as I can tell).  That bug
> has gone away, now, but has been replaced by more random-seeming freezes.
> (The freezes seem to generally be caused by filesystem, and/or NFS,
> activity.  But it could be broader than that.)

I got them too, at least with NFS. It seems to be a locking problem,
as a LOCKDEBUG compiled kernel often fall in DDB with high NFS
activity.

> Fourth...when I did the command as you had it above, I initially had a
> problem with an "install" command that was unable to find the tooldir-built
> "install" program.  (So maybe I had it 99% okay until I did a
> "sh build.sh tools" and retried the "make build"?)  That failure was not
> a signal, but was simply a "couldn't find .../nbinstall", so I did the
> obvious thing of updating my tools.)

Ok, forget it (Sorry, i didn't tested it :-(). Let's try the build.sh
way ...

Here is what i'm currently using to upgrade my bi-Oteron box :

./build.sh -Uu -m amd64 build
./build.sh -Uu -m amd64 install=/

With a small patch in `distrib/sets/Makefile' (attached) to enable X11
sets installation with the 2nd build.sh command.

-- 
Nicolas Joly

Biological Software and Databanks.
Institut Pasteur, Paris.

--qDbXVdCdHGoSgWSk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="netbsd-x11install.diff"

Index: distrib/sets/Makefile
===================================================================
RCS file: /cvsroot/src/distrib/sets/Makefile,v
retrieving revision 1.40
diff -u -r1.40 Makefile
--- distrib/sets/Makefile	2004/01/08 01:48:45	1.40
+++ distrib/sets/Makefile	2004/01/22 09:17:59
@@ -116,7 +116,8 @@
 	@echo "setenv INSTALLDIR before doing that!"
 	@false
 .endif
-	${SETSENV} ${HOST_SH} ${.CURDIR}/maketars -d ${DESTDIR:S,^$,/,} \
+	${SETSENV} ${HOST_SH} ${.CURDIR}/maketars \
+	    ${MAKEFLIST_FLAGS} -d ${DESTDIR:S,^$,/,} \
 	    ${METALOG.unpriv} -N ${NETBSDSRCDIR}/etc \
 	    -i ${INSTALLDIR} ${INSTALLSETS}
 

--qDbXVdCdHGoSgWSk--