Re: Tonight make world failed at isdnmonitor...
On Mon, 10 May 1999, Steve Kargl wrote: I sent a patch for this about 8 hours ago. No one seems to read -current. well it still is broken and i must of missed that patch somewhere in my mail, 3:58 a.m east coast time tuesday 11 rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Tonight make world failed at isdnmonitor...
On Tue, 11 May 1999, Hellmuth Michaelis wrote: I sent a patch for this about 8 hours ago. No one seems to read -current. well it still is broken and i must of missed that patch somewhere in my mail, 3:58 a.m east coast time tuesday 11 just read mail, tested Steves fix, committed. 10:23 am central european summer time tuesday 11 The world is round and needs 24 hours to rotate once. ;-) hellmuth O.k. I admit it i've been an ass over changing the names of 2 variables in what was it 8 lines of code. rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Make World Fails - minor and major conflict
On Tue, 11 May 1999, Thomas Dean wrote: I am running -current SMP as of last week. I cvsup'ed last night and started a 'Make -j12 world'. cvsup again that should fix it. if it doesnt add my or anything else for that matter, to all occurances of the variable minor and major in that file. Rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SPAM
On Mon, 10 May 1999, Chuck Robey wrote: On Mon, 10 May 1999, Thomas T. Veldhouse wrote: A spammer could simply become a list member and then SPAM. They won't care if they are removed once they have perpetrated their abuse. The could, but most wouldn't, wouldn't even know how. It wouldn't be a sure cure, but it would sure help. Don't do it on newbies type lists, like -questions or -newbies, even multimedia gets a lot of newbies. Current and committers would be good candidates. So you got some spam from the mailing list, so you generate a few hundred more emails about the spam, i'm being spammed by anti spam email :) Rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Tonight make world failed at isdnmonitor...
On Tue, 11 May 1999, oZZ!!! wrote:
Hello!
Makeworld failed at isdnmonitor:
=== usr.sbin/i4b/isdnmonitor
cc -Os -pipe -mpentium -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/usr.sbin/i4b/isdn
monitor/main.c
/usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as
different kind of symbol
/usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of
`major'
/usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as
different kind of symbol
/usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of
`minor'
{standard input}: Assembler messages:
{standard input}:1510: Fatal error: Symbol minor already defined.
*** Error code 1
tell phk thanks this ones related to his changes to types.h as well
Rob
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: does login.conf limitations work ?
On Sat, 24 Apr 1999, Brian Feldman wrote: On Sat, 24 Apr 1999, Stephane Legrand wrote: Andrzej Bialecki writes: On Fri, 23 Apr 1999, Luigi Rizzo wrote: Hi, i was wondering if the limitations that are supposed to be enforced via the login.conf mechanism do really work... In particular, i have tried (on 3.1 something, but don't think that current is much different in this respect) to enforce the daily etc. login times but the system seems to ignore them. I think /etc/login.conf is properly parsed, because if i assign a user to a class that is not defined in login.conf i get complaints, but other than that i am unable to limit login time... Any hints ? That's also my impression. I glipmsed the whole source tree and I couldn't find any place where the limits are enforced. BTW. what entity should enforce login time limits? Kernel? Some user-space daemon? To report a login.conf success, i've used on a 2.2.8 system the cputime ressource limit. I set it to zero and that worked very well. So may be only some limits are implemented ? If you'd like to see where the ones which are implemented are implemented, look at the process context-switch routines in the kernel. Not having checked, but guessing, I bet login reads login.conf as a db and uses the values to set rlimits, which is where they would be set. Stephane Legrand. -- stephane.legr...@wanadoo.fr : http://perso.wanadoo.fr/stephane.legrand/ FreeBSD Francophone : http://www.freebsd-fr.org/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Some of it works, and some doesn't some is implemented in login, other parts are in init.. rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATTENTION PLEASE: g77 in base system.
On Fri, 9 Apr 1999 p...@phoenix.volant.org wrote:
I always thought the criteria for inclusion of things into the base
system was:
1. Needed for 'make world';
2. Needed to get a basic functioning server up and running;
3. Something usefull only within FreeBSD (like the kernel ;), or
4. Can't be effectively built outside of /usr/src.
If {g77|f77} can be built as a port, using the system EGCS, then to
port's it goes. Otherwise why don't we include the Top 20 ports, or
maybe the Top 25, or...
The criteria for adding something to the base system is different
than the criteria for removing something from it. In both cases,
it requires compelling reasons to change the status quo.
Replacing an existing component is somewhat easier, particularly
if backwards compatability is retained. I may be mistaken, but I
believe the current discussion is whether or not to replace f77
with g77.
Didn't we just have this discussion a few months ago???
just put it in the tree already ;)
rob
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: ATTENTION PLEASE: g77 in base system.
On Sat, 10 Apr 1999, Rod Taylor wrote: Right or wrong, you forgot: 5. BSD tradition. Case 5 justifies Fortran. Me, I'd rather have Fortran as a port. I'd even grudgingly accept fortune as a port, as a matter of fact. Our base system is bloated. While a lot of widely used programs are only available through ports, a lot of obscure and obsolete stuff remains on our tree. They are there because of 5. As long as 5 exists, Fortran belongs in the tree. If we ever get rid of 5, then it's time to get the knife to our tree... Or the axe, if the vikings decide to have the first cut. :-) Whelp... I vote to break tradition. Hack away...The installer takes care of alot of stuff like ports installs. Perhaps different standard setups could be configured as ports. Ie. 'bloated setup' would require all the ports which are currently included. 'Server setup' port wouldn't have any Client stuff. 'Desktop' could install a 'nicer' windomanager (kde? gnome?) for teh user, and be pre-setup to start xdm, etc. The installer can currently install packages, so reworking those 'system install options' to fit simpler naming convention than 'Kernel Hacker, X user, X+ source, etc.' may be appropriate. I know.. lots of talk and no action. Oh well... my thoughts :) well geeze Xwindows isnt in the base source tree anymore, what more do ya want ;) rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATTENTION PLEASE: g77 in base system.
On Sat, 10 Apr 1999, Chuck Robey wrote: On Fri, 9 Apr 1999, eagle wrote: Whelp... I vote to break tradition. Hack away...The installer takes care of alot of stuff like ports installs. Perhaps different standard setups could be configured as ports. Ie. 'bloated setup' would require all the ports which are currently included. 'Server setup' port wouldn't have any Client stuff. 'Desktop' could install a 'nicer' windomanager (kde? gnome?) for teh user, and be pre-setup to start xdm, etc. The installer can currently install packages, so reworking those 'system install options' to fit simpler naming convention than 'Kernel Hacker, X user, X+ source, etc.' may be appropriate. I know.. lots of talk and no action. Oh well... my thoughts :) well geeze Xwindows isnt in the base source tree anymore, what more do ya want ;) Anymore? It's never been there to begin with. perhaps i'm wrong but i woulda swore it was in /usr/src/contrib in 4.4lite2 at least rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: something's wrong with the in the last 24 hours with the sources
On Wed, 7 Apr 1999, Tomer Weller wrote: doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. === cc_int make : dont know how to make insn-attrtab.c. Stop dont use make -j anything it is currently broken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS optimizations
On Mon, 5 Apr 1999, Alex Zepeda wrote: On Mon, 5 Apr 1999, Matthew Dillon wrote: There is nothing beyond -O2. Well, there's -O3, which tries to inline static functions, but that typically isn't beneficial because it really bloats up the code and subroutine calls on intel cpus are very fast. Really? The pgcc web page (goof.com/pcg) lead me to believe that there were a few more optimizations turned on by -O5 -O6.. pgcc isn't the same as egcs the current -mpentiumpro and -mpentiumarch stuff were taken from pgcc and ported back to egcs but i believe that pgcc has gone way beyond what it was when that happened. rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS breaks what(1)
On Tue, 6 Apr 1999, Bruce Evans wrote: Alternately, we could jimmy around with the current hack, and prefix it with 4 NULs, and see what happened. Sorry, I haven't tested this idea, as I've not yet made the EGCS jump. egcs aligns long (= about 28 bytes) strings to 32-byte boundaries. This adds up to 27 NULs to sccsid[] depending on the alignment of sccsidp[]. Aligning long strings to 32-byte boundaries is a pessimisation in kernels (because it makes poor locality poorer), especially on 486's where the cache line size is 16. Bruce not aligning data is extremely expensive on PII's rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make -jn ?
On Mon, 5 Apr 1999, Bob Bishop wrote: World builds OK here now, kernel, bootblocks and all. Good job! Is `make -jn' safe yet? Could turn these test builds round a lot faster :-) I'm running a test build at -j3 now following the reccomended ncpus +1 formula everything looks great so far. if it fails i'll let you know rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make -jn ?
On Mon, 5 Apr 1999, eagle wrote: On Mon, 5 Apr 1999, Bob Bishop wrote: World builds OK here now, kernel, bootblocks and all. Good job! Is `make -jn' safe yet? Could turn these test builds round a lot faster :-) I'm running a test build at -j3 now following the reccomended ncpus +1 formula everything looks great so far. if it fails i'll let you know rob build completed successfully will experment some more rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make -jn ?
On Mon, 5 Apr 1999, eagle wrote: On Mon, 5 Apr 1999, Bob Bishop wrote: World builds OK here now, kernel, bootblocks and all. Good job! Is `make -jn' safe yet? Could turn these test builds round a lot faster :-) I'm running a test build at -j3 now following the reccomended ncpus +1 formula everything looks great so far. if it fails i'll let you know build completed successfully will experment some more make -j anything greater than 3 fails rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
MAKEWORLD fails at texinfo
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I../intl -DLOCALEDIR=\/usr/local/share/locale\ -g -O2 -c makeinfo.c makeinfo.c: In function `xrealloc': makeinfo.c:1205: parse error before `void' makeinfo.c:1209: `exit_value' undeclared (first use this function) makeinfo.c:1209: (Each undeclared identifier is reported only once makeinfo.c:1209: for each function it appears in.) makeinfo.c:1252: parse error before `typedef' makeinfo.c: At top level: makeinfo.c:1254: warning: data definition has no type or storage class makeinfo.c:1259: parse error before `*' makeinfo.c: In function `reverse_list': makeinfo.c:1261: parse error before `*' makeinfo.c:1261: declaration for parameter `GENERIC_LIST' but no such parameter makeinfo.c:1263: syntax error before `*' makeinfo.c:1264: syntax error before `*' makeinfo.c:1268: `next' undeclared (first use this function) makeinfo.c:1268: invalid type argument of `-' makeinfo.c:1269: invalid type argument of `-' makeinfo.c:1269: `prev' undeclared (first use this function) *** Error code 1 this was cvsupped at 7:15 a.m on the 15th using the standard-supfile as found in /usr/share/examples RG To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
