Normally when building OpenJDK, the make variable OPENJDK should get set
to true. This happens automatically when the makefiles detect that certain
directories are missing, but I suppose this could be broken.
Try using an explicit: make OPENJDK=true
Or set OPENJDK as an environment variable, set to "true".
I'm suspecting that you have somehow fallen into a build that is not
an OPENJDK build (the makefiles are the same for OpenJDK and JDK).
We hope to completely remove our dependence on Motif in jdk7, or at least
I think that is the plan. I certainly won't miss this dependence, it's
quite convoluted how it hooks into the build process.
Are there any environment variables set with MOTIF in their name? e.g.
env | grep MOTIF
-kto
Peter B. West wrote:
On Sat, 2007-07-28 at 14:22 -0700, Kelly O'Hair wrote:
Where did you get these jdk sources?
From the source bundles of the OpenJDK project. Unfortunately, I have
not retained the bundle I downloaded, but I think it was the bundle from
the 15th of July. I'll try the latest bundle.
The OpenJDK sources should not have a dependence on Motif libraries,
just Motif include files.
-kto
Peter B. West wrote:
This thread started because I couldn't get jtreg to run against one of
the JDK sub-projects in NetBeans. As a result, I tried to build the j2se
project.
My environment is SuSE 10.2, NB 6 build 200704122300 Java 1.6.0_01. I
tried the build without specifying ALT_MOTIF_DIR, and was told I had no
motif 2.1. I have
openmotif-devel-2.3.0beta2-32
openmotif-libs-2.3.0beta2-32
openmotif-2.3.0beta2-32
installed.
I then tried grabbing the OpenBSD i386 2.1.30 package, and setting
ALT_MOTIF_DIR. That got me over the first hurdle, with the results shown
below.
Any suggestions?
Peter
-------- Original Message --------
Subject: Re: Getting Started with OpenJDK in NetBeans IDE?
Date: Thu, 19 Jul 2007 12:44:11 -0700
From: Dave Bristor <[EMAIL PROTECTED]>
To: Peter B. West <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Hi Peter, I think your question is better posted to the
[email protected] alias. If you can provide info re the distro
your
using, that might help. IIRC we tested on ubuntu and fedora.
Dave
Peter B. West wrote:
Dave Bristor wrote:
...
Before getting to that point, and thinking I might need to do a prebuild
of j2se, I tried that from a terminal. At the moment, that build is not
working because, in spite of what the docs say, the build requires not
only the openmotif header files, but the libs as well. The openmotif
libs I have installed are too recent, so it looks as though I will have
to build a set an install them in a non-standard place if I need to
build the jdk. Haven't sorted that one out yet.
The motif requirements are different for different OSs; cf the Ubuntu
6.06 v. 7.04 notes; in particular that the latter does have motif
dependencies (though I'm not sure this will resolve your problem without
knowing more about your build environment/platform). I just checked my
kubuntu 6.10 box, and seem to have headers+libs; YMMV.
Dave
Dave,
The first problem with the openmotif libraries is that the link points
to the hppa architecture's 2.1.30 package. Once I had corrected that, I
tried the build again. Here's a snatch of the output.
[exec]
../../../build/linux-i586/tmp/sun/sun.awt/motif21/obj/awt_motif21.o: In
function `awt_motif_getIMStatusHeight':
[exec] awt_motif21.c:(.text+0x426): undefined reference to
`_XmImGetGeo'
[exec] /home/pbw/src/openmotif/lib/libXm.a(DragC.o): In function
`DragKey':
[exec] DragC.c:(.text+0x2699): undefined reference to `__guard'
[exec] DragC.c:(.text+0x2785): undefined reference to `__guard'
[exec] DragC.c:(.text+0x279c): undefined reference to
`__stack_smash_handler'
[exec] /home/pbw/src/openmotif/lib/libXm.a(DragC.o): In function
`InitiatorMainLoop':
[exec] DragC.c:(.text+0x2d02): undefined reference to `__guard'
[exec] DragC.c:(.text+0x2d2c): undefined reference to
`__stack_smash_handler'
[exec] DragC.c:(.text+0x2eaa): undefined reference to `__guard'
It goes on and on like that. It looks as though it's trying to build
motif 2.1, but not 2.1 as we know it, Jim.
