On (2002/07/10 19:15), Dirk Engling wrote:
> Maybe this would be more interesting to
> the mozilla guys but mozilla compiles on
> 2.95.3, so I think, the problem is related
> to gcc-3.1
As far as I know, ports/lang/gcc31 is still required to build mozilla.
Ciao,
Sheldon.
To Unsubscribe: send m
Bruce,
On Thu, Jul 11, 2002 at 08:23:06AM +1000, Bruce Evans wrote:
>> The extra verboseness is fine, and I was almost finished posting a
>> note that mentioned it. But I didn't thinking that the __printf0like
>> bugs will never be fixed if we hide them by patching chmod.
> It was "fixed" more
My entire machine is built from source.
I started with no packages installed at all.
The only think I can think of is old binaries/libraries/other files left
behind from earlier -CURRENT. Is there a tool to clean these up yet? Maybe
it should be part of mergemaster. I'll clean them up manuall
Giorgos Keramidas <[EMAIL PROTECTED]> writes:
> Whoever fixes this, and however we agree to fix it,
> should also remember to close the bin/40382 PR.
Comments on the attached, untested patch?
Best regards,
Mike Barcroft
Disable fatal warnings during bootstrap, build, and cross tools
phase of w
I'm not sure what the deal with X is, but I have several non-X11 C++
programs that work just fine.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, Jul 10, 2002 at 01:34:50PM -0700, Don Lewis wrote:
> > ../../../vm/uma_core.c:1332: could sleep with "inp" locked from
>../../../netinet/tcp_subr.c:935
> > ../../../vm/uma_core.c:1332: could sleep with "tcp" locked from
>../../../netinet/tcp_subr.c:928
>
> I've never seen that one. I'
"Thyer, Matthew" wrote:
> Thanks Dirk but I cant install ports/x11/XFree86-4-clients either!
>
> Errors below a gcc 3.1 ism maybe ?
Almost certainly a compiler mixup. Did you install a binary package?
Secondly.. you have:
rm -f glxinfo
LD_LIBRARY_PATH=../../exports/lib cc -o glxinfo -ansi
On Thu, Jul 11, 2002 at 11:01:04AM +0930, Benjamin Close wrote:
> Hi All,
>I'm using current from just after the KSE & libc_r fix. However it
> appears that XFree86-client c++ stuff is still broken. Is there a
> planned time when this will be fixed or am I missing something else?
> (XFree-l
Thanks Dirk but I cant install ports/x11/XFree86-4-clients either!
Errors below a gcc 3.1 ism maybe ?
installing in programs/scripts...
/usr/bin/install -c -m 0755 xon.sh /usr/X11R6/bin/xon
install in programs/scripts done
installing in programs/glxinfo...
rm -f glxinfo
LD_LIBRARY_PATH=../.
Hi All,
I'm using current from just after the KSE & libc_r fix. However it
appears that XFree86-client c++ stuff is still broken. Is there a
planned time when this will be fixed or am I missing something else?
(XFree-libraries compiled and installed without a hitch ).
rm -f glxinfo
LD_LIBR
Doesn't seem to work for me with PERL defined in my environment and/or in
/etc/make.conf.
make: don't know how to make /usr/X11R6/bin/ucs2any.pl. Stop
*** Error code 2
Stop in /usr/ports/x11-fonts/XFree86-4-font100dpi.
*** Error code 1
Stop in /usr/ports/x11/XFree86-4.
fuzz: {1025} env | grep P
Whoever fixes this, and however we agree to fix it,
should also remember to close the bin/40382 PR.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Thus spake Peter Wemm <[EMAIL PROTECTED]>:
> Please do not. gcc is just a tool. If it emits a warning on some arches
> because gcc doesn't understand how our libraries work, then we should
> disable the gcc checking for those arches on those functions. ie: remove
> the __printf0like completely
On Wed, Jul 10, 2002 at 19:55:19 +0200, Dag-Erling Smorgrav wrote:
> Neither fix is correct. The correct solution is to remove the kludge
> in auth-passwd.c that tries to use PAM for password authentication.
I agree completely. My fix was quick & dirty workaround only and not
planned as a full
Peter Wemm <[EMAIL PROTECTED]> writes:
[...]
> peter@panther[4:22pm]~-106> cc -O -Wformat -c foo.c
> peter@panther[4:22pm]~-107>
>
> ie: it looks like it is completely disabled. Maybe the sparc64 tinderbox
> host is simply out of sync with -current?
It has a kernel/world of June 27, which seems
Eric Anholt wrote:
> I've posted a diff to the DRM at
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta
http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.diff
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body
On Wednesday, July 10, 2002, at 05:22 PM, Matthew Dillon wrote:
[snips]
>
> Personally speaking, as much as GCC annoys me it is sometimes
> better to
> modify the utility code then to add yet another hack to GCC that
> needs
> to be synchronized every time we update.
>
>
Dag-Erling Smorgrav wrote:
> Bruce Evans <[EMAIL PROTECTED]> writes:
> > The main bug is that the warning is emitted. err(1, NULL) is perfectly
> > valid (see err(4)). Apparently the sparc64 compiler is missing support
> > for __printf0like.
>
> Strangely, my Alpha (July 3 -CURRENT) complains a
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.diff
is the file. The patch brings t
Matthew Dillon wrote:
>
> :
> :Giorgos Keramidas <[EMAIL PROTECTED]> writes:
> :> How does this look for fixing this warning?
> :
> :No, gcc should accept a NULL format string for err(3). It looks like
> :__printf0like is broken.
> :
> :DES
> :--
> :Dag-Erling Smorgrav - [EMAIL PROTECTED]
>
>
I've posted a diff to the DRM at
http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> > Fatal error '_waitq_remove: Not in queue' at line 350 in file
> > /usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 0)
> I get the same message with xine on -STABLE each time i use it.
I've had this problem for months if not years, in all recent releases
of FreeBSD. It's not con
On Thu, 11 Jul 2002, Giorgos Keramidas wrote:
> The extra verboseness is fine, and I was almost finished posting a
> note that mentioned it. But I didn't thinking that the __printf0like
> bugs will never be fixed if we hide them by patching chmod.
It was "fixed" more than a month ago:
% RCS fi
Bruce Evans <[EMAIL PROTECTED]> writes:
> The main bug is that the warning is emitted. err(1, NULL) is perfectly
> valid (see err(4)). Apparently the sparc64 compiler is missing support
> for __printf0like.
Strangely, my Alpha (July 3 -CURRENT) complains about this too, but my
i386 (June 24 -CU
On 2002-07-10 14:22 +, Matthew Dillon wrote:
> :Giorgos Keramidas <[EMAIL PROTECTED]> writes:
> :> How does this look for fixing this warning?
> :
> :No, gcc should accept a NULL format string for err(3). It looks like
> :__printf0like is broken.
>
> Oops. I've already starting changing
On Wed, 10 Jul 2002, Giorgos Keramidas wrote:
> On 2002-07-10 09:58 +, Dag-Erling Smorgrav wrote:
> > ===> bin/chmod
> > cc1: warnings being treated as errors
> > /usr/home/des/tinderbox/sparc64/src/bin/chmod/chmod.c: In function `main':
> > /usr/home/des/tinderbox/sparc64/src/bin/chmod/chmod
:
:Giorgos Keramidas <[EMAIL PROTECTED]> writes:
:> How does this look for fixing this warning?
:
:No, gcc should accept a NULL format string for err(3). It looks like
:__printf0like is broken.
:
:DES
:--
:Dag-Erling Smorgrav - [EMAIL PROTECTED]
Oops. I've already starting changing the ca
Giorgos Keramidas <[EMAIL PROTECTED]> writes:
> How does this look for fixing this warning?
No, gcc should accept a NULL format string for err(3). It looks like
__printf0like is broken.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubsc
On Wed, Jul 10, 2002 at 09:32:07PM +0200, Gary Jennejohn wrote:
> Christian Brueffer writes:
> > The issue with mplayer is, that it crashes when i want to watch two
> > consecutive files. The first one works fine, but when I want to play
> > the second one, it crashes each time :)
> >
>
> Have y
On 10 Jul, Alex Zepeda wrote:
> On Wed, Jul 10, 2002 at 02:43:54AM -0700, Don Lewis wrote:
>
>> I haven't had any instability problems in a while on my UP box.
>
> Seems like the UP kernels are more unstable for me. Go figure.
>
>> > ../../../vm/uma_core.c:1332: could sleep with "process lock"
On 10 Jul, Dan Nelson wrote:
> I see this one once every 10 seconds or so:
>
> ../../../vm/uma_core.c:1332: could sleep with "inp" locked from
>../../../netinet/tcp_subr.c:935
> ../../../vm/uma_core.c:1332: could sleep with "tcp" locked from
>../../../netinet/tcp_subr.c:928
I've never seen th
+ Graham Guttocks wrote:
| I'm building a new primary office workstation and
| thought I might try -current instead of 4.6-STABLE
| in order to make upgrading to 5.0-RELEASE easier.
|
| Will this make it easier to upgrade to 5.0-RELEASE
| when that happens, or does it not really matter?
Runni
I'm building a new primary office workstation and
thought I might try -current instead of 4.6-STABLE
in order to make upgrading to 5.0-RELEASE easier.
Will this make it easier to upgrade to 5.0-RELEASE
when that happens, or does it not really matter?
Regards,
Graham
___
On 2002-07-10 09:58 +, Dag-Erling Smorgrav wrote:
> ===> bin/chmod
> cc1: warnings being treated as errors
> /usr/home/des/tinderbox/sparc64/src/bin/chmod/chmod.c: In function `main':
> /usr/home/des/tinderbox/sparc64/src/bin/chmod/chmod.c:174: warning: null format
>string
How does this look
"Andrey A. Chernov" wrote:
> On Wed, Jul 10, 2002 at 14:17:51 +0200, Dag-Erling Smorgrav wrote:
> > "Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> > > Why what? Sysadmin allows PasswordAuthentication only.
> >
> > Why?
>
> Because he choose to not trust hosts keys which can be stolen especiall
Dag-Erling Smorgrav wrote:
> Alex Zepeda <[EMAIL PROTECTED]> writes:
> > After the rude awakening that I was after all running current, I've
> > finally turned on the WITNESS related options for my kernel
>
> Congratulations in turning your -CURRENT box into a doorstop! ;)
Magician: For m
Christian Brueffer writes:
> The issue with mplayer is, that it crashes when i want to watch two
> consecutive files. The first one works fine, but when I want to play
> the second one, it crashes each time :)
>
Have you tried using a playlist ? I've played maybe 20 files in a
row doing that.
-
On Wed, 10 Jul 2002, Archie Cobbs wrote:
> John Baldwin writes:
> > It is the same problem. What we do is change callout_stop() to let you know if
> > it actually stopped the timeout or not. You then have to use your own locking
> > and synchronization in the timeout function and yourself to c
On Wed, 10 Jul 2002, John Baldwin wrote:
> On 09-Jul-2002 Julian Elischer wrote:
> > On Wed, 10 Jul 2002, Bruce Evans wrote:
> >> Can these flags be changed asynchronously? If so, then everything needs
> >> to be handled by ast() anyway. userret() should only check for work that
> >> needs doin
[ NOTE: I'm moving this discussion to [EMAIL PROTECTED] ]
John Baldwin writes:
> > What do you think of the idea of letting the timer code (optionally)
> > handle all the locking and race conditions?
>
> I'm not sure it can in a clean fashion since of the few cases I've known
> so far each clie
On Wed, Jul 10, 2002 at 02:43:54AM -0700, Don Lewis wrote:
> I haven't had any instability problems in a while on my UP box.
Seems like the UP kernels are more unstable for me. Go figure.
> > ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from
>../../../kern/kern_exec.c:3
Neither fix is correct. The correct solution is to remove the kludge
in auth-passwd.c that tries to use PAM for password authentication.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--- "Thyer, Matthew" <[EMAIL PROTECTED]> wrote:
> make: don't know how to make /usr/X11R6/bin/ucs2any.pl. Stop
> *** Error code 2
>
> --
Try:
build ports/lang/perl and set env PERL to /usr/local/bin/perl
__
Do You Yahoo!?
Sign up for SBC Yahoo!
On Wed, Jul 10, 2002 at 09:37:24 -0700, Gregory Neil Shapiro wrote:
> The problem seems to be the addition of opieaccess to the PAM
> configuration.
Not to PAM, but more strictly, to PAMified sshd. Addition of it to other
PAMified programs works as expected.
> With that addition, in -CURRENT,
On 10-Jul-2002 Archie Cobbs wrote:
> John Baldwin writes:
>> It is the same problem. What we do is change callout_stop() to let you know if
>> it actually stopped the timeout or not. You then have to use your own locking
>> and synchronization in the timeout function and yourself to close the re
In the last episode (Jul 10), Don Lewis said:
> On 10 Jul, Alex Zepeda wrote> After the rude awakening that I was after all running
>current, I've
> > finally turned on the WITNESS related options for my kernel (and boy is it
> > wickedly unstable as of now).
>
> I haven't had any instability pr
Maybe this would be more interesting to
the mozilla guys but mozilla compiles on
2.95.3, so I think, the problem is related
to gcc-3.1
(cd /usr/ports/www/mozilla/work/mozilla/dist/bin; /usr/bin/env
LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regxpcom; echo
skin,install,select,classic/1.0 >> chrome
If I may suggest a fix that will probably make everyone happy...
The problem seems to be the addition of opieaccess to the PAM
configuration. With that addition, in -CURRENT, unless a user creates
/etc/opieaccess and adds explicit "permit" lines, plain text passwords will
not be accepted if OPIE
John Baldwin writes:
> It is the same problem. What we do is change callout_stop() to let you know if
> it actually stopped the timeout or not. You then have to use your own locking
> and synchronization in the timeout function and yourself to close the rest of
> the race.
OK, thanks.
What do y
On Wed, Jul 10, 2002 at 15:37:11 +0200, Dag-Erling Smorgrav wrote:
> making any sense at all. If your config file really disables all
> authentication methods except PasswordAuthentication, then OPIE
> *never* worked for you, because it *cannot* be implemented over the
> SSH PaswordAuthentication
On 10-Jul-2002 Archie Cobbs wrote:
> John Baldwin writes:
>> > code would be modified to fit this new behaviour, besides this, everywhere
>> > callout_stop() is used need to hold sched_lock and do a mi_switch() and
>> > modify td_flags is also unacceptable, this SMP race should be resolved in
On 09-Jul-2002 Julian Elischer wrote:
>
>
> On Wed, 10 Jul 2002, Bruce Evans wrote:
>> Can these flags be changed asynchronously? If so, then everything needs
>> to be handled by ast() anyway. userret() should only check for work that
>> needs doing in the usual case, and hopefully there is n
On Wed, Jul 10, 2002 at 15:37:11 +0200, Dag-Erling Smorgrav wrote:
> Andrey, I'd really suggest you back off and chill down. You're not
> making any sense at all. If your config file really disables all
> authentication methods except PasswordAuthentication, then OPIE
> *never* worked for you,
On Wed, Jul 10, 2002 at 15:37:11 +0200, Dag-Erling Smorgrav wrote:
> Andrey, I'd really suggest you back off and chill down. You're not
> making any sense at all. If your config file really disables all
> authentication methods except PasswordAuthentication, then OPIE
> *never* worked for you,
"Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> On Wed, Jul 10, 2002 at 15:02:43 +0200, Dag-Erling Smorgrav wrote:
> > But why disable keyboard-interactive authentication?
> There is nowhere documented that keyboard-interactive auth is required for
> PasswordAuthentication. It works without it
On Wed, Jul 10, 2002 at 15:02:43 +0200, Dag-Erling Smorgrav wrote:
>
> But why disable keyboard-interactive authentication?
There is nowhere documented that keyboard-interactive auth is required for
PasswordAuthentication. It works without it for ages. Sysadmins tends to
remove all unneded auth
"Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> On Wed, Jul 10, 2002 at 14:17:51 +0200, Dag-Erling Smorgrav wrote:
> > "Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> > > Why what? Sysadmin allows PasswordAuthentication only.
> > Why?
> Because he choose to not trust hosts keys which can be st
On Wed, Jul 10, 2002 at 02:38:51PM +0200, Marc Recht wrote:
> > I get the same message with xine on -STABLE each time i use it. Xine
> > is simply not very stable on FreeBSD, that's why I'm using mplayer now
> Oh. :-)
> > (which has it's own issues on -CURRENT)
> IIRC then MPlayer doesn't use thre
> I get the same message with xine on -STABLE each time i use it. Xine
> is simply not very stable on FreeBSD, that's why I'm using mplayer now
Oh. :-)
> (which has it's own issues on -CURRENT)
IIRC then MPlayer doesn't use threads. So, KSE shouldn't be an issue
there.
To Unsubscribe: send mail
> > Kernel and world are of today. (cvusup'd 10:00 CEST).
> >
> > $FreeBSD: src/lib/libc_r/uthread/uthread_priority_queue.c,v 1.8
> > 2002/05/24 04:32:28 deischen Exp $
>
> Do you know when it broke?
Sorry, I've built today the first time. But, Christian (previous post) said he
has the same prob
On Wed, Jul 10, 2002 at 14:17:51 +0200, Dag-Erling Smorgrav wrote:
> "Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> > Why what? Sysadmin allows PasswordAuthentication only.
>
> Why?
Because he choose to not trust hosts keys which can be stolen especially
when not password-protected. Because i
On 10 Jul 2002, Marc Recht wrote:
> While running (newly build) Xine I get following error:
>
> Fatal error '_waitq_remove: Not in queue' at line 350 in file
> /usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 0)
>
> Is this an outstanding KSE issue or a problem of the port itself?
>
"Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> Why what? Sysadmin allows PasswordAuthentication only.
Why?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
A box running this morning's -current compiled with DEBUG_VFS_LOCKS
coughed up this error part way through a "cvs update" of the ports tree.
VOP_GETVOBJECT: x is not locked but should be
The stack trace is:
getnewvnode() + 0x182
ffs_vget() + 0x73
ufs_lookup() + 0x10df
vfs_vnoperate() + 0x13
On Wed, Jul 10, 2002 at 12:12:56 +0200, Dag-Erling Smorgrav wrote:
> "Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> > Consider following setup: OPIE is active and allow Unix plaintext
> > passwords for local users only (i.e. common way of using OPIE). Then lets
> > disable all sshd auth methods
Alex Zepeda <[EMAIL PROTECTED]> writes:
> After the rude awakening that I was after all running current, I've
> finally turned on the WITNESS related options for my kernel
Congratulations in turning your -CURRENT box into a doorstop! ;)
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubs
On 9 Jul, John Baldwin wrote:
>
> On 09-Jul-2002 Don Lewis wrote:
>> I recently started seeing the warning message:
>>
>> /usr/src/sys/vm/uma_core.c:1332: could sleep with "kernel linker" locked
>> from /usr/src/sys/kern/kern_linker.c:1797
>>
>> at boot time on my -current box. It appears to
On Wed, Jul 10, 2002 at 12:10:50PM +0200, Marc Recht wrote:
> While running (newly build) Xine I get following error:
>
> Fatal error '_waitq_remove: Not in queue' at line 350 in file
> /usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 0)
>
> Is this an outstanding KSE issue or a pro
"Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> Consider following setup: OPIE is active and allow Unix plaintext
> passwords for local users only (i.e. common way of using OPIE). Then lets
> disable all sshd auth methods excepting "PasswordAuthentication yes" in
> sshd_config.
Why?
> 2nd bug
While running (newly build) Xine I get following error:
Fatal error '_waitq_remove: Not in queue' at line 350 in file
/usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 0)
Is this an outstanding KSE issue or a problem of the port itself?
Kernel and world are of today. (cvusup'd 10:00
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On 10 Jul, Alex Zepeda wrote> After the rude awakening that I was after all running
current, I've
> finally turned on the WITNESS related options for my kernel (and boy is it
> wickedly unstable as of now).
I haven't had any instability problems in a while on my UP box.
> Anyways.. is there any
- Original Message -
From: "M. Warner Losh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002 7:05 AM
Subject: Re: Netgear MA401 pccard support?
> In message: <046701c2279c$2878c4e0$0e81a8c0@gilgamesh>
> "Mauritz Sundell" <[EMA
Peter Wemm wrote:
> John Baldwin wrote:
> >
> > On 08-Jul-2002 Peter Wemm wrote:
> > > A few months ago, I had a bit of a disaster with some pmap optimizations.
> > > After committing, all hell broke loose. It was backed out completely.
> > >
> > > I finally found the problem (diff cleaned up t
On Tue, 9 Jul 2002, M. Warner Losh wrote:
> More of a dmesg would help debug this.
Sure, full "boot -v" and "pciconf -lv" follows. -CURRENT is from
right before KSE-III went in.
To my untrained eye, the pcib1:
device wi0 requested unsupported memory range 0x0-0xf41f
looks suspect. How
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.
There is absolutely no warranty
After the rude awakening that I was after all running current, I've
finally turned on the WITNESS related options for my kernel (and boy is it
wickedly unstable as of now). Anyways.. is there any sort of list of
known warnings? I'm seeing a few consistantly relating to "pcm0:play:0",
"pcm0", "i
77 matches
Mail list logo
