Build environment updates

This pull contains commits to fix the OS X build and allow GitMake test to pass.
On Thu, Jul 10, 2014 at 3:42 PM, Ben Laurie <notifications@github.com> wrote:
>
> In util/pl/unix.pl:
>
> > @@ -226,12 +228,6 @@ sub fixdeps
> >  sub fixrules
> >    {
> >    my ($str) = @_;
> > -
> > -  # Compatible with -j...
> > -  $str =~ s/^(\s+@?)/$1cd \$(TEST_D) && /;
> > -  return $str;
>
> On 10 July 2014 19:38, Mike Bland <notifications@github.com> wrote: In util/pl/unix.pl: > @@ -226,12 +228,6 @@ sub fixdeps > sub fixrules > { > my ($str) = @_; > - > - # Compatible with -j... > - $str =~ s/^(\s+@?)/$1cd \$(TEST_D) && /; > - return $str; I said it worked because originally I wasn't using '-j', so it was working for me. When I used '-j 20', I didn't see the "cd: out.build: No such file or directory" errors and the shell return code was 0.

> That's what's puzzling me - I get you could miss the text-only errors, but I got an actual make-stopping error, and I'm wondering why you didn't?

There is other GitMake weirdness going on that I'm investigating,
which I was going to raise in a separate thread later, but since it
seems to be germane here...

While beginning my investigation into your earlier report this
morning, I noticed that in a brand new working directory identical to
the latest OpenSSL master branch, if I do a 'GitMake -j 1',
test_verify fails. If I then do a regular make, the subsequent
'GitMake -j 1 test_verify' will pass.

It seems something similar is happening with 'GitMake -j 1 test' in
general. I use git-new-workdir to have a private dir per branch. In my
original FreeBSD 9.1 working dir for this 'build' branch, running
'GitMake -j 1 test' even now (after re-introducing the obsolete
change), I'll see the 'cd' errors, but the make will return status
zero. I have previously done a regular 'make' in this directory.

Using the same, identical branch in a different workdir, without first
running 'make', I see the failures *and* make returns an error.

I'm spending this afternoon digging in to try to understand what the
difference is between the two directories that accounts for this
behavior. It's not obvious to me by diffing the output of 'find . >
files.txt' for each dir.