On Sat, Oct 19, 2002 at 12:02:21AM -0700, Julian Elischer wrote:
> Unfortunaly you need to replace almost all X11 stuff..
Not quite. You can easily identify problematic packages by doing something
like:
$ for f in `find /usr/X11R6/ -type f`; do nm $f 2>/dev/null | grep -qw "U __sF" &&
echo $f; d
Hi folks,
I saw many warning messages when compiling sth. under -current
(as expected) while I turned on the "-DNO_WERROR" in /etc/make.conf
as told in UPDATING.
But the warnings are always the same: "ISO C89 doesn't support %s",
so I thought about turning on the -std=c99 switch. But the kernel
c
On Sun, 2002-10-13 at 23:00, Eric Anholt wrote:
> On Sun, 2002-10-13 at 21:14, Kris Kennaway wrote:
> > On Sun, Oct 13, 2002 at 11:28:51PM -0400, Wesley Morgan wrote:
> >
> > > I know there is some work being done on the recent signal changes to fix
> > > some things, but are we sure this is the p
Long, Scott wrote:
All I'm asking is that ports maintainers make
an effort to maintain their ports. Will's accertation that it's an
all or nothing issue is certainly not productive, and neither is the
'us versus them' inuendo here.
The single one -CURRENT vs. -STABLE difference that causes many
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Hi,
I've noticed that after upgrading my -current box (15 Oct snapshot)
the `nroff -mandoc foo.X | less' construction no longer does produce
valid results. I'm seeing ESC[ all over the place, i.e.:
ESC[1mNAMEESC[0m
ESC[1mradioctl ESC[22m- control radio tuners
ESC[1mSYNOPSISESC[0m
ESC[1
At 04:15 19/10/2002, Alfred Perlstein wrote:
* Jake Burkholder <[EMAIL PROTECTED]> [021018 18:26] wrote:
> semop() leaks memory. An important free() was removed by alfred in
> rev 1.55. Try this.
Oh' c'mon, isn't MP-safeness a bit more important than a some
little memory leak, ram is cheap! pro
At 13:34 19/10/2002, Ben Stuyts wrote:
At 04:15 19/10/2002, Alfred Perlstein wrote:
* Jake Burkholder <[EMAIL PROTECTED]> [021018 18:26] wrote:
> semop() leaks memory. An important free() was removed by alfred in
> rev 1.55. Try this.
Seriously, I just checked in slightly different fix (based
On Sat, Oct 19, 2002 at 11:07:19AM +0300, Maxim Sobolev wrote:
> On Sat, Oct 19, 2002 at 12:02:21AM -0700, Julian Elischer wrote:
> > Unfortunaly you need to replace almost all X11 stuff..
>
> Not quite. You can easily identify problematic packages by doing something
> like:
>
> $ for f in `find
Well, now the bad free (actually appeared to me to be a bad malloc or a bad
call to malloc) is fixed; now I get a panic from GEOM (actually from
witness). There are 3 or 4 geom debug messages and then a panic
indicating Giant not owned. I'll follow up with an actual trace from a
serial consol
On Sat, Oct 19, 2002 at 02:11:34PM +0300, Maxim Sobolev wrote:
> Hi,
>
> I've noticed that after upgrading my -current box (15 Oct snapshot)
> the `nroff -mandoc foo.X | less' construction no longer does produce
> valid results. I'm seeing ESC[ all over the place, i.e.:
FreeBSD titan.klemm.apsfil
> A new set of 5.0 packages has been uploaded and is making its way out
> to mirror sites. I will soon be sending out mail to all maintainers
> of broken ports asking for submissions of fixes (or at least reporting
> the breakage to the relevant vendors).
Hmm, I've more broken ports on my system..
* Ben Stuyts <[EMAIL PROTECTED]> [021019 07:16] wrote:
> At 13:34 19/10/2002, Ben Stuyts wrote:
> >At 04:15 19/10/2002, Alfred Perlstein wrote:
> >>* Jake Burkholder <[EMAIL PROTECTED]> [021018 18:26] wrote:
> >>> semop() leaks memory. An important free() was removed by alfred in
> >>> rev 1.55.
On Sat, 19 Oct 2002, Maxim Sobolev wrote:
> On Sat, Oct 19, 2002 at 12:02:21AM -0700, Julian Elischer wrote:
> > Unfortunaly you need to replace almost all X11 stuff..
>
> Not quite. You can easily identify problematic packages by doing something
> like:
>
> $ for f in `find /usr/X11R6/ -type
Following up on my own message:
> Well, now the bad free (actually appeared to me to be a bad malloc or a bad
> call to malloc) is fixed; now I get a panic from GEOM (actually from
> witness). There are 3 or 4 geom debug messages and then a panic
> indicating Giant not owned. I'll follow up wi
In message <[EMAIL PROTECTED]>, Pete Carah writes:
>mbr_taste(MBR,geom.ctl)
>panic: mutex Giant not owned at /current/usr/src/sys/vm/vm_map.c:384
>Debugger("panic")
>Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
>db> tr
>Debugger(c035289f,c03c1880,c0351bb8,d7196bd8,1) at Debugger+0x54
* De: Eric Anholt <[EMAIL PROTECTED]> [ Data: 2002-10-19 ]
[ Subjecte: Re: X problems & 5.0... -RELEASE? ]
> >From the reports:
>
> Both stable and current users get the "self-healing" hang, where the X
> server responds to nothing but the mouse moves, and at some minutes
> later time it c
On Sat, Oct 19, 2002 at 08:19:18AM +0300, Maxim Sobolev wrote:
> > At some point before 5.0-RELEASE I will go through and mark all ports
> > listed on bento as BROKEN (consider this fair warning: I will not
> > entertain any complaints from port maintainers who take offense on the
> > basis of ign
On Sat, 19 Oct 2002, Juli Mallett wrote:
> Note that during these, mp3s keep playing, gtk-gnutella keeps downloading
> things, etc., it seems X just isn't updating the display... Even a resize
> of a sizable gtk frame I did while it was frozen took affect when it
> unfroze... Have you tried logg
> Note that during these, mp3s keep playing, gtk-gnutella keeps downloading
> things, etc., it seems X just isn't updating the display... Even a resize
But, it's not always so. For me most of the time everything stops.
Including playing mp3s/oggs, resizing windows and so on. And after some
time ju
On Mon, 2002-10-07 at 11:13, Andrew Gallatin wrote:
>
> Every so often, my X server locks up. It seems to be in a tight
> loop, 95% user time, and making only these ktrace'able calls:
>
> 27069 XFree86 0.019988 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0
> 27069 XFree86 0.39
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Sat, 19 Oct 2002 13:58:48 -0700
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> Sorry, my statement wasn't clear. I'll be doing something of the form
>
> .if ${OSVERSION} > 50
> BROKEN= "Does not compile on FreeBSD 5.x"
> .endif
>
> This will not affect users of 4.x
>
Is there a "corre
Well, the new groff update breaks world on Alpha. The groff does
work ok on sparc64. The alpha build dies trying to format the
usd/13.viref document. During the actual buildworld groff exited
with an 'out of memory' error. I did a world with NO_SHAREDOCS
and now when I try to build the share do
On Sat, Oct 19, 2002 at 11:57:37PM +0200, Clement Laforet wrote:
> On Sat, 19 Oct 2002 13:58:48 -0700
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> > Sorry, my statement wasn't clear. I'll be doing something of the form
> >
> > .if ${OSVERSION} > 50
> > BROKEN= "Does not compile on Free
* De: Marc Recht <[EMAIL PROTECTED]> [ Data: 2002-10-19 ]
[ Subjecte: Re: X problems & 5.0... -RELEASE? ]
> > Note that during these, mp3s keep playing, gtk-gnutella keeps downloading
> > things, etc., it seems X just isn't updating the display... Even a resize
> But, it's not always so. F
> Hmm, I've more broken ports on my system.. Like a trouble with net/samba-devel
> (because of PAM headers) and I can't compile lang/librep since KSE III.
Are you still having problems with this. If you could show me some
errors I may be able to relay them to the samba developers for you
unles
On Sa, 2002-10-19 at 22:36, David W. Chapman Jr. wrote:
> > Hmm, I've more broken ports on my system.. Like a trouble with net/samba-devel
> > (because of PAM headers) and I can't compile lang/librep since KSE III.
>
> Are you still having problems with this. If you could show me some
> errors
28 matches
Mail list logo
