On So, 27 Jan 2008, Bernd Schmidt wrote: > Actually it's nothing to do with gcc, it's an error you get from the > configure script when it tries to compile a test program and doesn't get > an executable for whatever reason. The actual error, from the log, > appears to be this: > > ld: in /Library/Frameworks, can't map file, errno=22 > collect2: ld returned 1 exit status > > No idea what that means though, I don't do MacOS. He's not either, he's using osX, which uses gcc. Which includes ld, and acts the same as ld on solaris, NetBSD, gcc on beos... I meant 'gcc' in terms of the 'gnu compiler collection' - which includes ld. (ld is the gnu linker.) Seriously, it's not an error that is coming from his choice of OS, please don't confuse it that way. When gcc, the gnu compiler collection, can't handle something dealing with a number of errors that have nothing to do with one another, it will often throw that very confusing error. I've seen it on Linux, osX, cygwin, gcc under AmigaOS, the BSD's ... basically anywhere gcc is available and you're trying to compile something... and it can't figure something out. Anyway these messages we've been sending all point to the same thing - there's something missing. And it's probably in the Frameworks directory, and it probably is something that the Xcode installer should have checked for and didn't. A reinstall of Xcode is probably all that will be needed. on the other hand, I got this error a long time ago when I didn't have the SDL framework... so Jens, check and be sure it didn't get removed.