OPENJDK env var not playing well with new build (original) (raw)

Erik Joelsson erik.joelsson at oracle.com
Wed Jan 23 13:00:34 UTC 2013


On 2013-01-23 13:23, Weijun Wang wrote:

On 01/23/2013 07:54 PM, David Holmes wrote: On 23/01/2013 8:58 PM, Erik Joelsson wrote: On 2013-01-23 11:30, Weijun Wang wrote:

I thought building an OpenJDK or Oracle JDK can be fully controlled by using the --enable-openjdk-only configure option, but it seems the OPENJDK env variable still plays a part. If the variable is set to true and --enable-openjdk-only is not provided, the new build process gets confused and fails. Can you point us at a log? I'd like to see exactly where the confusion arises. I don't have a log now. The problem is at libfreetype.so. Something like /libfreetype.so is needed to build .../libfreetype.so. Yes, I see how this would fail. In a closed build, configure doesn't setup freetype as it's not needed. Thanks.

/Erik



More information about the core-libs-dev mailing list