[LLVMdev] VMKit GNU classpath configure

[Garrison Venn]

Thanks for the response. Since X11 is by default installed on OS X when the developer tools
are installed. Running autoconf fixed the issue with configure not finding X11, although I did
not  check why the configure script did not have the correct path (I'm assuming this was the case).

Next I'm on to the gtk+ dependencies which I'm going to try to solve with macports if I have to. I
may punt on gtk+ though (per your instructions), if this gets to be a hassle. 

Thought you may want to track this.

Garrison

On Nov 22, 2011, at 11:29, Will Dietz wrote:

> On Tue, Nov 22, 2011 at 11:32 AM, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote:
>> As directed from http://vmkit.llvm.org/get_started.html, I'm getting:
>> 
>> checking for ld used by GCC... /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
>> checking if the linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
>> checking for shared library run path origin... /bin/sh: ./config.rpath: No such file or directory
>> done
>> checking for iconv... yes
>> checking how to link with libiconv... -liconv
>> checking for iconv declaration...
>>         extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
>> checking for X... no
>> configure: error: GTK+ peers requested but no X library available
>> 
>> when running:
>> 
>> ./configure --disable-plugin --disable-examples --disable-Werror
>> 
>> On:
>> 
>> OS X 10.7.2 with devel version:
>> 
>> Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)
>> Target: x86_64-apple-darwin11.2.0
>> Thread model: posix
>> 
>> Do I ignore the X check error, run X, or supply a path to X to configure etc?
>> 
> 
> Hi!
> 
> Glad you're trying out VMKit!
> 
> As to your issue, there are two solutions:
> 
> The simplest is to disable classpath's need for X, by telling it to
> not build its gtk peer (--disable-gtk-peer).  This will prevent you
> from running most applications that provide a GUI however.  Depending
> on your use case this might be acceptable.
> 
> Otherwise, ensure you have X11 installed (I'm not enough of a Mac user
> to tell you the best way to do this, including any possible gtk
> dependencies) and try the configure again.  Then take a look in
> config.log to see why the check is failing and point it to the right
> headers/libraries.  I'm happy to help with any further issues, but
> might be somewhat unavailable over the Thanksgiving holiday.
> 
> Let us know how this goes for you, and sorry I can't provide any more
> mac-specific help.
> 
> ~Will