Small fix for compile error with internat crypto code
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 code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
Following simple patch seems to cure the problem. Could anybody verify and
commit it?
--8-8-Cut here-8-8-
--- src/secure/lib/libcrypto/Makefile.inc.org Thu Apr 20 19:42:52 2000
+++ src/secure/lib/libcrypto/Makefile.inc Fri May 12 12:58:59 2000
@@ -30,10 +30,10 @@
echo "#endif" ) ${.TARGET}
openssl/opensslconf.h: ../libcrypto/opensslconf-${MACHINE_ARCH}.h
- @test -d openssl || mkdir -p openssl
+ -@mkdir -p openssl
cp ${.OODATE} ${.TARGET}
openssl/headers-copied:
- @test -d openssl || mkdir -p openssl
+ -@mkdir -p openssl
${INSTALL} ${COPY} -m 444 ${CRYPTO_HDRS} ${EXTRA_HDRS} openssl
@touch ${.TARGET}
--8-8-Cut here-8-8-
Thank you,
Haro
=--
_ _Munehiro (haro) Matsuda
-|- /_\ |_|_| Office of Business Planning Development, Kubota Corp.
/|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome
Chuo-ku Tokyo 103, Japan
Tel: +81-3-3245-3318 Fax: +81-3-3245-3315
Email: [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Small fix for compile error with internat crypto code
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 needed as `mkdir -p' will not return an error condition. - @test -d openssl || mkdir -p openssl + -@mkdir -p openssl Same here. Bruce Evans just told me the other day that make(1) can have issues with shell "" and "||". Guess you hit one of the cases it can fail with -j. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unknown: PNP...
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 up being probed twice at boot time. 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. 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 back, with no way (that I saw) to turn it off. Other than the annoying messages at boot, it never caused a problem that I saw, so I didn't really worry about it. If we aren't supposed to have "at isa? port ..." stuff in our config files, then someone should update GENERIC to reflect that. -Mike -- Mike Pritchard [EMAIL PROTECTED] or [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unknown: PNP...
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 back, with no way (that I saw) to turn it off. You can turn it off in the loader, I have to on my laptop to get it to work proberly... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small fix for compile error with internat crypto code
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 May 2000, David O'Brien wrote: | 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 needed as `mkdir -p' will not return an error condition. | | - @test -d openssl || mkdir -p openssl | + -@mkdir -p openssl | | Same here. Bruce Evans just told me the other day that make(1) can have | issues with shell "" and "||". Guess you hit one of the cases it can | fail with -j. | | -- Eugene M. Kim [EMAIL PROTECTED] "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: One more question (different now)
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 one. "Not yet" is what comp.std.c says, but any time soon. It is excepted to be available as a cheap PDF like the C++ standard. [info could be out of date, didn't check news for weeks] Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unknown: PNP...
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 became default some time back, with no way (that I saw) to turn it off. You can turn it off in the loader, I have to on my laptop to get it to work proberly... Would that be in /boot/loader.conf? I've tried PNPBIOS="NO" in /boot/loader.conf, and I'm still getting the messages. [snip]dmesg plip0: PLIP network interface on ppbus0 unknown: PNP0401 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources /dmesg - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unknown: PNP...
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 need to do this is actually a bug.) If we aren't supposed to have "at isa? port ..." stuff in our config files, then someone should update GENERIC to reflect that. We need that stuff in order to cope with older hardware that doesn't implement PNPBIOS (or PNPanything, for that matter). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can we please have a current that compiles?
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 views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true."Robert Wilensky, University of California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small fix for compile error with internat crypto code
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 freebsd-current" in the body of the message
Re: Small fix for compile error with internat crypto code
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 right. But then things still remain strange... Isn't this: test -d openssl || mkdir -p openssl supposed to never give the `mkdir: openssl: File exists' error? So I guess the real cause of that bug is not a race condition between two mkdir -p commands. Haven't seen the error recently so can't exactly tell, but it looks more like there is already an `openssl' that isn't a directory. Eugene -- Eugene M. Kim [EMAIL PROTECTED] "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: loader and libstand caution required.
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 fault. I am not sure if the x86 loader will be affected by a mismatch, but I would not like to bet on it. Be safe and make sure it is not linked against a stale libstand. :-) Cheers, -Peter --- Forwarded Message Date:Fri, 12 May 2000 15:45:16 -0700 From:Peter Wemm [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/boot/alpha/common Makefile.common peter 2000/05/12 15:45:16 PDT Modified files: sys/boot/alpha/common Makefile.common Log: Reactivate the FICL hooks to make it be compiled in, but also initialize FICL. bootforth is now live on the Alpha! **BEWARE** - you *MUST* build and install a current libstand or you will most likely get zfree() panics at loader startup. We should now be able to set up the loader.conf stuff on the Alpha too. Revision ChangesPath 1.7 +9 -9 src/sys/boot/alpha/common/Makefile.common --- End of Forwarded Message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: loader and libstand caution required.
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 issue of the end of code. Adding/removing code would make it fault. I am not sure if the x86 loader will be affected by a mismatch, but I would not like to bet on it. Be safe and make sure it is not linked against a stale libstand. :-) Cheers, -Peter --- Forwarded Message Date:Fri, 12 May 2000 15:45:16 -0700 From:Peter Wemm [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/boot/alpha/common Makefile.common peter 2000/05/12 15:45:16 PDT Modified files: sys/boot/alpha/common Makefile.common Log: Reactivate the FICL hooks to make it be compiled in, but also initialize FICL. bootforth is now live on the Alpha! **BEWARE** - you *MUST* build and install a current libstand or you will most likely get zfree() panics at loader startup. We should now be able to set up the loader.conf stuff on the Alpha too. Revision ChangesPath 1.7 +9 -9 src/sys/boot/alpha/common/Makefile.common --- End of Forwarded Message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
breakage in mtree?
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 -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/misc.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/mtree.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/spec.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/mtree/verify.c cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/i386/usr/include -o mtree compare.o crc.o create.o misc.o mtree.o spec.o verify.o setflags.o -lmd create.o: In function `cwalk': create.o(.text+0xcf): undefined reference to `check_excludes' mtree.o: In function `main': mtree.o(.text+0x1c): undefined reference to `init_excludes' mtree.o(.text+0x1e6): undefined reference to `read_excludes_file' verify.o: In function `vwalk': verify.o(.text+0xa7): undefined reference to `check_excludes' *** Error code 1 Stop in /usr/src/usr.sbin/mtree. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. making clean and remaking in usr.sbin/mtree is of no help, mailing list archives have no mention of this. This is on an existing 4.0-2214 system, kernel is 5.0-C as of 2 days ago. -- Marius Strom [EMAIL PROTECTED] Professional Geek/Unix System Administrator Alpha1 Internet http://www.alpha1.net http://www.marius.org/marius.pgp 0x42C74CBA Quidquid Latine Dictum Sit, Profundum Viditur. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can we please have a current that compiles?
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 8^), but none of them related to FreeBSD. Anyway, 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. === usr.bin/more sed -e 's/\\//g' -e 's/\"/\\\"/g' -e 's/$/\\n\\/' /usr/src/usr.bin/more/default.morerc defrc.h rm -f .depend mkdep -f .depend -a-I/usr/src/usr.bin/more -I/usr/obj/usr/src/usr.bin/more -DTERMIOS -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/more/ch.c /usr/src/usr.bin/more/command.c /usr/src/usr.bin/more/help.c /usr/src/usr.bin/more/input.c /usr/src/usr.bin/more/line.c /usr/src/usr.bin/more/linenum.c /usr/src/usr.bin/more/macro.c main.c /usr/src/usr.bin/more/ncommand.c /usr/src/usr.bin/more/option.c /usr/src/usr.bin/more/os.c /usr/src/usr.bin/more/output.c /usr/src/usr.bin/more/position.c /usr/src/usr.bin/more/prim.c /usr/src/usr.bin/more/screen.c /usr/src/usr.bin/more/signal.c /usr/src/usr.bin/more/tags.c /usr/src/usr.bin/more/ttyin.c cc: main.c: No such file or directory mkdep: compile failed *** Error code 1 Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true."Robert Wilensky, University of California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can we please have a current that compiles?
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 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. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can we please have a current that compiles?
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 directory mkdep: compile failed *** Error code 1 Oh, come on -- this is the New FreeBSD - "Designed for the die-hard hacker, we remove random parts of the system so you can enjoy the challenge of figuring out what the missing functions did!" sorry, couldn't help myself mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
OpenSSH (last chance!)
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. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
