Re: Commit f84871 breaks build on OS X

From: Brian Gernhardt <benji@silverinsanity.com>
Date: Dec 7, 2006, 15:29 UTC
Message-ID: <E8038C15-B359-4DE9-B3E0-45B065AEDBFA@silverinsanity.com>
In-Reply-To: <Pine.LNX.4.63.0612071554180.28348@wbgn013.biozentrum.uni-wuerzburg.de>

Alex Riesen wrote:

> Strange. You seem to have the old, generated Makefile you perl/
> directory. Haven't your pull failed?

My pull didn't fail, and your suggested list of commands tells me "Already up-to-date." I've pulled, reset, and removed perl/Makefile repeatedly when I was trying to use git-bisect. Primarily because of merge conflicts in perl/Makefile that running make causes.

Johannes Schindeli wrote:

Show 6 quoted lines

>> When I pulled the most recent changes for git (de51faf), `make` began
>> failing with the following messages: [...]
>
> I found the same, but could not reproduce it. But a "touch perl/ 
> perl.mak"
> fixes at least compilation.

Indeed, the following sequence works:

git reset --hard touch perl/perl.mak make

But this one doesn't:

git reset --hard make touch perl/perl.mak make

That one fails with "make[2]: *** No rule to make target `instlibdir'. Stop."

And both of these sequences cause `git status` to report that "perl/ Makefile" has been changed, which doesn't seem ideal.

(I'm replying to multiple messages because the list archive I'm browsing is getting the messages faster than I am, and I didn't feel the need to wait.)