Fw: Re: Unable to Compile Wine on MacOSX
jjmckenzie51 at earthlink.net
Thu Feb 25 10:13:46 CST 2010
>From: James Mckenzie <jjmckenzie51 at earthlink.net>
>Sent: Feb 25, 2010 6:52 AM
>To: Charles Davis <cdavis at mymail.mines.edu>
>Subject: Re: Unable to Compile Wine on MacOSX
>>James McKenzie wrote:
>>> Interestingly enough, I have run into the 'Unable to compile' problem
>>> building the latest git on MacOSX. Maybe there is corruption in my git
>>> pull, but this started yesterday....
>>> It appears that configure never fully finishes and config.status loops.
>>I don't have that problem... And I've been experimenting with clang as
>>By the way, I never use git pull. I always do git fetch; git rebase
>>origin, which is what you're supposed to do anyway if you have local
>>patches in your tree.
>That is what I have been doing. What I may need to do is run git clone and get a new copy. For some strange reason my git copy gets corrupted and I have to do a new 'pull'.
>>Another thing I do is run autoreconf, because I have local changes to
>>configure.ac in my tree. That might have something to do with it.
>>I have noticed a change in configure behavior, though. config.status
>>creates the makefiles during make, not configure. I find that odd, but
>>it still works, so I'm happy.
>I'm thinking that both were running and that was causing problems as the first pass finished and then a second one started up.
>At least you confirmed this is 'normal'.
Send to list as well.
Can anyone confirm that this changed with either yesterday's or Monday's git?
More information about the wine-devel