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
