configure fails on OS X 10.7.3 with Xcode 4.3

[haikuty]

Since I'm getting a crash on launch every time I thought I'd grab the source and see if I can fix it or run it under a debugger...
Got src ok, but running

Code: Select all

./configure

fails. But even before it fails it's emitting apparent nonsense:

HaikuView:VirtualBox-4.1.8_OSE tyler$ ./configure
Checking for environment: Determined build machine: darwin.amd64, target machine: darwin.amd64, OK.
Checking for kBuild: found, OK.
Checking for Darwin version: found version 10.7 (SDK: /Developer/SDKs/MacOSX10.6.sdk), OK.
Checking for gcc: found version 4.2.1, OK.
Checking for libIDL:
** libIDL-config (variable libIDL-config) not found!
Check /Volumes/HD/VirtualBox-4.1.8_OSE/configure.log for details
Mac1:VirtualBox-4.1.8_OSE tyler$ more configure.log
# Log file generated by
#
# './configure '
#

***** Checking environment *****
Determined build machine: darwin.amd64, target machine: darwin.amd64 <-- uh, pretty sure it's an intel chip in this machine... Intel Core i5 in fact.


***** Checking kBuild *****
found


***** Checking Darwin version *****
found version 10.7 (SDK: /Developer/SDKs/MacOSX10.6.sdk) <------ first, there is no /Developer; second why not the 10.7sdk? & why not LLVM?


***** Checking gcc *****
found version 4.2.1


***** Checking libIDL *****
** libIDL-config (variable libIDL-config) not found!

[michaln]

Try looking up "AMD64" on Wikipedia sometime.

And if you have to ask questions like "why not LLVM" then a good answer might be "try LLVM and you'll see why not".

[Perryg]

Aside from the additional questions, the real issue is a missing Lib or missing Lib-config (libIDL-config). Building VirtualBox on a MAC has its own way and Libs.

Here is the VirtualBox wiki with instructions
https://www.virtualbox.org/wiki/Mac%20O ... structions

And you can see here how someone else has achieved this.
viewtopic.php?f=31&t=44590

[haikuty]

Interesting to read about the history of AMD64. As a Mac dev I've only ever seen it referred to as "x86_64" for gcc/llvm.

After having some sleep (fool I am for posting at 2am), I can see that for a cross platform project, gcc is probably a better choice, though I'm really liking llvm for mac dev. Catches a lot of stuff that gcc let slip through and makes my code cleaner as a result.

Thanks for the link to the instructions for building on a mac, I'll check those out.

[michaln]

There's nothing wrong with LLVM (or clang) per se... the problem is that VirtualBox is low level enough that there is a very big chunk of code which needs to be adapted to each compiler. Even gcc-llvm isn't good enough.