On Wed, Feb 27, 2013 at 11:04 AM, Eric Blake <eblake@xxxxxxxxxx> wrote:
[...]
> You trimmed too much of your make line to tell us what was happening.
> It might also help to run 'make V=1' to get the full command line being
> attempted. I have to wonder if you have an unexpanded '$JAVA_HOME'
> injected somewhere into your configure output, where make is trying to
> compute $J (empty) followed by literal 'AVA_HOME'; maybe you should
> figure out what in your build setup is providing that bad variable value
> (correct would likely be '${JAVA_HOME}'). But I cannot reproduce your
> build failure, so it is something in your environment and not in libvirt
> itself that is causing you grief.
>
Eric, i was dizzy. Actually, i don't know why automake recognized
$JAVA_HOME as $AVA_HOME. However, i solved the problem like
following.
JVM_DIR=${shell echo ${JAVA_HOME}}
It works well for me. Thanks for your help ;-)
--
Thanks
Harry Wei
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list