Hi, Phil.
Should we update help.m4 as well and add a message for fontconfig like
we do for cups and others?
cups)
PKGHANDLER_COMMAND="sudo apt-get install libcups2-dev" ;;
cups)
PKGHANDLER_COMMAND="sudo yum install cups-devel" ;;
On 24/10/2017 14:15, Philip Race wrote:
Bug
Bug: https://bugs.openjdk.java.net/browse/JDK-8170681
Webrev: http://cr.openjdk.java.net/~prr/8170681/
This fix removes the copy of fontconfig.h from the JDK sources.
The file was originally included in the JDK sources because the
build platforms of the day were too old to include it.
It will h
Sorry I did not reply to this earlier.
But yes I've tested it and it works and I am going to send my fix for
review soon.
-phil.
On 10/22/17, 11:59 PM, Magnus Ihse Bursie wrote:
On 2017-10-18 13:28, Erik Joelsson wrote:
In preparation for removing fontconfig.h from the jdk src, this
change u
Can you provide some details about your toolchain, processor and os plus
a dump of the native instructions around the SEGV. This might give us
enough info to be able to figure out what’s going on.
Bob.
> On Oct 24, 2017, at 1:21 PM, Peter Budai wrote:
>
> I get that error running in the debugg
I get that error running in the debugger but also running without/outside of
the debugger as well.
I saw the comment in the code about generating SEGV in function
generate_get_cpu_info(), however the debugger can execute that, and the SEGV I
experience is coming later in the VM_Version::get_pro
Was this a SEGV while you were running the debugger?
There is an intentional SEGV generated. This is used to determine if we can
use some of newer
CPU features. Try to allow the SEGV to continue to see if you run normally.
Bob.
> On Oct 24, 2017, at 11:37 AM, Peter Budai wrote:
>
> It seem
It seems that the compile is progressing well, I have 49 executables/tools and
38 compiled shared libraries already in the JDK folder.
I have tried to run the product with the simplest ‘java -version’ command,
however I get a SIGSEGV at get_cpu_info_stub() in vm_version_x86.cpp,
VM_Version::ge
* Do you get to this stage at all? I.e, can you see "Createing jre jimage"
in the output?
Hi Magnus, when comparing the linux and aix logs of our openjdk9 builds , I
see for Linux at some point :
gmake[3]: Entering directory ` . . . /nightly/jdk9/make'
/bin/echo Creating jre jimage
On 2017-10-23 10:16, Thomas Stüfe wrote:
Hi Magnus,
On Mon, Oct 23, 2017 at 9:12 AM, Magnus Ihse Bursie
mailto:magnus.ihse.bur...@oracle.com>>
wrote:
On 2017-10-18 16:14, Thomas Stüfe wrote:
On Wed, Oct 18, 2017 at 3:25 PM, Volker Simonis
mailto:volker.simo...@gmail.com
On 2017-10-23 16:39, Erik Joelsson wrote:
This patch adds building of a new test bundle containing just the
remaining demos, which are used for client testing. It's basically
resurrecting the build logic for the old demo bundles, but adding
tests to the bundle name to make the intent clear. It'
10 matches
Mail list logo
