Small fix for compile error with internat crypto code

2000-05-12 Thread Munehiro Matsuda
Hello all, When run 'make -j4 buildworld' with internat crypto code installed, I get following error: === librsausa cp /usr/src/secure/lib/librsausa/../libcrypto/opensslconf-i386.h openssl/opensslconf.h mkdir: openssl: File exists *** Error code 1 1 error *** Error code 2 1 error *** Error

Re: Small fix for compile error with internat crypto code

2000-05-12 Thread David O'Brien
On Fri, May 12, 2000 at 04:41:09PM +0900, Munehiro Matsuda wrote: When run 'make -j4 buildworld' with internat crypto code installed, I get following error: mkdir: openssl: File exists *** Error code 1 - @test -d openssl || mkdir -p openssl + -@mkdir -p openssl The "-" is not

Re: unknown: PNP...

2000-05-12 Thread Mike Pritchard
On Wed, May 10, 2000 at 10:16:17AM -0400, Garrett Wollman wrote: On Wed, 10 May 2000 11:57:21 +0800, Trent Nelson [EMAIL PROTECTED] said: Something else I've noticed in the mean time is that PnP devices like my printer - that are also on buses that are probed for PnP devices - end

Re: unknown: PNP...

2000-05-12 Thread Soren Schmidt
It seems Mike Pritchard wrote: I did notice that I started getting all of the "unknown: PNPx" messages after the PNPBIOS option became default. On the machine I'm typing on this on, I used to see those messages if I defined PNPBIOS in my config file. PNPBIOS became default some time

Re: Small fix for compile error with internat crypto code

2000-05-12 Thread Eugene M. Kim
It looks like a race condition. -@mkdir -p openssl is a good workaround I guess, although it could be fine if we had a flag to mkdir(1) that makes it just succeed when there's already a directory of the same name. Just my 2 wons (1 KRW ~= .0084 USD as of this writing :-p), Eugene On Fri, 12

Re: One more question (different now)

2000-05-12 Thread Martin Cracauer
In [EMAIL PROTECTED], Sheldon Hearn wrote: On Thu, 11 May 2000 03:58:57 +0200, Bernd Luevelsmeyer wrote: The Standard itself is a book and can be bought as such in bookstores. Can you give us details? Do I just hunt Amazon.com for "C99", or does it have a proper title? I need this

Re: unknown: PNP...

2000-05-12 Thread Donn Miller
Soren Schmidt wrote: It seems Mike Pritchard wrote: I did notice that I started getting all of the "unknown: PNPx" messages after the PNPBIOS option became default. On the machine I'm typing on this on, I used to see those messages if I defined PNPBIOS in my config file. PNPBIOS

Re: unknown: PNP...

2000-05-12 Thread Garrett Wollman
On Fri, 12 May 2000 05:08:10 -0500, Mike Pritchard [EMAIL PROTECTED] said: [I wrote:] Delete the `at isa? port blah' cruft from your config file. For what devices? The only devices I have those on match what is in GENERIC. For those devices which are double-probed. (The fact that you

Can we please have a current that compiles?

2000-05-12 Thread Stephen Hocking
For the past few days, current has not compiled, owing to problems (in no particular order) with more, vinum and various INET options in the GENERIC kernel. Can people please check things before they commit them? I like a working compile at least *once* a week. Stephen -- The

Re: Small fix for compile error with internat crypto code

2000-05-12 Thread David O'Brien
On Fri, May 12, 2000 at 06:34:08AM -0700, Eugene M. Kim wrote: I guess, although it could be fine if we had a flag to mkdir(1) that makes it just succeed when there's already a directory of the same name. Yes, that is "-p". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe

Re: Small fix for compile error with internat crypto code

2000-05-12 Thread Eugene M. Kim
On Fri, 12 May 2000, David O'Brien wrote: | On Fri, May 12, 2000 at 06:34:08AM -0700, Eugene M. Kim wrote: | I guess, although it could be fine if we had a flag to mkdir(1) that | makes it just succeed when there's already a directory of the same name. | | Yes, that is "-p". | Oh yes you're

HEADS UP: loader and libstand caution required.

2000-05-12 Thread Peter Wemm
Please be sure that you build and install libstand before building a loader! (or use buildworld, that should work) FICL is now active on the Alpha, and actually seems to work. The Alpha problems have been solved - it was an alignment issue of the end of code. Adding/removing code would make it

Re: HEADS UP: loader and libstand caution required.

2000-05-12 Thread Nate Williams
Please be sure that you build and install libstand before building a loader! (or use buildworld, that should work) Good job tracking this one down Peter Nate FICL is now active on the Alpha, and actually seems to work. The Alpha problems have been solved - it was an alignment

breakage in mtree?

2000-05-12 Thread Marius Strom
cvsup as of ~20 minutes ago, during a buildworld: === usr.sbin/mtree cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/compare.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/create.c cc -O

Re: Can we please have a current that compiles?

2000-05-12 Thread Stephen Hocking
This is the first I've heard of a problem in Vinum. Can people please check things before they commit them? I like a working compile at least *once* a week. I'm wondering if you haven't had some other problem. I haven't heard anybody else with problems. I have a number of problems

Re: Can we please have a current that compiles?

2000-05-12 Thread Greg Lehey
On Friday, 12 May 2000 at 23:35:09 +0800, Stephen Hocking wrote: For the past few days, current has not compiled, owing to problems (in no particular order) with more, vinum and various INET options in the GENERIC kernel. This is the first I've heard of a problem in Vinum. Can people please

Re: Can we please have a current that compiles?

2000-05-12 Thread Mike Nowlin
I'd just seen a series of bad commits whose corrections weren't caught by the frequency of my cvs updates I guees. Vinum is compiling now, and kernels with IPSEC and INETV6 now link, it's just that last night's problems with more got me a little ticked off. cc: main.c: No such file or

OpenSSH (last chance!)

2000-05-12 Thread Kris Kennaway
I've had several positive reports about the new OpenSSH version, so I'm intending to commit the changes tomorrow night. This is your last chance to tell me it's broken! http://www.freebsd.org/~kris/ssh2.tgz Kris In God we Trust -- all others must submit an X.509 certificate. --