[collectd] Configuring/compiling collectd with Java support on Mac OS X

[Geoffrey Arnold]

Message bounced because of attachment size.  Here's the bzip'd config.log:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log.bz2
Type: application/x-bzip2
Size: 34896 bytes
Desc: not available
Url : http://mailman.verplant.org/pipermail/collectd/attachments/20100204/dc4700d4/attachment-0001.bin 
-------------- next part --------------

On Feb 4, 2010, at 2:38 PM, Geoffrey Arnold wrote:

> Hi Octo,
> 
> I started fresh and ran collectd-4.9.1/configure with the following options:
> 
> 	$ export JAVA_CPPFLAGS="-I/Library/Java/Home/include" 
> 	$ export JAVA_LDFLAGS="-L/Library/Java/Home/bundle/Libraries -Wl,-rpath -Wl,/Library/Java/Home/bundle/Libraries" 
> 	$ export JAVAC="/Library/Java/Home/bin/javac" 
> 	$ ./configure --prefix=$HOME/Applications/collectd-4.9.1 --enable-java
> 
> ... and received the same error:
> 
> 	libjvm  . . . . . . . no (libjvm not found)
> 	...
> 	configure: error: "Some plugins are missing dependencies - see the summary above for details"
> 
> Attached is config.log.
> 
> Thanks!
> Geoff.
> 
> <config.log>
> 
> On Feb 4, 2010, at 3:58 AM, Florian Forster wrote:
> 
>> Hi Geoff,
>> 
>> On Wed, Feb 03, 2010 at 05:43:51PM -0500, Geoffrey Arnold wrote:
>>> I tweaked the configure script to reflect the location of the required
>>> directories (the issue is that the `find` command used in the
>>> configure script does not traverse symlinks by default)
>> 
>> Unfortunatly, the option required to follow symbolic links is not
>> specified by POSIX and failed on some systems, iIrc some BSDs.
>> 
>> But you don't have to edit the configure script to specify the paths
>> manually. Try this:
>> 
>> JAVA_CPPFLAGS="-I/Library/Java/Home/include" \
>> JAVA_LDFLAGS="-L/Library/Java/Home/bundle/Libraries -Wl,-rpath -Wl,/Library/Java/Home/bundle/Libraries" \
>> JAVAC="/Library/Java/Home/bin/javac" \
>> ./configure $MORE_OPTIONS
>> 
>> This way you can manually specify the CPP-, C- and LD-flags used when
>> compiling the java plugin. It's not nice, but it should work for all
>> installations of Java.
>> 
>>> I believe that the issue is with finding libjvm.dylib.
>> 
>> Can you provide the "config.log" created by the "configure" script? It
>> should contain *why* the java plugin was disabled.
>> 
>> Regards,
>> -octo
>> -- 
>> Florian octo Forster
>> Hacker in training
>> GnuPG: 0x91523C3D
>> http://verplant.org/
>