[uae] Re: Problem compiling latest CVS on OSX?
- From: Richard Drummond <evilrich@xxxxxxxxxxxxxx>
- To: uae@xxxxxxxxxxxxx
- Date: Fri, 10 Mar 2006 01:00:10 -0500
Hi Jeff
On Thursday 09 March 2006 16:01, Demon Hell wrote:
> Nope, I just did what the docs said with a ./configure etc.
Yes. But that doesn't cover building from a CVS drop. The CVS repository
doesn't including the configure scripts, etc. since these are generated
files. The ./bootstrap.sh script calls the autotools commands to ensure that
all the necessary bits and pieces are generated. I probably need to add a
README.CVS in there to cover this stuff.
> Yep, did the ./bootstrap.sh and ran into them :(
> it now fails with..
>
> ld: Undefined symbols:
> _gFinderLaunch
> _getApplicationName
Yep. As as I said, the current CVS state is broken for OS X and building on OS
X was a complete hack anyway. I'm checking in the changes right now, so check
back around this time tomorrow, and all should be well.
> Great, if you need a guinea pig, gimme a shout.
I'll be doing a source-code snapshot probably tomorrow for people to test, so
if you try building that and letting me know what problems you have.
> BTW, has anyone else had problems with recoverable alerts on OSX ?
> When I set the CPU to 'after p96' the alerts flash once then vanish, but
> set to direct they stay flashing as normal...or is this the OS3.1 Alert bug
> in action?
Hmmm. The 'after p96' stuff only applies to the JIT and then only with the
JIT's direct-memory access. Are you building on OS X/x86?
Cheers,
Rich
Other related posts:
