Re: Changes to libfetch in 5.0 break proxy support?
Brian J. McGovern [EMAIL PROTECTED] writes: Anyone have any ideas if something has broken, or whether its pilot error? Please show the output of fetch -vvv some-url-that-doesn't-work DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Unresolved reference compiling Objective-C ??
Jonathon McKitrick [EMAIL PROTECTED] writes: On Sun, Nov 10, 2002 at 03:41:38PM +0100, Dag-Erling Smorgrav wrote: | In other words: always specify libraries at the end of the compiler or | linker command line. So why allow putting them at the beginning, where mistakes like this can happen? Is that ever useful? Would it be wrong to 'assume' all libraries be linked after all object files? It is conceivable that a high-level application framework would define main and require the developer to define some other entry point which main would then call. In that case you'd have to put the library that contains main first. The point is that there is no real difference between foo.c, foo.s, foo.o, foo.a, -lfoo etc., they're just different ways of telling the compiler where to find the objects your program consists of (in the first two cases it has to create the object itself from source code). The only thing special about -lfoo is that it tells the compiler to look for libfoo.a or libfoo.so in the linker path and use the first one it finds. You could use /usr/local/lib/libfoo.so instead of -lfoo and it would work just as well. Also, if some symbols your program needs are defined in more than one of the objects listed on the linker command line, the ordering becomes very important because it determines which version of the symbol is used (unless one is strong and all the others are weak, in which case the strong version is used) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: No buffer space available
Eric Anderson [EMAIL PROTECTED] writes: 131/32768/32768 mbuf clusters in use (current/peak/max) You ran out of mbuf clusters at some point. How can I fix this? Add kern.ipc.nmbclusters=65536 to /boot/loader.conf and reboot. BTW, -chat is not the appropriate forum for this kind of question. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: No buffer space available
Eric Anderson [EMAIL PROTECTED] writes: Dag-Erling Smorgrav wrote: Eric Anderson [EMAIL PROTECTED] writes: 131/32768/32768 mbuf clusters in use (current/peak/max) You ran out of mbuf clusters at some point. What part of the netstat -m indicated this? Well, duh. The part I quoted. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: No buffer space available
Eric Anderson [EMAIL PROTECTED] writes: Sorry. I'm a dumbass. We all have our moments :) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: RELENG_4_6
Bruce A. Mah [EMAIL PROTECTED] writes: From what I can tell (my local respository, commit logs, and cvsweb) it looks like src/crypto/openssh/auth-skey.c didn't get committed to the RELENG_4_6 branch. Thanks. That's where the first commit died, and apparently I off-by-one'd when I restarted it. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
