Problems with j2sdk_1.3.1

2002-07-13 Thread Andrzej Kwiatkowski
When i try to compile Openoffice 1.0 my instalation stops when compiling port jdk13 My output looks like: g++ -Wall -Wno-unused -Wconversion -c -I/usr/local/include -O -D_GNU_SOURCE -DXP_UNIX -DVERSION="\"1.3.1-p6-kwiatek-020712-17:22\"" -DDATE="\"Jul-12-2002\"" -DARCH="\"i386\"" -DRAPTOR_API -

Re: New ipfw isn't 64-bit clean

2002-07-13 Thread Luigi Rizzo
Seems to me that the problem is not in ipfw2.c but rather in different structure padding when compiling the kernel and userland. ipfw2.c uses sizeof() to determine the size of the structure so it does not make any assumptions on operand sizes etc. Re. the printf problems could you submit a patch

Re: Problems with j2sdk_1.3.1

2002-07-13 Thread Szilveszter Adam
Hello, On Sat, Jul 13, 2002 at 10:00:43AM +0200, Andrzej Kwiatkowski wrote: > When i try to compile Openoffice 1.0 > my instalation stops when compiling port jdk13 > My output looks like: <...> > -I../../../../src/solaris/javavm/export -I/usr/X11R6/include -o > ../../tmp/bsd/i386/GetFactory.o

sparc64 tinderbox failure

2002-07-13 Thread Dag-Erling Smorgrav
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: Here's a new(er) one

2002-07-13 Thread Christian Brueffer
I got a similar one tonight: GNU gdb 5.2 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. Th

Re: mergemaster failure

2002-07-13 Thread Giorgos Keramidas
On 2002-07-12 23:50 +, Munish Chopra wrote: > I first saw this a while ago (10 days?) but thought I'd screwed > something up myself. Didn't get a chance to clean the box up fully and > try again until this morning. After a successfull buildworld, trying to > do a mergemaster, this happens: >

Re: i386 trap code

2002-07-13 Thread Alfred Perlstein
* David Xu <[EMAIL PROTECTED]> [020712 19:38] wrote: > > when did the vm86_lock become spin lock ? I havn't seen changes in cvs, > it is still a MTX_DEF. I had tried changing it to spin lock and got a > panic. :( Did you also change the functions that access it to use mtx_*_spin? -- -Alfred P

Re: i386 trap code

2002-07-13 Thread John Baldwin
On 13-Jul-2002 Alfred Perlstein wrote: > * David Xu <[EMAIL PROTECTED]> [020712 19:38] wrote: >> >> when did the vm86_lock become spin lock ? I havn't seen changes in cvs, >> it is still a MTX_DEF. I had tried changing it to spin lock and got a >> panic. :( > > Did you also change the function

Out of disk space on snapshots-jp?

2002-07-13 Thread Donny Lee
Hi there, it looks like the past few days snapshots build failures were all because out of disk space on the snapshots-jp box. -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Update to the DRM

2002-07-13 Thread Michael Nottebrock
Eric Anholt wrote: > On Wed, 2002-07-10 at 17:17, Eric Anholt wrote: > >>I've posted a diff to the DRM at >>http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta > > > Evolution's "send" button is way too big. > > http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.di

Re: Update to the DRM

2002-07-13 Thread Eric Anholt
On Sat, 2002-07-13 at 11:23, Michael Nottebrock wrote: > Eric Anholt wrote: > I have just compiled a world with the 20020711.diff. It sure runs fast, > but the quality isn't very good. I tested with glxgears and gltron and > in both there is a lot of flashing and lighting errors. > > Do you ha

Re: bus_alloc_resrouce() fails in if_wi.c

2002-07-13 Thread M. Warner Losh
: wi0: mem 0xf420-0xf4200fff irq 3 at device 11.0 on pci1 : pcib1: device wi0 requested unsupported memory range 0x0-0xf41f (decoding :0xf410-0xf41f, 0xf420-0xf42f) : wi0: No Mem space on prism2.5? : device_probe_and_attach: wi0 attach returned 6 Yes. The pcib1 message

Re: HEADS UP, beware of pmap changes.

2002-07-13 Thread Peter Wemm
Peter Wemm wrote: > Peter Wemm wrote: > > This is mostly a FYI because I do not expect major problems this time. > > I have been extensively testing it in a handful of configurations. > > As murphy would dictate, something fishy is going on. In the last 12 hours > or so (I had a long sleep), I'v

Re: Here's a new(er) one

2002-07-13 Thread Don Lewis
What was the original panic message, the one where uma_core.c prints the name of the lock being held and where it was locked? On 12 Jul, Alex Zepeda wrote: > * $FreeBSD: src/sys/kern/vfs_bio.c,v 1.319 2002/07/10 17:02:28 dillon Exp $ > * $FreeBSD: src/sys/kern/vfs_syscalls.c,v 1.267 2002/07/02 1

Re: Here's a new(er) one

2002-07-13 Thread zipzippy
On Sat, Jul 13, 2002 at 07:28:43PM -0700, Don Lewis wrote: > What was the original panic message, the one where uma_core.c prints the > name of the lock being held and where it was locked? Any way to determine this post-mortem? I woke up and the system had rebooted. Unfortunately the power sup

Re: Here's a new(er) one

2002-07-13 Thread Don Lewis
On 13 Jul, zipzippy wrote: > On Sat, Jul 13, 2002 at 07:28:43PM -0700, Don Lewis wrote: > >> What was the original panic message, the one where uma_core.c prints the >> name of the lock being held and where it was locked? > > Any way to determine this post-mortem? I woke up and the system had

Re: Here's a new(er) one

2002-07-13 Thread Juli Mallett
* De: Don Lewis <[EMAIL PROTECTED]> [ Data: 2002-07-13 ] [ Subjecte: Re: Here's a new(er) one ] > On 13 Jul, zipzippy wrote: > > On Sat, Jul 13, 2002 at 07:28:43PM -0700, Don Lewis wrote: > > > >> What was the original panic message, the one where uma_core.c prints the > >> name of the lo