World borken :((
To whom it may concern In file included from /shares/UF/obj/usr/src/i386/usr/include/readline/readline. h:38, from /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb. 291/gdb/top.c:39: /shares/UF/obj/usr/src/i386/usr/include/readline/tilde.h:80: conflicting types f or `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/defs.h:510: pr evious declaration of `tilde_expand' In file included from /shares/UF/obj/usr/src/i386/usr/include/readline/readline. h:38, from /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb. 291/gdb/tracepoint.c:36: /shares/UF/obj/usr/src/i386/usr/include/readline/tilde.h:80: conflicting types f or `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/defs.h:510: pr evious declaration of `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In func tion `init_main': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:3467: wa rning: assignment from incompatible pointer type *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World borken :((
On Wed, Apr 11, 2001 at 17:41:09 +0300, Maxim Sobolev wrote: GDB maintainer already notified with proposed patch. To whom it may concern In file included from /shares/UF/obj/usr/src/i386/usr/include/readline/readline. h:38, from /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb. 291/gdb/top.c:39: /shares/UF/obj/usr/src/i386/usr/include/readline/tilde.h:80: conflicting types f or `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/defs.h:510: pr evious declaration of `tilde_expand' In file included from /shares/UF/obj/usr/src/i386/usr/include/readline/readline. h:38, from /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb. 291/gdb/tracepoint.c:36: /shares/UF/obj/usr/src/i386/usr/include/readline/tilde.h:80: conflicting types f or `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/defs.h:510: pr evious declaration of `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In func tion `init_main': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:3467: wa rning: assignment from incompatible pointer type *** Error code 1 -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World borken :((
"Andrey A. Chernov" wrote: On Wed, Apr 11, 2001 at 17:41:09 +0300, Maxim Sobolev wrote: GDB maintainer already notified with proposed patch. Well, if you know about this problem why you did not wait for his reply before proceeding with importing? I hardly can see any reason to rush with this and leave the tree in the broken state for the unindentified period of time. At least you could send a HEADS-UP to the appropriate mailing list, thus saving my and possibly others' time. -Maxim To whom it may concern In file included from /shares/UF/obj/usr/src/i386/usr/include/readline/readline. h:38, from /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb. 291/gdb/top.c:39: /shares/UF/obj/usr/src/i386/usr/include/readline/tilde.h:80: conflicting types f or `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/defs.h:510: pr evious declaration of `tilde_expand' In file included from /shares/UF/obj/usr/src/i386/usr/include/readline/readline. h:38, from /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb. 291/gdb/tracepoint.c:36: /shares/UF/obj/usr/src/i386/usr/include/readline/tilde.h:80: conflicting types f or `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/defs.h:510: pr evious declaration of `tilde_expand' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In func tion `init_main': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:3467: wa rning: assignment from incompatible pointer type *** Error code 1 -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World borken :((
On Wed, Apr 11, 2001 at 06:43:52PM +0400, Andrey A. Chernov wrote: On Wed, Apr 11, 2001 at 17:41:09 +0300, Maxim Sobolev wrote: GDB maintainer already notified with proposed patch. Awake now. Patch commited. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World borken :((
On Wed, Apr 11, 2001 at 19:09:55 +0300, Maxim Sobolev wrote: "Andrey A. Chernov" wrote: On Wed, Apr 11, 2001 at 17:41:09 +0300, Maxim Sobolev wrote: GDB maintainer already notified with proposed patch. Well, if you know about this problem why you did not wait for his reply before proceeding with importing? First of all, David ask me for readline importing, what I did was an response. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World borken :((
"Andrey A. Chernov" wrote: On Wed, Apr 11, 2001 at 19:09:55 +0300, Maxim Sobolev wrote: "Andrey A. Chernov" wrote: On Wed, Apr 11, 2001 at 17:41:09 +0300, Maxim Sobolev wrote: GDB maintainer already notified with proposed patch. Well, if you know about this problem why you did not wait for his reply before proceeding with importing? First of all, David ask me for readline importing, what I did was an response. I see, but still think that a short HEADS-UP would be a good way to show your respect to other developers. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World borken :((
On Wed, Apr 11, 2001 at 08:34:37PM +0400, Andrey A. Chernov wrote: Well, if you know about this problem why you did not wait for his reply before proceeding with importing? First of all, David ask me for readline importing, what I did was an response. But my request wasn't a request to break world. W/o doing the import myself (which typically means doing it in a local repo to test first), I could not have known the upgrade would break world. ;-) -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Who is maintainer of kerberos/heimdall/sendmail?
Who is the maintainer of this code?
They appear to use SOMAXCONN, incorrectly.
The value of SOMAXCONN is not valis; the valid limit is only
obtainable from sysctl (kern.ipc.somaxconn).
Here is a function which does the right thing:
int
getsomaxconn( void)
{
char*name = "kern.ipc.somaxconn";
int somaxconn;
size_t size = sizeof(somaxconn);
if( sysctlbyname(name, somaxconn,size, NULL, 0))
somaxconn = SOMAXCONN;
return( somaxconn);
}
If someone wants something prettier (e.g. sysctl instead of
sysctlbyname), they are welcome to write it.
Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
world (still) having trouble (after gdb.291/gdb/defs.h)
OK; I ran into the earlier problem with tilde_expand, saw the commit, hand-patched my copy, started the build again. In "stage 4: building everything...", it got well past that point, but blew up in usr.bin/kdump: === usr.bin/jot cc -O -pipe -Wall -W -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/jot/jot.c cc -O -pipe -Wall -W -I/usr/obj/usr/src/i386/usr/include -o jot jot.o gzip -cn /usr/src/usr.bin/jot/jot.1 jot.1.gz === usr.bin/kdump cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:99: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the location of the previous definition In file included from ioctl.c:78: /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:65: `SMB_MAXSRVNAMELEN' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:65: size of array `ioc_srvname' has non-integer type /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:70: `SMB_MAXUSERNAMELEN' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:70: size of array `ioc_user' has non-integer type /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:71: `SMB_MAXUSERNAMELEN' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:71: size of array `ioc_workgroup' has non-integer type /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:72: `SMB_MAXPASSWORDLEN' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:72: size of array `ioc_password' has non-integer type /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:82: `SMB_MAXSHARENAMELEN' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:82: size of array `ioc_share' has non-integer type /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:83: `SMB_MAXPASSWORDLEN' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:83: size of array `ioc_password' has non-integer type /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:133: syntax error before `smbfh' *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # Script done on Wed Apr 11 04:16:16 2001 Heads up; clues welcome. Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SOMAXCONN -- not tunable?
Here are patches to make SOMAXCONN tunable from the config files. Right now, it's not possible to override SOMAXCONN. I would like to see these merged into 4.3? I stuffed the option into opt_inet.h, since it is the only opt_*.h file already included in the only place the value is used in the kernel (kern/uipc_socket.c). Obviously, user space programs should use kern.ipc.somaxconn to retrieve the current value, rather than relying on the header. What is the feeling about #ifdef _KERNEL and providing sysctl inlines, so that user space programs "just work" for everything but global (static) initializers? Index: socket.h === RCS file: /home/cvs/FreeBSD/sys/sys/socket.h,v retrieving revision 1.1.1.1 diff -r1.1.1.1 socket.h 303a304 #ifndef SOMAXCONN 304a306 #endif Index: options === RCS file: /home/cvs/FreeBSD/sys/conf/options,v retrieving revision 1.5 diff -r1.5 options 262a263 SOMAXCONN opt_inet.h Terry Lambert [EMAIL PROTECTED] --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
build failure for today
=== usr.bin/kdump cc -O -pipe -march=pentiumpro -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr. bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/ kdump.c cc -O -pipe -march=pentiumpro -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr. bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:99: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redef ined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the loc ation of the previous definition In file included from ioctl.c:78: /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:65: `SMB_MAXSRVNAMELEN' undec lared here (not in a function) /usr/obj/usr/src/i386/usr/include/netsmb/smb_dev.h:65: size of array `ioc_srvnam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world (still) having trouble (after gdb.291/gdb/defs.h)
On Wed, 11 Apr 2001, David Wolfskill wrote: In "stage 4: building everything...", it got well past that point, but blew up in usr.bin/kdump: Sorry, delta was committed to smb_dev.h. It should be ok now. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world (still) having trouble (after gdb.291/gdb/defs.h)
Date: Thu, 12 Apr 2001 04:40:03 +0700 (ALMST) From: Boris Popov [EMAIL PROTECTED] In "stage 4: building everything...", it got well past that point, but blew up in usr.bin/kdump: Sorry, delta was committed to smb_dev.h. It should be ok now. Yup -- built; I'm running: FreeBSD m133.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #26: Wed Apr 11 09:36:48 PDT 2001 root@:/common/C/obj/usr/src/sys/LAPTOP_30W i386 (in multi-user mode) right now. Thanks! That said, while I was trying to figure out what had gone wrong, I ended up chasing something that was "merely" a warning, but loks to me as if it has some unpleasant potential: the dual (conflicting) definitions of MDF_ACTIVE, thus: sys/pccard/cardinfo.h:81:#define MDF_ACTIVE 0x40/* Context active (read-only) */ and sys/sys/memrange.h:18:#define MDF_ACTIVE (127) /* currently active */ The notion of the same program (kdump, in this case) actually using both include files would seem to be a cause for some concern. Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
