>> The only surprise here is that configure is no longer looking for X11. Since
>> X11 is slated for complete excision I don't *really* consider that a bug, or
>> at the least an extremely low priority bug which puts it below JDK-8003900
>> anyways.
>
> If we cannot build without X11, then it
On 2014-01-10 18:17, David DeHaven wrote:
The only surprise here is that configure is no longer looking for X11. Since
X11 is slated for complete excision I don't *really* consider that a bug, or at
the least an extremely low priority bug which puts it below JDK-8003900 anyways.
If we cannot
The only surprise here is that configure is no longer looking for X11. Since
X11 is slated for complete excision I don't *really* consider that a bug, or at
the least an extremely low priority bug which puts it below JDK-8003900 anyways.
-DrD-
> Hello,
>
> I think this needs to be looked at b
> I'm trying to do a vanilla build on Mac OS X Mavericks. (Using an old copy
> of Xcode 4.)
>
> Configure succeeds as follows, while acknowledging that X11 is not found:
>
> sh configure --with-boot-jdk=$JAVA7_HOME
> --with-tools-dir=/Applications/Xcode4.app/Contents/Developer/usr/bin
> ...
>
Hello,
I think this needs to be looked at by someone in the 2d team. David
DeHaven was involved in this work I think.
Solaris in this context contains a lot of things common to all non
windows platforms.
/Erik
On 2014-01-09 19:47, Dan Smith wrote:
I'm trying to do a vanilla build on Mac O
