BUILD_HEADLESS_ONLY

[David Holmes]

On 6/03/2012 8:16 PM, martin burtscher wrote:
> Hello,
>
> i get the following error when i try to compile openjdk7:
>
>     /home/marty/openjdk/build/linux-i586/tmp/sun/sun.awt/jawt/obj/jawt.o
>    -L/home/marty/openjdk/build/linux-i586/lib/i386 -lawt
> -L/home/marty/openjdk/build/linux-i586/lib/i386/headless -lmawt
> -ljava -L/home/marty/openjdk/build/linux-i586/lib/i386/server -ljvm
> -lc
> /home/marty/openjdk/build/linux-i586/tmp/sun/sun.awt/jawt/obj/jawt.o:
> In function `JAWT_GetAWT':
> jawt.c:(.text+0x2a): undefined reference to `awt_GetDrawingSurface'
> jawt.c:(.text+0x39): undefined reference to `awt_FreeDrawingSurface'
> jawt.c:(.text+0x49): undefined reference to `awt_Lock'
> jawt.c:(.text+0x52): undefined reference to `awt_Unlock'
> jawt.c:(.text+0x5b): undefined reference to `awt_GetComponent'
> collect2: ld returned 1 exit status
> make[4]: *** [/home/marty/openjdk/build/linux-i586/lib/i386/libjawt.so] Error 1
> make[4]: Leaving directory `/home/marty/openjdk/jdk/make/sun/jawt'
> make[3]: *** [all] Error 1
> make[3]: Leaving directory `/home/marty/openjdk/jdk/make/sun
>
> i dont think this is a known issue, because i couldn't find anything
> about it. But what i'm really wondering is, that it's compiling awt
> altough i try to build it headless. Heres how i start the build:
>
> make LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk
> ALLOW_DOWNLOADS=true BUILD_HEADLESS_ONLY=true CROSS_COMPILE_ARCH=i586
> ALT_COMPILER_PATH=/usr/bin

Don't use BUILD_HEADLESS_ONLY it isn't really part of the OpenJDK build. 
It's an artifact of embedded builds for platforms where there are no 
graphics headers or libs available at build time - and may not even 
still work correctly.  Normal OpenJDK builds will build both headless 
and headful (by setting BUILD_HEADLESS true).

Why are you cross-compiling for x86 on linux-x86 using the local build 
tools ??? By doing this you've lost the defaults paths to the X11 
headers etc and so need to set ALT_OPENWIN_PATH.

David
-----

> As it doesn't seem to happen to someone else, i think its probably a
> configuration problem by myself. But i really have no idea what i
> could be. Any ideas are welcome.
>
> Greetz
>
> Marty